OpenKuai exists because sales teams live in WhatsApp, but software keeps asking them to leave it. Kuai meets the team where they already work: each rep keeps their own WhatsApp business number on the official Cloud API, and an AI agent works alongside them inside the 1:1 threads their customers are already in.

Agents paired with reps — not a replacement

A human remains the authorising party for anything a customer receives. The agent answers product enquiries from the catalogue with citations, qualifies the lead, and escalates to its rep when policy or confidence requires it. Drafts by default; never an autonomous send.

What OpenKuai is

• The sales team works where they already work. Rep business numbers on the official WhatsApp Cloud API, formed into human + agent teams, with the customer base segmented by demographic or other criteria.
• Customers get answered in the conversation they are already in. A customer’s own message in a 1:1 thread triggers auto-response and product enquiry.
• Every conversation is logged, searchable and reviewable — by humans and by agents — through Graph RAG, with citations. Conversation history is a first-class product, not exhaust.
• Product knowledge maintains itself through agentic SDK/MCP tooling that fits the team’s existing tools.

Non-negotiables

Customer data is a core asset held in-house. The system is self-hosted, and no third-party SaaS sees the customer corpus. Any egress relay that reaches WhatsApp carries ciphertext only — sessions and message content stay on the customer’s own node.

OpenKuai is built by Chatek, and lives at github.com/openkuai/kuai.