Reference: channel × segmentation compatibility, glossary and error codes
A table of which channel supports each segmentation and message type, a glossary of terms, and the most common error codes with their fix.
This is a quick-reference page for broadcasts: what each channel supports, what each term means, and what to do when a send fails. Keep it handy when planning campaigns.
Compatibility: channel × segmentation and message
Broadcasts support these four channels:
| Channel | Free-form message | Template required | Segment by groups/tags | Custom field |
|---|---|---|---|---|
| Only inside the 24h window | Yes, outside the window | Yes | Yes | |
| Yes (subject + body) | No | Yes | Yes | |
| SMS | Yes (plain text) | No | Yes | Yes |
| Telegram | Yes (the contact must have messaged your bot first) | No | Yes | Yes |
Rule of thumb: the stricter the channel (WhatsApp/Meta), the more the approved template and the 24-hour window matter.
Glossary
- Broadcast: the same message sent to many contacts, keeping each conversation individual.
- Template: a message pre-approved by Meta, required on WhatsApp outside the 24h window.
- Variable: a field like
{{first_name}}filled per contact. - Segment: a subset of contacts defined by tags, groups or filters.
- 24h window: the period after the customer's last message in which you can send free-form text.
- MAC (monthly active contacts): the cost unit; every contact you message counts against your plan.
- Opt-in / Opt-out: permission to receive messages / voluntary unsubscribe.
- Delivery rate: sent messages that reached the contact's device.
- Number quality: the score Meta assigns to your WhatsApp number; it drops with blocks and reports.
Common WhatsApp error codes
| Code | Meaning | What to do |
|---|---|---|
| 131047 | Re-engagement: 24h window closed | Send an approved template instead of free-form text |
| 131049 | Meta throttled the send to protect the ecosystem | Reduce marketing volume to the same user; space out sends |
| 131026 | Message undeliverable | Invalid number, no WhatsApp, or it blocked your account |
| 132000 | Parameter count doesn't match the template | Fill in every template variable |
| 132001 | Template does not exist / was deleted | Pick another template or recreate it and await approval |
| 132018 | Invalid template component | Check buttons/header; don't mix unsupported formats |
| 190 | Access token expired | Reconnect the channel (Embedded Signup) |
| 80007 / 130429 | Rate limit | Retry later; lower your send speed |
| 100 | Invalid parameter in the request | Check the recipient or template format |
If a whole send fails
- Open the campaign and look at the per-contact error in the recipient list.
- If all fail with the same code, it's usually token (190) or template (132001).
- Fix the cause and duplicate the campaign to resend only to the failed contacts.
Related articles
Related articles
-
How to create a broadcast campaign
Create, segment and schedule a broadcast to your contacts step by step in Omnifox.
-
Best practices to broadcast without getting blocked
Reduce spam reports and blocks by following these rules when sending broadcasts on WhatsApp and other channels.
-
What a campaign is and its statuses (draft, scheduled, sending, completed)
What a broadcast campaign is in Omnifox and what its statuses mean: draft, scheduled, sending and completed.
-
Supported broadcast channels (WhatsApp, Email, SMS, Telegram)
Learn which channels you can use to send broadcasts in Omnifox and what each one requires.
-
Segment your audience: everyone, groups, tags (AND/OR) and custom field
Learn to precisely choose who receives your broadcast by combining groups, tags with AND/OR logic and custom fields.