When a carrier rejected a text because the destination was a landline or
an invalid/unreachable number, the system kept retrying that same number
through automations, manual sends, and bulk sends. Every retry failed the
same way and logged another compliance violation, which chips away at your
sending reputation with the carriers.
The number is now paused the first time a carrier reports it as a
landline or invalid — there’s no longer any need for it to fail several
times before it stops. Previously the safeguard only kicked in after three
consecutive failures, so a known-bad number could be re-attempted (and rack
up violations) before it was paused.
What’s Fixed
- A text that fails because the carrier reports the number as a landline,
an invalid handset, or a non-mobile number now pauses SMS to that number
immediately, across automations, manual sends, and bulk sends. - Pausing happens on the first failure rather than after three, so
known-bad numbers stop accumulating compliance violations. - Carrier-filtering (“spam”-style) failures are unchanged — those can be a
message-content issue rather than a bad number, so they still rely on the
existing repeated-failure safeguard.
Re-enabling a paused number
Carriers occasionally mis-classify a real mobile number as a landline. If a
number was paused by mistake, open the contact’s phone settings and resume
SMS for that number to start sending again.
Migration
No action required.