Quick answer: The EU interoperability push is the Digital Markets Act's Article 7, an obligation placed on designated gatekeeper messaging apps to interoperate with smaller messaging services on a staged timetable. It is not an obligation on carriers, it does not mention RCS, and it creates no cross-app right for business senders. The European RCS story buyers actually see, Apple's iPhone base receiving RCS on enabled carriers, was shipped by carriers adopting a GSMA standard, documented with dates in the Apple-iOS reach post. What the mandate changes for business messaging is therefore narrower and more specific than the headlines: it puts cross-app person-to-person reach on a legal calendar, and it makes the open, carrier-delivered rail that is RCS more strategically central. The channel-priority math and the levers you control are mapped below, with a dated public watchlist at the end.
What the EU interoperability push actually mandates
Three settled facts anchor everything else in this post, and each one is a matter of public record rather than industry rumor.
Fact one: the obligation sits on designated gatekeeper messaging apps, not on carriers. Regulation (EU) 2022/1925, the Digital Markets Act, entered into force in November 2022. Its Article 7 requires a designated gatekeeper's number-independent interpersonal communications services to make basic capabilities interoperable with smaller qualifying messaging services that request it. The addressees are the app providers the Commission designated. Meta's WhatsApp and Messenger carry that designation. No article of the DMA orders a mobile carrier to switch on any messaging technology, and none of it sets or caps messaging prices.
Fact two: Apple's iMessage was excluded, so Apple-side interoperability was never mandated. On 13 February 2024 the Commission concluded iMessage did not meet the gatekeeper threshold and excluded it from designation. Any reading of "the EU made iPhones interoperate" is wrong on its face: RCS arriving on European iPhones is a carrier and standards story, not a Brussels order, and not an Apple concession to regulators either.
Fact three: the mandate is staged by implementing act, and its current scope is a compliance question to read off the sources, not a headline. Article 7 sequences obligations, basic one-to-one messaging first, then group messaging, then further capabilities, with the technical conditions set out in a Commission implementing act. Where that sequence stands on any given date, including whether group messaging ships cross-platform and on what terms, is published compliance status. This post does not freeze that status; the watchlist at the end names the two public sources that carry it, because a compliance calendar moves and a blog date does not.
What the mandate does not do is equally load-bearing for a buyer:
- It creates no right for business senders to deliver across apps. The obligation runs between interpersonal messaging services. Business API traffic, WhatsApp Business Platform included, is not a qualifying smaller service requesting interop. Whether business messages ever ride interoperable rails is an open regulatory question, not a shipped capability anywhere in the EU as of this writing.
- It does not govern RCS. RCS interoperation between carriers is not DMA interoperability; it predates the DMA and runs on a different mechanism entirely, the GSMA standards process below.
- It does not set or constrain what you pay per message. Verified-agent RCS rates come from RBM hosts and carrier rate cards, and WhatsApp rates come from Meta's published per-country cards, as priced in the per-message pricing shift explainer. Brussels is not a party to either.
The precise claim to hold in your head: the EU mandated that a small number of giant consumer apps open basic person-to-person messaging to smaller apps, on a staged legal calendar. Everything else in the "EU interoperability" headline space is either that calendar's future stages, or something else entirely.
What is voluntary GSMA work, and why the distinction matters
The second engine behind European RCS is not law but standard: the GSMA's Universal Profile, the single specification carriers and handset vendors adopt to make RCS one channel instead of a bilateral peering maze. Three strands matter for a buyer.
The Universal Profile capability line. Consumer RCS capabilities, richer cards, deeper links, the Universal Profile 3.0 direction documented in the carrier and OS rollout explainer, ship when vendors and carriers ship them. Adoption is individual and voluntary per carrier, which is exactly why coverage is a mosaic rather than a mandate would produce a uniform floor.
The RCS Business Messaging verification framework. Verified agents, branded sender profiles, and template categories are GSMA-framework constructs operated through RBM hosts and carrier validators, per the H2 2026 consolidated explainer. A brand's ability to land rich in a European inbox rides this framework, not the DMA.
Open Gateway and the CAMARA APIs. The operator-side API program, number verification, device status, quality-on-demand, is a separate voluntary carrier initiative that complements messaging rather than mandating it. The Open Gateway / CAMARA explainer covers what those APIs do for business messaging today.
The distinction matters for planning because the two engines move on different clocks and answer to different triggers. A DMA obligation advances when the Commission advances it, through implementing acts and compliance decisions, and its dates are legal dates. A GSMA capability advances when carriers and vendors ship it, and its dates are rollout dates you can observe in the market. Budget against what you can observe; watch what you cannot.
The shipped baseline: what an iPhone recipient in Europe already sees
Before interoperability enters the picture at all, the European baseline is already different from two years ago, and it is shipped, not promised.
Apple shipped consumer RCS in iOS 18 in September 2024. Through 2025 and 2026, carriers in the UK and major Western European markets, Germany, France, Spain, and Italy among them, enabled RCS for their iPhone subscriber bases, the same market-by-market pattern as the US turns documented in the H2 2026 update. On an enabled carrier, Apple Messages for Business delivers a verified brand agent into the native iPhone inbox with rich cards; on a carrier that has not enabled it, the same send degrades to SMS, often inside the same country. The durable operator rule from the rollout explainer holds in Europe unchanged: OS support sets the ceiling, the destination carrier sets the floor.
Two consequences follow for the mandate discussion. First, a large share of the "interop reach" buyers want in Europe already exists without any mandate, carried by carriers adopting an open standard on both operating systems. Second, the remaining gap, carrier B in the same country degrading to SMS, is a registration and enablement gap that Article 7 does not close, because Article 7 was never addressed to carriers. The mechanism that closes it is the one the iOS reach post names: per-recipient capability probing plus a tenant-owned fallback chain.
What interoperability adds on top of the shipped baseline
Holding the baseline fixed, the DMA's interoperability calendar adds three things, in descending order of certainty.
Certainty one: cross-app person-to-person reach is on a legal calendar. A user of a smaller EU messaging service has a legal basis to exchange basic messages with WhatsApp and Messenger contacts. For a business messaging buyer this is indirect but real: the premise "my customers live inside one walled app" weakens at the person-to-person layer, and with it the argument that any single app's installed base is a permanent moat.
Certainty two: the open rail gains strategic centrality. If app walls thin at the person-to-person layer, the carrier-delivered, vendor-neutral rail that reaches the native inbox on both operating systems becomes more, not less, central to business reach. RCS is that rail. This is an argument about direction, not a claim that any specific business capability ships on a date.
Open question: whether business traffic ever rides interoperable rails. Nothing in the staged obligation as written covers business-originated messaging, and no EU-wide mechanism publishes business interoperable delivery as of this writing. Treat any vendor claim that DMA interoperability "opens WhatsApp's audience to your campaigns" as unsupported until a dated public source says otherwise. The watchlist's first two rows exist precisely to catch the day that changes.
What interoperability does not add: a uniform European RCS floor, a change to per-message billing, a change to template verification, or a substitute for SMS fallback. All four remain exactly as they are on the shipped baseline.
The channel-priority math after the mandates
The working math, carried in full in the channel fallback matrix, is per market and per use case:
- WhatsApp keeps its position where installed-base depth and conversation economics win: per-conversation category billing with a free customer-initiated service lane, inside an app your recipient already uses. Its moat argument weakens at the person-to-person layer as interop stages land, but its business API, pricing model, and installed reach are untouched by Article 7 as written.
- RCS keeps and strengthens its position as the native-inbox rich channel on enabled carriers: per-message verified-agent billing, verified branding, rich cards on both operating systems per the adoption market-state post. The interoperability direction described above points toward greater, not lesser, reliance on the open rail.
- SMS keeps its position as the destination-universal floor under both, unchanged by any scenario in this post.
The decision rule therefore does not flip; it tightens. Probe the actual recipient segment per market before allocating budget, because the carrier floor, not the headline, prices your campaign, per the RCS vs WhatsApp guide. Keep the fallback chain configured so every interoperability future, mandated, voluntary, or stalled, delivers to the whole segment rather than the capable slice. The one planning change: add the two app-side compliance sources to your quarterly review, because a business-traffic extension of interop is the single scenario that would move WhatsApp reach numbers materially, and it is exactly the scenario the current record does not confirm.
Tenant-owned levers on Devotel Orbit
Whatever the calendar does, the levers below are tenant-owned configuration on Devotel Orbit today, and they are the posture that makes every interoperability future cheap to absorb.
- Per-recipient capability probing with an org-level RCS-to-SMS fallback. Orbit checks whether a recipient can receive RCS before the send and retries on SMS automatically on capability failure, with the downgrade visible in per-channel analytics. On a carrier mosaic that regulation will not flatten, this is the mechanism that converts a patchwork floor into a delivered audience. The pattern is documented in the RCS fallback strategy post and configured from the same account as every other channel.
- Template governance with tracked approval. Cards, carousels, and suggested actions are registered content types; submission and approval status live in the channel's template manager, and verification re-audits on drift. European carrier quality gates read that record, so governance is a deliverability control, not paperwork, per the launch checklist.
- Per-message pricing shift planning. RCS bills per delivered message at the host's per-market rate card with no free lane; planning the verified-agent mix and the fallback share against your destination mix is the budget discipline, priced in full in the pricing shift explainer.
- A tenant-owned consent posture. Opt-in evidence, quiet hours, opt-out handling, and retention are configured by your tenant for your jurisdictions, independent of whichever regulatory wave is cresting. European consent enforcement, Germany's UWG practice included, reads your consent record first; the tenant-owned controls are the durable answer regardless of what the DMA calendar does next.
The pattern is the same in each case: the mandate moves on a legal clock you do not control, and the levers sit on a clock you do.
A buyer's 90-day watchlist
Every row below is a dated public source, not a prediction. Re-run this list each quarter; the article body above states only what these sources settled as of 26 October 2026.
- EUR-Lex, Regulation (EU) 2022/1925, Article 7, plus the Commission's Article 7 implementing act and compliance decisions. In force November 2022; iMessage excluded from designation on 13 February 2024; WhatsApp and Messenger designated. Watch for: any implementing act amendment, compliance decision, or staged-capability date that touches group messaging scope, and anything extending obligations toward business-originated traffic.
- Meta's DMA interoperability publications for WhatsApp and Messenger. The designated gatekeeper's own dated statements are the authoritative record of which interop stages have shipped to EU users. Watch for: a published date for cross-platform group messaging at scale, and any business-traffic position.
- European carrier RCS enablement announcements, per carrier. The dated record of 2025 to 2026 enablement across the UK, Germany, France, Spain, and Italy is aggregated in the H2 2026 update; the primary sources are the carriers' own press and coverage pages. Watch for: enablement on carriers your top segments ride, because each one raises your per-market rich floor.
- GSMA Universal Profile and RBM releases, plus Open Gateway carrier adoption lists. Voluntary-standard strand; handset-capable capability sets and operator API coverage move here. Watch for: capability your templates plan to use shipping into the installed base, and new markets in Open Gateway coverage per the Open Gateway explainer.
- Carrier quality-gate and sweep cycles. The enforcement cadence that re-audits verified agents and templates, documented in the H2 2026 sweep coverage. Watch for: re-verification requirements on your agents after any brand or route change.
- National consent and sender-ID enforcement in your markets. Germany's UWG consent practice and the Q4 2026 enforcement calendar are the nearest dated examples in the Germany A2P rules post and the carrier and regulatory round-up. Watch for: new national windows that change the consent evidence your sends must carry.
Frequently asked questions
Does the EU mandate carriers to deliver RCS?
No. The DMA's interoperability article addresses designated gatekeeper messaging apps; no EU instrument orders a carrier to enable RCS. European carrier enablement is carriers adopting a GSMA standard, market by market, which is why coverage varies by carrier within a country and why per-recipient capability probing plus SMS fallback remain the operating posture.
Will my business messages reach non-WhatsApp apps because of the DMA?
Not on the current record. The staged Article 7 obligation runs between interpersonal messaging services; business API traffic is not within the obligation as written, and no EU-wide business interoperable delivery is published as of this writing. Watchlist rows one and two carry the sources that would change that answer.
Does the interoperability push change what I pay per RCS message?
No. RCS per-message verified-agent billing comes from RBM hosts and per-carrier rate cards, and WhatsApp category billing comes from Meta's published cards. Neither pricing surface is a DMA subject. The budget work is the per-market mix and fallback share, priced in the pricing shift explainer.
What should I do now, given the mandates?
Hold the shipped posture and run the watchlist. Probe recipients per market, keep the RCS-to-SMS fallback chain configured and visible in analytics, keep templates governed and re-verified on drift, and keep consent evidence tenant-owned per jurisdiction. The levers section above maps each to Devotel Orbit configuration; the launch checklist walks the sequence end to end.
The takeaway
The EU interoperability push is a real mandate with a narrow addressee: designated gatekeeper apps opening basic person-to-person messaging on a staged legal calendar, with iMessage excluded and business traffic outside the obligation as written. The European RCS reach buyers already benefit from was shipped by carriers on a voluntary GSMA standard, not by Brussels. Plan on what you can observe: the carrier floor per market, per-message economics, template governance, and a tenant-owned fallback and consent posture. Watch what you cannot: the two compliance sources that will say, on a dated public record, when group messaging and any business-traffic extension actually ship.
Resources
- Apple's RCS Support Changed Business Messaging in 2026, the shipped, dated Apple-side state.
- RCS Business Messaging in 2026 H2, the consolidated carrier mosaic and verified-agent economics.
- Channel Fallback Matrix: WhatsApp, RCS, SMS, the failure shapes and the cost math.
- RCS Per-Message and Template Pricing Shift, the billing model in full.
- RCS for Business Launch Checklist 2026, the operator's go-live sequence.
- GSMA Open Gateway and CAMARA, Explained, the voluntary operator-API strand.
Published 26 October 2026.