--- title: "The state of business messaging, 2026" summary: "Four changes that landed between 2025 and 2026 — per-message billing, mandatory registration, RCS on every modern handset, and AI disclosure — and what each one does to a programme built before them." canonical: https://cpaas.co/en/insights/the-state-of-business-messaging-2026 kind: report depth: advanced origin: original published: 2026-09-07T11:34:07.986Z updated: 2026-09-08T11:34:08.201Z topics: ["Market", "Messaging", "A2P"] language: en --- # The state of business messaging, 2026 Most published guidance on business messaging describes a world that no longer exists. Four specific changes landed in the last two years, and each one invalidates advice that was correct when it was written. ## 1. WhatsApp bills per message Meta moved the WhatsApp Business Platform to per-message billing on 1 July 2025, replacing the conversation-based model that had defined the economics since 2022. Utility templates sent inside an open customer service window became free for all businesses at the same time. **What this invalidates:** every cost model built on conversation counts, and every piece of advice that treats a 24-hour conversation as a unit you are buying. The rate card and the rules about what is billable have changed more than once; treat the pricing documentation as the source of truth rather than any secondary summary, this one included. ## 2. Unregistered US traffic is blocked, not throttled Since February 2025, major US carriers block A2P traffic from unregistered 10DLC numbers outright. **What this invalidates:** any launch plan that treats registration as a post-launch task, and any advice describing a degraded-but-functional path for unregistered senders. There is no such path. Campaign vetting can take around ten business days, and a rejection means resubmission. ## 3. RCS is on the phones Apple added RCS in iOS 18, released September 2024. The GSMA finalised Universal Profile 4.0 in March 2026, adding in-thread video calling and richer formatting, with 4.1 following on secure messaging foundations and published work on encryption. **What this invalidates:** the standing dismissal of RCS as Android-only. Reach is now a question about operator deployment rather than handset support. **What it does not change:** it remains carrier-mediated A2P with registration and content rules, and every deployment still needs an SMS fallback designed as a first-class path. ## 4. AI disclosure became a legal requirement The EU AI Act's transparency obligations began enforcement on 2 August 2026. People interacting with an AI system must be told, clearly and at first interaction, in a form that cannot easily be overlooked. **What this invalidates:** automated support built on the assumption that disclosure is a brand choice. It is now a legal one in the EU, and it stacks with the GDPR rather than replacing any part of it. ## What did not change Worth stating, because the noise around the above obscures it: - **Delivery rate still measures the network, not your programme.** - **Consent is still per channel and per purpose**, and a single boolean still cannot express it. - **The inbound direction is still the cheapest and least constrained**, and programmes that earn inbound contact still outperform programmes that buy outbound reach. - **Identity across channels is still the hard part**, and no vendor has solved it for you. The noise around four simultaneous changes obscures the durable part, and the durable part is where programmes actually succeed or fail. Delivery rate still measures the network rather than your programme. Consent is still per channel and per purpose, and it still does not travel between them. The layer above transport — orchestration, identity, evidence — is still where switching is expensive and where every serious difference between vendors lives. None of the four changes above touches any of that. A team that got the durable part right in 2023 has four adjustments to make. A team that did not has a rebuild, and the four changes are merely what made it visible. ## The practical implication If your messaging programme was designed before mid-2025 and has not been revisited, at least three of its assumptions are now wrong — and the two that will cost you money first are the billing model and the registration requirement. Start there. ## The four changes on one timeline Read together rather than separately, the sequence has a direction: every one of these moves cost, accountability or evidence from the platform onto the sender. ```diagram:timeline # What landed, and when Sep 2024 | RCS arrives in iOS 18 | Reach stops being a handset question and becomes an operator-deployment question. Feb 2025 | US carriers block unregistered 10DLC | No degraded path. Registration moves from launch task to prerequisite. Jul 2025 | WhatsApp bills per message | Conversation-based cost models stop describing the invoice you receive. Mar 2026 | Universal Profile 4.0 | In-thread video and richer formatting; 4.1 follows on secure messaging foundations. Aug 2026 | EU AI Act Article 50 enforced | Disclosure of automated interaction becomes a legal obligation, not a brand choice. > Five dates in under two years. A programme designed before the first one is wrong about pricing, wrong about launch sequencing, and now non-compliant in the EU. ``` ## What each one does to a programme built before it ```diagram:compare Change | What it invalidates | What to do now Per-message billing | Cost models counting conversations; advice treating the 24-hour window as a unit you buy | Re-model on the current rate card; treat the pricing docs as the source of truth Registration enforcement | Any plan with registration after launch, or assuming a throttled fallback | Register during development; budget ten business days and a possible resubmission RCS on every handset | The dismissal of RCS as Android-only | Re-assess by operator deployment; keep SMS as a designed path, not a fallback afterthought AI disclosure | Automated support assuming disclosure is optional | One line, first interaction, stored next to consent > Only the fourth row is a compliance obligation. The other three are ways of being wrong about your own numbers. ``` ## What to take away Four changes, one direction: cost, accountability and evidence moved toward the sender. Re-model the economics, move registration before launch, treat RCS as a capability rather than a channel, and disclose automation. Then check that the parts nobody changed are still right, because that is where the expensive problems are. ## Sources - [Updates to WhatsApp Business Platform pricing](https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/) — Meta for Developers - [Ten-Digit Long Code (10DLC) Registration Guidelines](https://learn.microsoft.com/en-us/azure/communication-services/concepts/sms/ten-digit-long-code-guidelines) — Microsoft Learn - [RCS Now in iOS: a New Chapter for Mobile Messaging](https://www.gsma.com/newsroom/article/rcs-nowin-ios-a-new-chapter-for-mobile-messaging/) — GSMA - [RCS Universal Profile 4.1: Stronger foundations for secure messaging](https://www.gsma.com/newsroom/article/rcs-universal-profile-4-1-stronger-foundations-for-secure-messaging/) — GSMA - [Commission starts enforcing AI Act rules and new transparency requirements on 2 August](https://digital-strategy.ec.europa.eu/en/news/commission-starts-enforcing-ai-act-rules-and-new-transparency-requirements-2-august) — European Commission --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.