Connect a WhatsApp number to a KNet agent so people can talk to it where they already are.
Placeholder. The overview, links and concepts below are accurate; the detailed guides are still being written. Anything not yet covered is listed under What is not documented yet.
The WhatsApp integration connects a WhatsApp number to a KNet agent. Messages arrive as agent input and replies go back to the sender, so users get an assistant in an app they already have rather than one more login.
Open it: flow.knetai.com/whatsapp
Where it fits
- WhatsApp is a channel — it carries messages, it does not decide anything.
- Workflow Builder holds the agent that decides.
- KNet Traces records each conversation, grouped by session, so a multi-turn exchange reads as one thread.
Concepts
Instance — one connected WhatsApp number. Each instance routes to one agent.
Session — a conversation with one contact. Because WhatsApp is inherently multi-turn and long-lived, session handling matters more here than in a request-response channel: the agent needs to know what was said yesterday.
Webhook — how incoming messages reach the platform.
Before you connect a number
WhatsApp is a regulated channel with rules set by Meta, not by KNet. Template approval, opt-in requirements and messaging windows all apply, and they constrain what an agent may send unprompted. Confirm your use case is permitted before building on it.
What is not documented yet
- Connecting and verifying a number
- Message templates and approval
- Session and conversation-window handling
- Media messages
- Routing one number to multiple agents
- Rate limits and delivery guarantees
Getting help
Something here wrong or missing? Get in touch — a person reads every support request, and gaps in these pages are worth reporting.