
A customer taps "Get code," but the SMS never arrives. A minute later they request the code again, then once more. From the user's side, it looks like one undelivered SMS. From the service's side, that's already three messages instead of one, an incomplete authentication, and the risk of losing the customer before they even log in.
The scale of the problem is much bigger than that. According to Mobilesquared's estimate, the global A2P market lost around 1.26 trillion messages in 2024. By 2029, that figure could grow to 2.48 trillion. The causes include shifting communication channels, fraud, routing issues, and tighter control over A2P traffic.
That's why, for a business, the number of SMS marked "sent" isn't what matters. What matters is knowing how many messages were actually delivered, how long it took, and which carriers are generating failures.

An SMS from a service and a message one person sends another are different types of traffic as far as a mobile carrier is concerned. OTPs, delivery notifications, appointment reminders, and marketing blasts all fall under A2P — application-to-person messaging.
That kind of traffic goes through extra checks. A carrier may analyze the sender, the route, message frequency, campaign registration, text templates, and other parameters. This is needed to fight spam, smishing, Sender ID spoofing, and other forms of abuse. According to BICS, roughly 4–5% of global SMS traffic is fraudulent.
Picture a service that normally sends 10,000 SMS a day. During a major campaign, hourly volume jumps several times over.
For the business, that's a successful launch. For the carrier's automated system, a sudden change in pattern can be one of the signals that triggers extra scrutiny or traffic throttling.
That's why large campaigns need to be planned with throughput, the specific carrier's rules, and A2P traffic registration requirements in mind.
Carriers and SMS platforms apply automated filtering to enforce their own messaging policies and regulatory requirements. Twilio, for example, explicitly warns that carrier filtering in the US and Canada can affect SMS and MMS delivery.
Suspicious URLs, a mismatch between the message and its registered use case, missing user opt-in, or other violations of a given market's rules can all cause problems.
That's why changing a single word in a message doesn't always fix the issue. If the root cause lies in the Sender ID, the route, or campaign registration, editing the text won't restore delivery.
Sender reputation isn't built on a single message. Carriers may take into account the type of Sender ID, traffic history, complaints, and compliance with local rules.
Requirements vary by country. In some places, registering an alpha sender name is enough; in others, you need to provide company details, a use-case description, sample messages, or proof of opt-in.
The US is a good illustration of just how much regulation can affect delivery.
As of February 1, 2025, A2P traffic sent through US 10DLC numbers must be registered with The Campaign Registry. Unregistered messages are blocked by major carriers, including AT&T, T-Mobile, and Verizon. In February 2025, Bandwidth also reported network-level blocking of unregistered 10DLC traffic.
In that scenario, resending the message doesn't fix the problem.
If a company sends 50,000 SMS a month but its campaign doesn't meet a specific market's requirements, the entire message stream is at risk — not just a handful of failed SMS.
That's why Sender ID and A2P campaign registration need to be checked before traffic goes live.

