Overview
We’ve made message sending smarter by automatically catching issues that would cause messages to fail - before they’re sent.
Whether it’s a landline, an opted-out contact, or an invalid number, we’ll now give you instant, helpful feedback so you can take action (and save credits).
What’s New?
Checks for known issues before sending
We now catch messages that would have failed due to these common reasons:
21610
– Contact opted out (replied STOP)21635
, 30006
– Landline numbers that can't receive SMS21211
, 21614
– Invalid or non-mobile numbers21661
– Your number isn’t SMS-capable30034
– A2P registration not yet completed21408
– Region restrictions on sending...and more
Instant, clear feedback in the app
When a message can’t be sent for one of these reasons, you’ll now see a clear explanation — not just a cryptic error code.
Smart DND tagging to protect your list
We now help you automatically manage contacts that can’t be messaged:
Permanent DND
is applied when a number is known to be unreachable long-term,
such as:- Replied STOP (21610)
- Landline (21635,30006)
- Invalid or non-mobile number (21211,21614)
Temporary
DND is used when the issue might resolve soon, like:- Phone switched off or unreachable temporarily
- Carrier-specific delivery issues
This ensures your messages go only to reachable contacts — without you needing to monitor everything manually.
Why This Helps You
Boost message deliverability
Save credits by avoiding known failures
Understand issues right away (no more guesswork)
Run smoother campaigns with cleaner contact lists
Good to Know
- Already live — no action needed
- Works across Conversations, Campaigns, Bulk Messaging, and Workflows
- Only messages with guaranteed delivery issues are held back; all others will send as usual
Our Support Team is always here for you! If you’re unsure why a message wasn’t sent or want help optimizing your contact lists, just reach out — we’re happy to help.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article