Skip to main content

Chatbot — BOT Squad

Team landing page for the BOT Squad (Qontak). This folder groups the initiatives the Chatbot & AI team owns.

Initiatives​

The AI Agent's "action" surface is split into three sibling initiatives by what the action targets and how it authenticates. They share one Action drawer (IA) but are separate programs:

  • mekari-action/ — AI Agent actions in other Mekari products (Talenta, Jurnal, Desty), authenticated via HMAC with one-time SSO Super Admin approval.

  • qontak-action/ — AI Agent actions in Qontak's own features (create deal/ticket/tag, assign agent, resolve conversation, send attachment), authenticated via the company token.

  • native-integration/ — AI Agent actions in third-party apps outside Mekari (Google, Calendly, Salesforce, Zoho, Midtrans), authenticated via OAuth / per-provider. (Formerly midtrans-native-integration/, generalized into a provider umbrella.)

  • engineering-q3-2026/ — classed engineering bucket for independently pullable EOL tech-stack, runtime, dependency, reliability, and performance work.

  • code-readiness-q3-2026/ — open-contributor bucket for repository workflows, testing, MCP, hooks, agent skills, and internal operational tooling.

Jira work routing​

Primary outcomeCanonical homeJira Epic
Customer-facing product behaviorRelevant product initiativeThat initiative's declared Epic
Repository workflow, tests, MCP, hooks, agent skills, internal operational/admin toolingCode ReadinessBOT-4500
Runtime/framework/dependency/security/reliability/performance/architecture modernizationEngineering InitiativesBOT-4620
Standing QA BAU (automation coverage, deployment support, QA test ops)Not an initiative — delivery/qa-bau.mdCurrent-quarter Epic on that file (BOT-4609 in 2026-Q3); new Epic each quarter

Split work with independently deliverable outcomes; otherwise route by the primary outcome. See ADR 0001.

Program Management​