The state of business messaging, 2026

If your business sends text messages, WhatsApp messages or automated chat replies, the rules and prices underneath them changed a lot between late 2024 and the second half of 2026. Much of the guidance you will find online, including vendor blog posts and older internal documents, describes the world before these changes. This report summarises the four that matter most, what each one makes out of date, and what to do now. It is written for a global audience; where a change applies only to one country or region, it says so.

Meta moved the WhatsApp Business Platform to per-message pricing on 1 July 2025, replacing the conversation-based model it had used since 2022. Businesses now pay for each delivered marketing or authentication template, and for utility templates sent outside an open customer service window; utility templates sent inside the window became free at the same time. That part did not last: since 1 October 2026 Meta charges for utility templates sent inside the window as well, and for free-form replies (service messages) after 1,000 free per business phone number each month. WhatsApp 101 sets out the current rules.

What this invalidates: every cost model built on conversation counts, and every piece of advice that treats a 24-hour conversation as the unit you are buying. Rates vary by country and category and have changed more than once since; treat Meta's pricing documentation as the source of truth rather than any secondary summary, this one included. See the 24-hour window.

In the United States, the major carriers rely on The Campaign Registry for 10DLC (ordinary ten-digit numbers used for business texting): each brand and each use case ("campaign") must be registered. Through 2023 to 2025, carriers and platforms moved from filtering and surcharging unregistered traffic to blocking it. Toll-free numbers similarly require verification before they can send.

The same direction is visible elsewhere. Singapore made registration of alphanumeric sender IDs mandatory from 31 January 2023. Ireland's regulator ComReg launched a mandatory SMS Sender ID Registry in 2025, with unregistered sender IDs labelled "Likely Scam" from 3 July 2025. India has required registration of senders, headers and message templates on its DLT platforms for years, and several Gulf states pre-approve sender IDs.

What this invalidates: any launch plan that treats registration as a post-launch task, and any advice describing a degraded-but-working path for unregistered senders. Vetting can take from days to several weeks depending on the country and the case, and a rejection means resubmission. See sender registration around the world.

Apple added RCS in iOS 18, released in September 2024. The GSMA published RCS Universal Profile 4.0 in March 2026, adding video calls started from inside a conversation, richer text formatting, and business features such as video inside rich cards. Universal Profile 4.1 followed in July 2026, focused on making end-to-end encryption work between different apps.

What this invalidates: the old dismissal of RCS as "Android only". Reach is now mainly a question of operator deployment and sender verification in each market, not of which phone people own.

What it does not change: RCS business messaging is still carried by operators, with registration and content rules, and a published specification is not the same as a feature on people's phones. Every deployment still needs an SMS fallback designed as a first-class path. See RCS after iOS.

The EU AI Act's transparency obligations apply from 2 August 2026, and the European Commission announced it would start enforcing them from that date. People interacting directly with an AI system must be told, clearly and at the latest at their first interaction, unless it is obvious.

What this invalidates: automated support built on the assumption that disclosure is a brand choice. In the EU it is now a legal one, and it applies alongside the GDPR rather than replacing any part of it. Other jurisdictions have their own, narrower rules; check where your customers are. See Article 50 for messaging teams.

Read together, the sequence has a direction: each one moves cost, accountability or evidence from the platform toward the sender.

Only the last row is directly a legal duty in itself; the registration rules are enforced by carriers and regulators, and the other two are ways of being wrong about your own numbers.

Worth stating, because the noise around the above obscures it:

• Delivery rate still measures the network, not your programme. See delivery rate is not a result.
• Consent is still per channel and per purpose, and a single yes/no field still cannot express it.
• Messages customers start are still the cheapest and least constrained, and programmes that earn inbound contact still tend to outperform programmes that buy outbound reach.
• Identity across channels is still the hard part, and no vendor solves it for you.

None of the four changes touches any of that. A team that got these durable parts right has four adjustments to make. A team that did not may face a rebuild, and the four changes are simply what made it visible.

If your messaging programme was designed before mid-2025 and has not been revisited, several of its assumptions are probably wrong, and the two likely to cost money first are the billing model and the registration requirement. Start there, then check your AI disclosure if you serve customers in the EU.

Four changes, one direction: cost, accountability and evidence moved toward the sender. Re-model the economics, move registration before launch, treat RCS as an upgrade that depends on each market, and disclose automation. Then check that the parts nobody changed are still right, because that is where the expensive problems usually are.

• What the analysts disagree about: why published market sizes differ by a factor of two.
• GSMA on RCS, encryption and the future of operator messaging: the primary sources behind the RCS section.