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.
FAQ
Can WhatsApp use a different workspace than the website?
Yes, but answer consistency usually suffers. Prefer one Support workspace.
Where do failed sends appear?
Check Meta delivery errors and Qefro conversation/tool logs for the tenant.