Skip to content
Home/FAQ/Answer

How can my team adopt OpenKuai?

Adoption starts with a self-hosted deployment. Your reps keep their own WhatsApp business numbers; your product knowledge is imported into Kuai KB from existing sources; then you switch on human+agent teaming and tune the policy engine per team.


OpenKuai is deployed self-hosted, on your infrastructure. A pilot has three steps:

  1. Onboard the reps — each rep’s own WhatsApp business number joins via the official Cloud API; identity binds through your directory groups.
  2. Feed the knowledge base — Kuai KB imports from the product sources you already have, with review and audit from day one.
  3. Pair the agents — human + agent teams go live with the policy engine set conservatively (drafts only, quiet hours, disclosure), then loosens as trust is earned.

Managers see their team’s conversations through review; admins manage roles through directory groups — one source of entitlement. Reach out via the contact on the About page to talk through a pilot.

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