Manage WhatsApp conversations, templates, outbound work, and operational controls.
- For
- Revenue teams and admins
- Owner
- Communication operations
- Outcome
- Use WhatsApp with visible connection, template, and delivery state.
- Last verified
- 2026-08-30
- Next review
- 2026-11-28
- Status
- supported
WhatsApp is split into day-to-day conversation work, outbound operations, automation, and settings. Start with the conversation, then move to the supporting surface that owns the decision.
The core surfaces
- WhatsApp is the conversation workspace.
- Outbound holds sequences, broadcasts, and send-oriented work.
- Settings owns templates, operations, voice, and channel configuration.
- Automation holds bots, flows, and auto-responders.
- Developer is for integration and webhook work, not day-to-day replies.
A safe launch path
- Connect and verify the channel identity.
- Create or review approved templates before using them in a customer workflow.
- Start with one internal or tightly bounded test audience.
- Confirm the message and delivery evidence in the conversation.
- Only then expand the audience or automation scope.
Keep the human boundary clear
Automation can prepare or route work, but customer-facing sends still need the right role, provider readiness, and workspace configuration. If the channel is paused or unavailable, leave the work visible for review.