Skip to content
Home/FAQ/Answer

How does the OpenKuai WhatsApp agent work?

Each sales rep gets their own WhatsApp business number on the official Cloud API. When a customer messages in a 1:1 thread, the agent answers from the product catalogue with citations, qualifies the enquiry, and escalates to the rep when needed. Sends are gated on a human authorisation row.


The interaction unit is the 1:1 thread, not a room:

  1. A customer writes to one rep’s business number — the number the rep already uses, on the official WhatsApp Cloud API.
  2. The agent answers from the product catalogue with citations, qualifies the enquiry, and escalates to a human when policy or confidence requires it.
  3. A human authorises everything a customer receives — the bridge commits before it acknowledges, and sends go out only when an authorisation row exists.
  4. A policy engine keeps it polite — never-reply rules, quiet hours, rate limits, and disclosure.

The agent drafts by default; it never sends autonomously.

Ask againAbout OpenKuai

Ask OpenKuai

FAQEsc Close · Ask OpenKuai

Connect an agent

Copy the prompt below into your agent to access OpenKuai via MCP.

Configure ask.mcpUrl in site.config / instance.config to enable MCP.

After connecting, ask in natural language. Does not support /await, promise responses, elicitation, chatgpt_app, arbitrary extension fields, result actions, or long-term memory.

Other machine-readable resources

  • /llms.txtSite entry map for agents to discover articles, FAQ, and API links
  • /openapi.jsonAPI fields and access notes for programmatic clients
  • Health checkConfirm Ask / MCP is online