Valid doesn't mean sendable: why some numbers still fail SMS/WhatsApp

"Valid" doesn't mean "sendable": why some numbers still fail SMS/WhatsApp

We've all been there: the list looks clean, the numbers parse fine, and a chunk of the campaign still comes back failed, undelivered, or quietly never delivered.

Most of the time it's not a single bug — it's three different problems hiding in the same list:

1) Format is valid, but the number isn't what it looks like. SMS and WhatsApp routing are strict about E.164 formatting. A number that parses fine visually can still break routing once the aggregator tries to interpret the country code or trunk prefix. Normalizing everything to full international format before it hits a gateway removes a whole class of failures.

2) The list has duplicates. The same contact twice means the same send charged twice — and dedupe matters more on paid A2P routes, where you get billed per message segment.

3) Grammar-clean doesn't equal routable. A number can be syntactically perfect and still be a dead line, a VoIP number that a given OTT/Messaging channel won't register, a landline masking as mobile for SMS, or a number with no carrier route at all. Syntax checking and carrier-level / line-type / registration checks answer different questions — and for campaigns you usually want both layers.

Practical pattern that saves money:

- Normalize to E.164 first.

- Dedupe on the normalized value.

- Then run a line-type / reachability-layer check (carrier, mobile-vs-fixed, and channel registration like WhatsApp or Telegram where relevant).

- Preflight a small sample before approving the full send.

I tend to wire it as: quick local formatting pass → bulk check via an API on the remaining rows → only then hand the clean set to the SMS/WhatsApp provider.

If you're cleaning or verifying phone lists before a campaign or a route decision, the verification workflows at https://phoneveriflo.com cover this kind of preflight (E.164 normalization, line type / carrier signals, and messaging-channel registration checks). Worth a look if you're still shipping raw lists to your gateway.

Anyone else running list hygiene as a mandatory step before bulk messaging? What layer tends to catch the most waste for you — duplicates, formatting, or reachability?