An SMS database with 15% inactive numbers doesn’t raise any red flags at the point of entry. It shows up in your deliverability rate and on your bill at the end of the month. Verifying a mobile phone number before sending means eliminating wasted spend before it piles up. This guide covers the available methods, the right moments to apply them, and the most common pitfalls.
Why do invalid numbers cost so much?
Every SMS sent to an inactive, deactivated, or poorly formatted number is billed at the same rate as a successfully delivered message. No return, no conversion. The cost line doesn’t change.
The issue lies in the very nature of the mobile network. According to GSMA Intelligence, roughly one in seven mobile subscribers switches carriers over a 12-month period worldwide. In France, ARCEP reports a steady churn rate of around 4% per quarter on postpaid plans — that’s approximately 16% of the base over a year. A number that’s valid today may be reassigned to a different subscriber within six months, with no update to your database.
On a list of 50,000 contacts that hasn’t been verified in 18 months, the volume of numbers that have gone invalid can amount to several thousand wasted sends per campaign. And when your deliverability rate drops, carriers activate filters — making subsequent sends, even to valid numbers, harder to get through.
How to check if a mobile number is active in real time
The gold standard is to query the carrier’s network register directly. The HLR (Home Location Register) is the database each mobile operator maintains for its active subscribers. It holds the SIM status, network location, and number portability information. A network verification request returns an immediate answer: the number is active, inactive, or non-existent.
This check identifies unallocated or deactivated numbers, portability events from one carrier to another, and the line type (mobile or landline). The verification is non-intrusive: no SMS is sent to the checked number and the subscriber receives no notification. This is an important point for legal teams questioning the compatibility of this type of check with GDPR.
Captain Verify offers this service via API or file upload, with announced coverage across 96 countries and over 300 carriers. Unlike a reverse phone lookup, this method reveals no information about the number holder’s identity — it only answers whether the number can receive an SMS right now.
E.164 formatting: a step that’s often overlooked
Before running a mobile number verification, the number must be readable by telecom systems. The E.164 format, defined by the International Telecommunication Union (ITU), is the standard for any international SMS delivery.
The structure is straightforward: the + sign, followed by the country code (1 to 3 digits), then the subscriber number — no spaces or dashes — for a maximum of 15 digits. A French number is written as +33612345678, not 06 12 34 56 78 or 0033612345678.
Yet online forms accept dozens of different formats. The same number can end up stored in a database in four or five distinct forms. Without prior normalization, verification tools return false negatives, and SMS platforms reject sends or reprocess them at an extra cost. Normalization is handled upstream using libraries like libphonenumber (Google) or during CRM import. Most number verification tools include this step before the network check.
When should you verify a mobile number?
There isn’t just one right moment — there are three. Treating them as separate steps eliminates blind spots.
At the point of entry
A phone field equipped with a validation API rejects obviously incorrect numbers (impossible format, non-existent country code) before they ever enter the database. This is the lowest possible cost of correction and the only method that truly prevents degradation at the source.
Before each campaign
A verification pass on the full list identifies numbers that have gone inactive since the last check. For a database that’s growing fast or hasn’t been verified in several months, this check can reveal significant volumes to exclude.
Periodic cleaning
A full database cleanup rounds out the process. The frequency depends on the industry: monthly for businesses with a high volume of new contacts, quarterly to biannually for more stable databases. Without this safety net, obsolete numbers accumulate and drag down your metrics without anyone pinpointing the cause.
What GDPR says about storing mobile phone numbers
GDPR enforces a data minimization principle: mobile phone numbers may only be retained for as long as necessary to fulfill the purpose for which they were collected. Beyond that, they must be deleted or anonymized.
For numbers collected for SMS prospecting purposes, the CNIL recommends a maximum retention period of three years from the last active contact. A number left unverified beyond that window exposes you to two risks at once: contacting a former holder who never consented to receive your messages, and retaining personal data beyond the legal timeframe.
CNIL fines for serious GDPR violations can reach €20 million or 4% of annual global turnover. In this context, regularly verifying number validity serves both campaign performance and regulatory compliance. Captain Verify makes it possible to combine network activity verification and identification of numbers to purge in a single operation.
A clean phone database doesn’t happen by accident. It’s built at the point of entry and maintained send by send.
Frequently asked questions
Can you verify a mobile phone number for free?
Some tools offer a limited number of free verifications as a trial. Beyond that, real-time network verification is a paid service, billed per unit or per volume tier. The cost remains lower than that of an undelivered SMS — for campaigns involving several thousand sends, the math works out quickly.
How do you identify a mobile number’s carrier?
Network verification returns, in addition to the active or inactive status, the number’s current carrier and country of origin. This information accounts for portability: if a subscriber has switched carriers, the new carrier appears in the result. Useful for segmenting a database by network or detecting foreign numbers in a supposedly domestic list.
Does verification also work for landline numbers?
No. Network verification via HLR is specific to mobile lines. Landline numbers rely on a different type of infrastructure and cannot be queried the same way. Verification tools do identify the line type (mobile or landline) during the check, which allows you to filter out landline numbers that may have slipped into an SMS database.
