WhatsApp automation is not a single toggle. It is a rollout.
If you enable "auto" too early, you will lose trust internally and externally. The safer approach is to deploy modes:
- Off: nothing acts
- Shadow: the system observes/drafts (no automatic sends)
- Auto: the system can act (with controls)
See:
Mode 1: Off (baseline)
Use this when:
- You are still connecting accounts and templates
- You are not confident in your data quality
- You have not validated consent capture
Off mode is the correct starting state.
Mode 2: Shadow (observe/draft)
Shadow mode is how you learn without causing incidents.
Use it to validate:
- Who would have been messaged?
- Which template would have been selected?
- Which guardrail would have blocked sending?
- Where data gaps exist (missing variables, missing identifiers)
Shadow mode is also how you build stakeholder trust: you can review drafts before the system is allowed to act.
Mode 3: Auto (act, but with guardrails)
Only enable auto mode when:
- Templates and variables are stable
- Consent capture is reliable
- Budgets are in place (tenant + conversation)
- Kill switch is tested
Auto mode without budgets is not "automation." It is an accident generator.
The rollout checklist (printable)
- Connect WhatsApp accounts
- Configure templates and variables
- Enforce consent gating (fail closed)
- Turn on shadow mode for 1-2 weeks
- Review drafts and denial reasons
- Add budgets and kill switch
- Enable auto mode for a narrow workflow
- Expand only after stability
What to do next
- Start with the foundation: WhatsApp Business integration (Dubai)
- Then implement the guardrails: WhatsApp automation (Dubai)