Customer chat
DJINN + WhatsApp
Customer conversations with the company's memory behind them, and a human holding the send.
How it connects
Business API, one number
A Business API number and a webhook. Everything behind the channel layer — memory, routing, approvals — is already built and shared with every other channel.
Reply drafts, not autoresponders
An autoresponder that is wrong in front of a customer costs more than it saves. DJINN drafts with full account history; a person sends.
No connector yet
The WhatsApp Business Cloud API delivers inbound messages by webhook only — there is no endpoint that lists message history. Everything pollable is configuration, not conversation.
Documents
WhatsApp setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- SetupBusiness API onboarding
- ReferenceEscalation and handoff rules
Want WhatsApp wired into your own company brain?