Create a WhatsApp Broadcast Campaign
Send a permission-based WhatsApp campaign using an approved template, selected contacts or segments, variables, and scheduling.
Main concepts and fields
| Source Number | Connected WhatsApp Business number. |
|---|---|
| Template | Meta-approved Utility, Marketing, or Authentication template. |
| Audience | All eligible contacts, selected contacts, or a segment. |
| Variable Mapping | Connects template placeholders to Wemblo fields. |
| Schedule | Immediate or future send time in PKT. |
Step-by-step instructions
- Open Campaigns and choose WhatsApp Broadcast.
- Select the connected number and approved template.
- Choose the eligible audience.
- Map every variable and add fallback values where supported.
- Assign reply ownership.
- Send an internal test.
- Schedule or launch.
- Review sent, delivered, read, and failed events where Meta provides them.
Common issues and solutions
Provider charges and Meta messaging rules remain separate from the Wemblo plan.
| Template is missing | Check WABA, language, approval, and synchronization. |
|---|---|
| Recipient fails | Check +92 phone format, consent, and the provider error. |
| Variable is blank | Check contact field mapping. |
Who should use it
Marketing users, sales teams, workspace managers and authorized campaign operators.
Where to find it in Wemblo
Wemblo -> Marketing -> Campaigns -> WhatsApp
Before you begin
- Use the correct workspace and connected channel.
- Confirm audience consent and provider eligibility.
- Prepare fictional test contacts and approved content.
- Assign a person or team to handle replies.
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: