Communication β WhatsApp integration
The WhatsApp Business integration sends automated template messages to guests via WhatsApp for appointment confirmations, reminders, and follow-ups. This article covers day-to-day operations for the WhatsApp Business API configuration. For messaging through HyperConnect's agent UI, see the HyperConnect category.
On this page
- Before you begin
- How WhatsApp messaging works
- Message types
- Configure and manage templates
- Handle WhatsApp failures
- Reconciliation
- Tips
Before you begin
Permission: You need organization administrator access to configure WhatsApp messaging and template approvals; any user with notification-management permission can enable or disable approved templates.
- The WhatsApp Business integration must be configured. See Configure WhatsApp business messaging.
- Templates must be approved by Meta before they can be sent.
How WhatsApp messaging works
- A guest books an appointment and has a WhatsApp-enabled phone number on their profile with a valid opt-in.
- At the configured send time, Zenoti renders the appropriate approved template and dispatches it through Meta's WhatsApp Cloud API.
- The message is delivered through your WhatsApp Business Account (WABA) from your registered business phone number.
- The guest receives the message in the WhatsApp app. Delivery and read receipts flow back to Zenoti via Meta's webhook.
Integration settings follow Zenoti's standard inheritance: center-level settings override organization-level settings. If a center has no WhatsApp configuration, the organization-level settings apply.
Message types
| Type | Scope | Used by Zenoti automation? |
|---|---|---|
| Template message | Pre-approved message with placeholders; can be sent to any opted-in guest at any time. | Yes β all automated Zenoti notifications use template messages. |
| Session message | Free-form message allowed only within 24 hours of the guest's most recent inbound message. | No β Zenoti's automated notifications do not use session messages. |
All automated Zenoti notifications use template messages. Session messages belong to conversational-messaging workflows covered in the HyperConnect category.
Configure and manage templates
- Navigate to Configuration > Integrations > Integration settings, then search and expand Whatsapp.
- Select View Template Migration Status Dashboard. Templates themselves are authored and approved with your messaging provider and Meta; Zenoti shows each Template Name, Type, and Status (Pending, In-Progress, Completed, Failed).
- Author templates with your provider for:
- Appointment confirmations.
- Appointment reminders (for example, 24 hours before and 2 hours before).
- Post-appointment follow-ups.
- Submit each template for WhatsApp approval with your provider.
- Once Meta approves a template and its migration shows completed in Zenoti, enable it in the relevant notification setting. Select Retry on a failed migration.
- Monitor template status periodically β Meta can retire approvals if a template violates policy or is rarely used.
Handle WhatsApp failures
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| Message not delivered | Delivery status remains Sent or shows Failed. | Verify the guest's phone number includes the country code and is WhatsApp-enabled. Confirm the guest has opted in. |
| Template rejected by Meta | The template's migration shows failed and it cannot be used. | Review Meta's feedback, edit the template to comply with the category and messaging policy, and resubmit. |
| Sender not active | The Configuration Summary shows the Sender Status as unverified, or messages stop sending. | Expand Whatsapp under Configuration > Integrations > Integration settings, select Verify Number, and complete the verification code again. |
| WABA migration pending | Integration page displays a migration banner. | Complete the migration to update your provider configuration, then re-verify templates. |
| 24-hour session window expired | A reply-style message (session message) is rejected. | Use an approved template instead, or wait for the guest to re-initiate the conversation. |
| Guest revoked opt-in | Individual messages to that guest fail. | Remove the guest from further WhatsApp automation; honour the revocation. |
Reconciliation
Match Zenoti's outbound WhatsApp volume against Meta Business Suite's reporting.
| Source | Report / view | Match key | Cadence |
|---|---|---|---|
| Zenoti | Notifications sent log, filtered to WhatsApp channel | Send timestamp + guest number | Weekly |
| Meta | Meta Business Suite > WhatsApp Manager > Insights | Send timestamp + guest number | Weekly |
Investigate sends that appear in Zenoti as Sent but do not show up in Meta's Insights β these usually indicate template-rendering or network issues during dispatch.
Tips
- WhatsApp messages require an opt-in from the guest. Ensure your guest onboarding process includes WhatsApp consent that complies with Meta's policy.
- Template messages must comply with Meta's messaging policies β avoid promotional language in transactional templates.
- Monitor message delivery rates in Meta Business Suite and in Zenoti's integration health dashboard.
- For WhatsApp messaging through HyperConnect's agent UI, see the HyperConnect category.