--- title: "The state of business messaging, 2026" summary: "Four changes that landed between 2024 and 2026 (per-message WhatsApp billing, stricter sender registration, RCS on both major phone platforms, and AI disclosure) and what each one does to a programme built before them." canonical: https://cpaas.co/en/learn/the-state-of-business-messaging-2026 kind: report depth: advanced origin: original published: 2026-10-13T16:26:18.899Z updated: 2026-10-14T16:26:19.573Z topics: ["Market", "Messaging", "A2P"] language: en --- # The state of business messaging, 2026 ## Why this matters 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. ## 1. WhatsApp bills per message 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](/en/learn/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](/en/learn/the-24-hour-window). ```diagram:compare | Conversation-based, from 2022 | Per message, from 1 July 2025 The unit you pay for | A 24-hour conversation | Each delivered template Marketing and authentication templates | Inside a conversation's charge | Charged per delivered template Utility templates inside an open service window | Inside a conversation's charge | Free from July 2025; charged again from 1 October 2026 A cost model that counts conversations | Described the invoice | No longer does > Rates vary by country and category and have changed more than once since. Meta's pricing documentation is the source of truth. ``` ## 2. Sender registration became a precondition, in more places 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](/en/learn/sender-registration-around-the-world). ```diagram:matrix # Registration before the first send United States | Brand and campaign registered with The Campaign Registry for 10DLC; unregistered traffic moved from surcharged to blocked through 2023–2025. Singapore | Alphanumeric sender IDs must be registered, from 31 January 2023. Ireland | ComReg's mandatory SMS Sender ID Registry; unregistered IDs labelled "Likely Scam" from 3 July 2025. India | Senders, headers and message templates registered on DLT platforms, for years now. > Vetting can take days to several weeks, and a rejection means resubmission. ``` ## 3. RCS is on both major phone platforms 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](/en/learn/rcs-adoption-after-ios). ## 4. AI disclosure became a legal requirement in the EU 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](/en/learn/ai-act-article-50-for-messaging). ## The four changes on one timeline Read together, the sequence has a direction: each one moves cost, accountability or evidence from the platform toward 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. 2023–2025 | US blocks unregistered business texting | 10DLC registration and toll-free verification move from launch task to prerequisite. Jul 2025 | WhatsApp bills per message | Conversation-based cost models stop describing the invoice you receive. Jul 2025 | Ireland labels unregistered sender IDs | One of several countries moving from voluntary to mandatory sender registration. Mar 2026 | RCS Universal Profile 4.0 | In-thread video and richer formatting; 4.1 follows in July on encryption interoperability. Aug 2026 | EU AI Act Article 50 applies | Disclosure of automated interaction becomes a legal obligation, not a brand choice. > Several dates in under two years. A programme designed before the first one may be wrong about pricing, wrong about launch sequencing, and, in the EU, non-compliant. ``` ## What each one does to a programme built before it | Change | Where it applies | What it makes out of date | What to do now | |---|---|---|---| | Per-message WhatsApp billing | Worldwide | Cost models that count conversations | Re-model on the current rate card for your countries and categories | | Stricter sender registration | US, India, Singapore, Ireland, Gulf states and others | Plans that register after launch | Register during development; allow weeks, and plan for a resubmission | | RCS on both major phone platforms | Market by market | "RCS is Android only" | Ask for reach per market; keep SMS as a designed path | | AI disclosure | EU (others vary) | Bots that never say they are bots | One clear line at the first interaction, recorded beside consent | 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. ## What did not change 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](/en/learn/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. ```diagram:checklist # Still true after all four changes Delivery rate measures the network | Not your programme Consent is per channel and per purpose | A single yes/no field still cannot express it Messages customers start are cheapest and least constrained | Earned inbound still tends to beat bought outbound Identity across channels is the hard part | No vendor solves it for you ``` ## The practical implication 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. ```diagram:steps # Where a review of an older programme starts The billing model | One of the two likely to cost money first The registration requirement | The other AI disclosure | If you serve customers in the EU ``` ## 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 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. ## Where to go next - [What the analysts disagree about](/en/learn/what-analysts-disagree-about): why published market sizes differ by a factor of two. - [GSMA on RCS, encryption and the future of operator messaging](/en/learn/the-mobile-economy-a2p): the primary sources behind the RCS section. ## Sources [^1]: [Pricing on the WhatsApp Business Platform](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing) — Meta for Developers [^2]: [Updates to WhatsApp Business Platform pricing](https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing/) — Meta for Developers [^3]: [Upcoming pricing updates for Meta Business Agent, service and utility messages](https://developers.facebook.com/documentation/business-messaging/whatsapp/pricing/non-template-messages) — Meta for Developers, 2026-09-30 [^4]: [The Campaign Registry](https://www.campaignregistry.com/) — The Campaign Registry [^5]: [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 [^6]: [SMS Sender ID Registry: frequently asked questions](https://www.sgnic.sg/faq/sms-sender-id-registry) — Singapore Network Information Centre (SGNIC) [^7]: [ComReg launches registry for organisations to help prevent SMS text message scams in Ireland](https://www.comreg.ie/ga/comreg-launches-registry-for-organisations-to-help-prevent-sms-text-message-scams-in-ireland/) — ComReg, 4 June 2025 [^8]: [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 [^9]: [From Rich Text to Video: RCS Universal Profile 4.0 has arrived](https://www.gsma.com/newsroom/article/from-rich-text-to-video-rcs-universal-profile-4-0-has-arrived/) — GSMA, March 2026 [^10]: [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, July 2026 [^11]: [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, 31 July 2026 --- 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.