Most WhatsApp reporting answers one question: how many went out. That number is comforting and nearly useless, because it treats three unrelated problems as one.
Here is what separates them, and what each one asks you to do differently.
A rejected template is a decision, not an outage
A template is reviewed before it can ever be used. When it comes back rejected, nothing was sent and nothing failed in transit — the message was never eligible to leave.
The fix is editorial rather than technical: the variables, the category the template was submitted under, or the promotional language in a message submitted as a utility one.
An unreachable number is a data problem
A number with no WhatsApp account behind it, or one that has blocked your business, will never accept a message however many times you retry it.
This is the failure worth acting on in your contact list rather than your campaign. Retrying costs a credit each time and changes nothing.
- Check the number's format before the send, not after the failure
- Keep opt-outs out of the list rather than filtering them at send time
- Treat a repeated hard failure as a reason to stop contacting that number
Throttling is the platform pacing you
A send that is held back is not a send that failed. Messaging limits scale with the quality rating of your number, so the answer to being paced is rarely to send harder.
The number's rating responds to how people react to your messages — blocks and reports pull it down far faster than volume pushes it up.
Report the three separately
The practical change is small: stop reporting one failure count. A campaign with 40 rejections, 3 unreachable numbers and 200 paced sends needs three different people to do three different things, and a single total tells none of them which.
Want this running on your numbers?
Start with a free trial — no card, and every service on one account.
