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.
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-3476/3662/3496 |
| Qontak Chat actions | Assign agent, resolve conversation, create tag — internal workers (no token) | Backend shipped (3); not in legacy FE picker | — |
| 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 |
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).