Products
A customer service agent and analytics system built around the sales team, not instead of it.
- 1:1
- WhatsApp thread model
- 100%
- Self-hosted customer data
- K1–K5
- Capability surface
- 24/7
- Knowledge base uptime
Featured
Featured products
Kuai KB
The self-maintaining product knowledge base at the core of OpenKuai — a review board, chat, and audit trail over a graph of your product knowledge, served read-only to agents and reps alike.
Gives every agent and rep one reviewed, citation-backed source of product truth — maintained by agentic tooling, not by hand.
- Live serving the real database read-only, behind a review board and full audit log
- Hourly fetch tier lands sha256-checked source records onto an append-only ledger
- Retrieval over pgvector with HNSW + trigram search and a local reranker
- MCP bindings so any prime-agent can query product knowledge with citations
Kuai Agent
One agent per sales rep, answering product enquiries in 1:1 WhatsApp threads on the rep's own business number — with citations, qualification, and human-in-the-loop escalation.
Customers get answered in the conversation they are already in, while the rep keeps authorship of everything a customer receives.
- Runs on each rep's own WhatsApp business number via the official Cloud API
- Answers from the product catalogue with citations, then qualifies the enquiry
- Policy engine enforces never-reply rules, quiet hours, rate limits, and disclosure
- Sends are gated on a human authorisation row — drafts by default, never autonomous send
Kuai CRM
The customer-side surface — NextCRM, self-hosted, extended with Kuai's rep identity spine so every conversation, lead, and approval belongs to a real person on a real team.
Customer data stays a core asset held in-house — no third-party SaaS ever sees the customer corpus.
- Self-hosted NextCRM on PostgreSQL, kept MIT-clean with a 127-tool MCP surface
- Entitlement has one source — LLDAP groups — deliberately decoupled from CRM-local roles
- Rep, manager, and admin roles with a least-privilege session model
- Customers never authenticate — they are data subjects, not accounts
Archive