Qontak Action (AI Agent)
Let the Qontak AI Agent do what Qontak's own features already do — create and update deals and tickets, create tags, assign agents, resolve conversations, and send attachments — invoked via function-calling during a conversation and authenticated with the company's Qontak token. These are first-party actions: no cross-product credential approval is required; the builder simply enables them.
QA Lane
Lane B — keeps a human QA gate. Money-critical: creates deal and ticket revenue objects. No E2E test specs exist for this initiative yet, so the Lane-A entry bar (100% E2E, spec-mapped coverage) is unmet regardless. Classified 2026-06-29.
One of three sibling "action" initiatives. They share one Action drawer (IA) but differ in what they target and how they authenticate:
Initiative Targets Auth Drawer groups Qontak Action (this) Qontak's own features Company token Mekari Qontak Mekari Action Other Mekari products HMAC + SSO Super Admin approval Mekari Talenta / Jurnal / Desty Native Integration Third-party apps outside Mekari OAuth / per-provider Other integration
Master index (ANCHOR)
qontak-action-anchor.md— the ANCHOR PRD: the initiative master index (identity, action catalog, decisions, Development Status). It carries no acceptance criteria of its own (those live in the action PRDs), so it sits at the initiative root rather than underprds/. Confluence: Qontak Action — Released Actions (as-built) — there is no Confluence ANCHOR page for this initiative; the as-built page is the initiative-level overview.
Jira Epics (multi-Epic initiative)
This initiative is a catalog of first-party actions, each action group tracked by its own Jira
Epic (see the ANCHOR). Jira's BOT project is flat (no tier above Epic), so the initiative is
anchored by an umbrella Epic — BOT-4597 — AI Agent — Qontak Native Actions (umbrella)
(the jira_epic above) — and each action group hangs off its own child Epic below. The umbrella is a
naming anchor only: the flat project cannot re-parent the child Epics under it. Because the
initiative genuinely spans several Epics, the README frontmatter declares jira_epic_model: umbrella,
which switches the delivery drift linter (lint-delivery.mjs CHECK GROUP H) into umbrella mode: it
validates each action PRD's header Epic against the child-Epic allow-set below (this table's Child Epic column) instead of requiring one Epic per initiative. A declared child Epic passes; an
undeclared / typo'd one still fires PRD_EPIC_NOT_IN_FAMILY, and a PRD that collapses onto the
umbrella anchor fires PRD_EPIC_IS_UMBRELLA — the model is accommodated, not silenced. Keep every
action PRD's child Epic listed here.
| Action group | Child Epic | Notes |
|---|---|---|
| Qontak CRM + Chat actions | BOT-3350 | 26Q1 Qontak MCP Integration: Backyard Management (Done). The individual actions shipped as Tasks under it — create deal BOT-3476, update deal BOT-3496, create ticket BOT-3662. |
| Send Attachment | BOT-4341 | AI Agent - Actions Send Attachment (In progress). |
| CRM Deals Custom Fields | BOT-4662 | 26Q3 adjustment to Qontak CRM actions: pipeline-scoped custom fields (incl. array-typed) on create deal / create ticket. GA to all clients/users 2026-07-27; implementation recorded in Chatbot BE 1.324.0 and Hadiningbot FE 3.8.3. |
| Get Ticket & Get Deals | BOT-4790 | 26Q3 Chatbot - CRM Actions: Get Ticket & Get Deals (To Do). Minted 2026-07-27 to hold work that was mis-parented under BOT-4662 — see the capture note. FE field-array picker BOT-4727 (Done, Baghiz Firdausa) re-parented here. |
| Send WhatsApp Flow | TBD | Epic to be created when the PRD leaves DRAFT. |
| Appointment Booking actions | TBD | Epic to be created when the PRD leaves DRAFT. |
Action catalog
| Action group | Goal | Status | Epic |
|---|---|---|---|
| Qontak CRM actions | Create deal, update deal, create ticket, update ticket — via company token | Backend shipped (4); 3 in legacy FE picker, Update deal backend-only | BOT-3350 (tasks 3476/3496/3662) |
| Qontak Chat actions | Assign agent, resolve conversation, create tag — internal workers (no token) | Backend shipped (3); not in legacy FE picker | BOT-3350 |
| Send Attachment (Confluence) | Native action that sends the actual file/image to a customer, reusing the send-attachment bot-response function | In review | BOT-4341 |
| CRM Deals Custom Fields | Map tenant CRM custom fields (incl. array-typed) into the create deal / create ticket actions | Shipped — GA to all clients/users 2026-07-27 (note) | BOT-4662 |
| Get Ticket & Get Deals | Look up a ticket (by string ticket id) or a deal and reply with only the response fields the builder selected | Not started — FE field picker Done (BOT-4727); BE unstarted, no PRD yet | BOT-4790 |
| Appointment Booking actions | create_booking / find_booking against the Qontak Appointment service — idempotent create with server-side round-robin, compact find — via company token | Draft | TBD |
Contents
prds/— action PRDs (each with its own ACs → Jira Epic) land here.rfcs/— Request for Comments (technical design proposals).tests/— E2E / acceptance test specs.delivery/— TPM program-management docs (timeline, status, decisions).