Research
Field notes on conversation intelligence, product knowledge graphs, and human+agent teams from the OpenKuai team. 11 articles.
Series
01 / Series
Research
Conversation intelligence, knowledge graphs, and human+agent teaming research.
Enter series
02 / Series
Product
OpenKuai product capabilities, launches, and deploy milestones.
Enter series
Archive
Browse by topic2026
2026-09-23
Welcome to OpenKuai
OpenKuai is a customer service agent and analytics system for sales teams. This site documents capabilities, research reports, deploy milestones, and builder notes.
Research
2026-09-23
Kuai KB Is Live — Serving the Real Database, Read-Only
The Kuai KB knowledge tier went live, serving the real database read-only behind a review board and audit log; the fetch tier lands sha256-checked records hourly.
2026-09-23
Inside the Enquiry Loop — What We Measured
The 1:1 WhatsApp enquiry loop was measured end to end, webhook to send, on the live channel. The transport is not the bottleneck; the time goes to knowledge-base coverage and model re-asks.
2026-09-22
K4 — Product Knowledge That Maintains Itself
K4 keeps the product knowledge base current through agentic fetch, a ledger applier, retrieval over pgvector, and MCP bindings — live end to end, serving the real database read-only.
2026-09-21
One Registry Name per Service — the Networking Model
The OpenKuai networking model — three planes (bridge, tailnet, internet), a registry giving one name per service, and agents that are clients of everything and servers of exactly one thing.
Research
2026-09-20
K1 — WhatsApp, Team Formation, and Segmentation
K1 is the delivery path — reps on their own WhatsApp business numbers (official Cloud API), human+agent team formation, and customer segmentation. Transport is live; the team and segmentation product surface is in design.
2026-09-19
K3 — Conversation Intelligence via Graph RAG
K3 makes every customer↔rep↔agent conversation searchable and reviewable through Graph RAG, with citations — a second, rep-scoped corpus with index-time privacy and retraction paths.
2026-09-18
One Bot per Rep — Why OpenKUAI Is 1:1-Only
OpenKUAI is 1:1-only by design — one agent per rep on the rep's own WhatsApp business number, with group chats out of scope. The 1:1 thread keeps session ownership, privacy and per-rep scoping simple.
2026-09-17
K5 — Analytics as a Rendered Page, Not a BI Stack
K5 renders analytics as a page over the existing stores — conversation corpus, Kuai DB, and the CRM — with no warehouse, no BI stack, and no event pipeline.
2026-09-16
Data Sovereignty by Architecture — Ciphertext-Only Egress
Data sovereignty is preserved architecturally — the egress relay that reaches WhatsApp carries ciphertext only; sessions and message content never leave the customer's own node.
Research