WhatsApp connects Meta Cloud API messaging to a Qefro Customer AI workspace. Availability: Growth+.
Short definition (citation-ready)
Qefro WhatsApp Customer AI receives Meta Cloud API webhooks at
api.qefro.com, runs the bound workspace’s RAG/tools, and sends replies back through Meta.
API routes
| Method | Path | Purpose |
|---|---|---|
| GET | /api/v1/whatsapp/webhook | Meta verification challenge |
| POST | /api/v1/whatsapp/webhook | Inbound messages |
Tenant credentials and workspace mapping are configured in Admin Console (encrypted). Confirm exact field names in the console UI.
Architecture
Workflow
Follow the full playbook: Deploy WhatsApp AI.
WhatsApp readiness
- Website quality first — Same Support workspace preferred.
- Confirm Growth+ — Plan entitlement.
- Meta app + tokens — Store secrets in Qefro.
- Verify webhook — GET challenge must succeed.
- Pilot users — Compare answers to widget.
Conversation commands
WhatsApp has no native New conversation button like the Website Widget or Admin Playground. Users can manage threads with slash commands (case-insensitive):
| Command | Description |
|---|---|
/new | Start a new conversation (previous thread is archived, not deleted) |
/clear | Same as /new — start over with a fresh conversation |
/help | Show available commands |
Example replies:
/new→ “Started a new conversation…”/clear→ “Conversation cleared…”/help→ command list
These are system commands: they never call the AI Runtime, RAG, Business Tools, or consume LLM tokens. Verified identity and authentication context for the WhatsApp contact are preserved.
Interactive Reply Buttons
WhatsApp replies can include platform-owned quick-action buttons (Meta Interactive Reply Buttons):
| Button | Action |
|---|---|
| 🆕 New Chat | Same as /new |
| ❓ Help | Same as /help |
Only Qefro platform actions are supported today. Business-specific buttons (track order, book service, my account, …) are not implemented yet — those will come later through Business Tool capabilities.
Fallback: If Meta rejects an interactive message (unsupported client, API error, etc.), Qefro sends plain text and lists /new and /help so users never lose the actions.
Slash commands continue to work alongside buttons. Widget and Playground UI are unchanged.