The price of a single SMS can vary several times over between providers. The reason isn't always margin. What matters is understanding which route the message takes to reach the mobile carrier.
A white route runs through agreed commercial channels. A grey route exploits gaps in interconnect agreements or other schemes that let A2P traffic pass without going through a standard termination model.
According to Mobilesquared, in 2015, 65% of global A2P SMS traffic passed through grey routes. By the end of 2019, that figure had dropped to 39.6%, thanks to the spread of SMS firewalls and other control systems.
The same research also estimated that grey routes cost mobile carriers $37.1 billion in lost revenue between 2020 and 2024 — roughly $7.69 billion a year.
For a business, the problem shows up in delivery quality. A route that works today may stop getting through after a carrier updates its firewall.
That's why an unusually low SMS price warrants extra scrutiny. It's worth asking the provider about the route type, DLR, and delivery specifics for the GEO you need.
Delivery rate is easier to grasp in absolute numbers. That makes the business impact clearer.
Say a service sends 100,000 SMS a month.
At a 98% delivery rate, customers receive 98,000 messages. At 92%, only 92,000 get through. That's a difference of 6,000 undelivered SMS in a single month.
If this is a marketing campaign, the business loses part of its potential reach. If it's an OTP, the problem hits earlier – a user may fail to complete registration, a payment, or a login.
For a service sending 500,000 OTPs a month, even a single percentage point of delivery rate equals 5,000 messages. So the difference between 97% and 98% may look small in a report, but in absolute terms it's thousands of customer sessions.
Diagnosing this requires more than looking at how many messages were sent. You need DLRs, delivery receipts, which show the actual result of processing an SMS.
Depending on the platform, statuses may vary, but the logic usually includes delivered, failed, expired, rejected, or unknown.
A "sent" status just means the platform passed the message along the route. It doesn't confirm the SMS actually reached the customer's phone.
That's why a report like:
100,000 sent
tells you almost nothing about delivery quality.
A far more useful breakdown looks like:
100,000 sent → 97,200 delivered → 1,600 failed → 1,200 expired/unknown.
From there, this data needs to be broken down by country and carrier.
If the overall delivery rate is 97.2%, but it dropped to 82% in one GEO, the average is masking a local problem.

Rather than starting by editing the SMS text, start by localizing the problem. That means comparing delivery rate across time periods, countries, carriers, and Sender IDs.
For example, yesterday Poland delivered 98% of messages, and today it's 83%. Other countries haven't changed. That already narrows the search for the cause significantly.
Check:
which Sender ID was used;
whether it's registered in that specific country;
whether the route changed;
what DLRs the carrier is returning;
whether the drop affects one carrier or the entire GEO;
whether traffic volume changed sharply;
whether the content meets local requirements;
whether there are issues with URLs;
whether the TTL expired for time-sensitive messages.
For OTPs, it's also worth tracking delivery time. A code that arrives after 15 minutes may technically be marked delivered, but for the user it's already useless.
Before setting up SMS, it's worth defining the countries, message type, and expected volume. OTPs, transactional messages, and marketing campaigns can have different requirements for Sender ID, registration, and throughput.
DID Global helps organize SMS traffic for specific GEOs and check sender requirements. For international businesses, this matters especially because A2P rules in the US, EU countries, and other markets differ.
After launch, it's not just the price per SMS that needs monitoring. The key metrics for a business are delivery rate, DLR by country and carrier, delivery time, and the share of failed messages.
For example, a route priced at $0.04 with a 98% delivery rate can turn out cheaper than a route at $0.03 with an 85% delivery rate. At 100,000 SMS, the first route delivers 98,000 messages and costs $4,000. The second costs $3,000 but delivers only 85,000.
If you calculate the cost per delivered SMS, you get approximately $0.0408 for the first option and $0.0353 for the second. That's why, for OTPs and transactional messages, you need to look even further: how many users completed the intended action after delivery, and how much a failed delivery costs for that specific business process.
To select SMS routes through DID Global, give your manager the countries you need, expected volume, and message type. Before launch, you can check Sender ID and GEO-specific requirements, and after launch, monitor delivery rate against actual traffic.

A customer taps "Get code," but the SMS never arrives. A minute later they request the code again, then once more. From the user's side, it looks like one undelivered SMS. From the service's side, that's already three messages instead of one, an incomplete authentication, and the risk of losing the customer before they even log in. The scale of the problem is much bigger than that. According to...
A phone lead can be highly valuable to a business, but without attribution, a marketer only sees the fact that a call happened. Invoca's 2026 study analyzed over 70 million phone conversations across 10 industries. 38% of calls answered by a human were leads, and 42% of those leads converted during the call. In DTC eCommerce, phone lead conversion reached 54%. So leaving calls out of ad analytics...

A phone attack can start with a single compromised SIP account. An attacker gains access to outbound calling, routes traffic to expensive international or premium destinations, and the company only notices the problem once the bill spikes. For a call center, there's another scenario: an attack overloads the SIP server, leaving agents unable to receive customer calls. The scale of the problem goes...