Messaging Infrastructure: What Changed in 2025–26

A snapshot, not a forecast

This isn't a "trends to watch" piece. It's a snapshot of what's actually changed in messaging infrastructure over the last 18 months and what it means operationally.

1. 10DLC reached steady state — and it's expensive

The US 10DLC migration is now complete. Unregistered traffic is filtered or surcharged across all major carriers. Practical implications:

• Sender ID changes are now 4–6 week projects, not config changes
• Per-message surcharges have stabilised at $0.001–0.003 above the base rate, charged by the carriers, not the vendor
• Throughput tiers are tied to vetted brand status; un-vetted brands are capped at 75 segments/minute regardless of vendor

Operationally: maintain pre-registered backup sender IDs in case of campaign rejection or sudden filtering. Don't assume you can rotate quickly.

2. RCS Business crossed the deployment threshold

RCS Business Messaging is now a viable channel for the first time. Apple's adoption in late 2024 closed the device gap. Operator support across the US, UK, France, Germany, Spain, India, and Brazil is sufficient for production use.

What this changes:

• Rich content (cards, buttons, suggested replies) is now a default option for transactional flows
• Read receipts give you a real fallback signal — RCS-then-SMS chains are operationally feasible
• Brand verification is required and adds 2–4 weeks to onboarding
• Per-message cost is similar to or slightly above SMS in most markets

What it doesn't change:

• For OTPs, SMS remains the right primary channel — RCS adds latency variance you can't afford
• Reach is still imperfect; expect 60–85% RCS-capable users in mature markets, lower elsewhere

3. WhatsApp Business pricing got more nuanced

Meta's category-based pricing model is now fully in effect. Prices vary significantly by:

• Country (10–15x range from cheapest to most expensive)
• Category (utility, authentication, marketing, service)
• Conversation type (template-initiated vs user-initiated)

The "free 1000 conversations/month" is gone. New free-conversation entitlements only apply to user-initiated service conversations.

Operational implications:

• WhatsApp economics now require category-aware routing logic
• Marketing categories are 3–5x more expensive than utility categories — content classification matters for cost
• Authentication-category templates are the right home for OTPs only in markets where carrier SMS is unreliable or expensive

4. Europe: GDPR enforcement on messaging metadata

Several EU DPA rulings in 2025 made it clear that messaging metadata (delivery times, click events, read receipts) is personal data when associated with a contactable person. Practical effect:

• Vendor contracts now need explicit DPIAs covering metadata
• Cross-border transfer concerns apply to vendors with US-based control planes
• Retention windows for delivery logs are being scrutinised — shorter, documented windows are becoming the defensible default; multi-year is increasingly hard to justify

5. LATAM: WhatsApp dominance, SMS price volatility

In Brazil, Mexico, Colombia, Argentina, WhatsApp is now the de facto channel for most B2C communication outside of OTPs. SMS pricing in these markets has become more volatile as operators adjust to lower volumes.

Operationally:

• Build for a WhatsApp-primary, SMS-fallback chain in LATAM consumer flows
• Treat SMS as the OTP channel and the multi-factor backup, not the primary marketing channel
• Expect operator-level pricing changes with 30–60 days notice

6. UK and Ireland: regulator focus on consent records

Ofcom and the Irish DPC have both signalled increased focus on opt-in evidence. Vendors are increasingly asking customers to demonstrate the consent record before activating new sender IDs.

This isn't a new requirement — it's tighter enforcement. Maintain a queryable consent log per recipient with timestamp and source.

What this means for your roadmap

Three things worth prioritising in the next 12 months:

1. A category-aware routing layer that can handle WhatsApp's pricing model and the transactional/marketing split on RCS and SMS
2. A consent log integrated with your messaging API that vendors can query during onboarding
3. Per-market routing rules that reflect the rapidly diverging economics across regions

If your current setup treats messaging as a single global pipeline, you're leaving money and reliability on the table.

---

If you're planning a 2026 messaging architecture refresh, book a 30-minute messaging review. We'll share the patterns we're seeing across our customers.