Two years ago, a marketing team planning a rich messaging campaign in the UK had to write off half of its audience before the first send. Android users got the carousel, the buttons and the branded sender. iPhone users got a plain text with a link. Splitting by operating system was a workaround, not a strategy.
Apple RCS changed that arithmetic. RCS on iPhone arrived with iOS 18 in September 2024, business messaging followed in iOS 18.1, and in May 2026 iOS 26.5 added encrypted RCS in beta. This explainer covers what is live today, what changed for senders, and what to expect from EU and UK carriers before you rebuild your channel plan.
Yes. iPhone supports RCS natively in the Messages app on iOS 18 and later, and businesses can reach iPhone users through RCS for Business on iOS 18.1 and later, on carriers that have enabled it. The catch is the last clause. Apple switches RCS on per operator through a carrier bundle. Whether a given iPhone can receive your message depends on the SIM inside it, not only on the iOS version.
Three milestones matter. iOS 18 brought person-to-person RCS: high-resolution media, read receipts, typing indicators. iOS 18.1 opened RCS for Business, so verified brand messages with rich cards and suggested replies could land on iPhone. iOS 26.5 added E2EE for RCS in beta, built on GSMA Universal Profile 3.0 and the Messaging Layer Security (MLS) protocol. Encryption applies only when both carriers in the conversation support the new profile (MacRumors, 2026).
iOS 27, released on 14 September 2026, did not change reach; it added inline replies and emoji reactions in cross-platform threads. Apple RCS has been ready for business use since late 2024. What is still moving is the carrier map.
RCS stopped being an Android-only channel and became a device-agnostic one, with the same fallback logic underneath. This is what a sender gets on an iPhone today versus before Apple RCS:
| What | Before Apple RCS (until Sept 2024) | After Apple RCS (today) |
|---|---|---|
| Reach on iPhone | SMS only: plain text, 160 characters, no media | RCS rich messages on iOS 18.1+ with a supported carrier; SMS for the rest |
| Sender identity | Alphanumeric sender ID or a number, no verification badge | Verified sender profile with brand name, logo and description |
| Message format | Text plus a shortened link | Rich cards, carousels, suggested replies, high-resolution images |
| Encryption | None on SMS; RCS to iPhone not available | E2EE RCS in beta where both carriers support Universal Profile 3.0 |
| Delivery data | Delivery report (DLR) only | Delivered and read receipts on RCS, DLR on SMS fallback |
| Campaign planning | Two audiences: Android on RCS, iPhone on SMS | One RCS campaign with a capability check and SMS fallback |
At BSG, we've seen that the biggest operational change is not the format, it is the segmentation. Teams that used to split their audience by OS before every send now run one RCS campaign, let the RCS capability check sort the devices, and let SMS fallback cover the remainder. The SMS that lands on an unsupported iPhone is the same message that customer received two years ago, so nothing is lost on the downgrade path.
The UK is one of the better-covered markets for RCS on iPhone, but not a uniform one. On Apple's carrier feature list updated on 15 September 2026, EE, BT and Three show encrypted RCS messaging in beta, while O2, giffgaff and Tesco Mobile show standard RCS messaging. Vodafone UK is not listed with RCS on iPhone at all (Apple Support, 2026).
That gap matters because iOS holds 51.29% of the UK mobile OS market against 48.35% for Android (StatCounter, 2026). Before Apple RCS, half of the audience was out of reach for rich messaging. Today most of it is reachable, but the Vodafone share still needs SMS, and UK MVNOs enable RCS on their own schedule.
The device side is ready: iOS 26.6 and 26.5 together account for roughly 77% of UK iPhones (StatCounter, 2026). The bottleneck is the operator. In our experience working with retail clients in the UK, the honest Apple RCS UK planning rule is this: assume RCS on iPhone for EE, BT, Three and O2 subscribers, plan SMS for Vodafone, and re-check the carrier list every quarter, because Apple updates it without announcement.
There is no EU-wide switch. Apple enables RCS operator by operator, and the map in September 2026 has three tiers. Encrypted RCS in beta is live on Telekom, O2 and 1&1 in Germany, and on Orange, O2, Yoigo and Pepephone in Spain. It is also live on Orange, Proximus and Telenet in Belgium, Magenta in Austria, T-Mobile in Czechia, Cosmote in Greece, Magyar Telekom in Hungary and Slovak Telekom in Slovakia. Standard RCS on iPhone is live on Vodafone Germany, on Orange, SFR, Bouygues Telecom and Free Mobile in France, on Movistar, Vodafone and Masmovil in Spain, and on BASE in Belgium (Apple Support, 2026).
The third tier is the one that bites. Italy, the Netherlands, Poland, Portugal, Ireland, the Nordics and most of Central and Eastern Europe have no operator listed with RCS on iPhone yet. An eCommerce brand shipping across the EU has iPhone RCS reach in four or five markets and SMS-only iPhone reach almost everywhere else.
Based on what we observe across the campaigns we support in the EU, the common mistake is to treat Apple RCS as a European fact. It is a German, French, Spanish and Belgian fact, expanding quarter by quarter. One fintech client sending onboarding messages into six EU markets saw RCS delivery on iPhone range from roughly half of iOS recipients in Germany to none in Poland, with the same template. Their fix was not to wait: they kept one RCS template and let cascade routing send SMS wherever the capability check returned no RCS.
Three things stayed exactly as they were. Consent rules did not move: RCS for Business sits under GDPR and, in the UK, PECR, so the opt-in you need for SMS is the opt-in you need for RCS. Fallback is still mandatory in practice: any iPhone on an unlisted carrier, on iOS 17 or older, or with RCS switched off in Settings receives SMS. And the sender still has to be verified: an RCS agent receives a verified sender profile before the first message, and that takes days, not minutes.
The numbers changed, though. Juniper Research expects business RCS traffic to pass 200 billion messages globally by 2027, with 3.8 billion active RCS users by the end of 2026 (Juniper Research, 2025), and Apple RCS is a large part of why. What our clients have found is that read receipts alone reshape reporting: for the first time they can see that a promotion was opened on an iPhone, not only that the carrier accepted it.
The planning rule that follows: build the campaign as RCS, write the SMS fallback as the first line of the RCS copy, and check your RCS-capable share per market before you commit budget. For the protocol, the agent model and pricing, our complete guide to RCS messaging covers them in full; the RCS vs SMS channel guide shows where each channel wins on cost and conversion.
If your audience skews iPhone in the UK, Germany, France or Spain, this is the moment to test Apple RCS against your current SMS results rather than read about it. BSG runs RCS for Business with SMS fallback built into cascade routing, so one campaign covers every carrier state above, including the ones that change next quarter. Talk to our team with your target markets and we will share the RCS-capable share we see for each.
Yes. iPhone supports RCS on iOS 18 and later, and RCS for Business on iOS 18.1 and later, but only on carriers Apple has enabled through a carrier bundle. Check Apple's carrier feature list for your market; if the operator is not listed with RCS messaging, that iPhone receives SMS instead.
Yes, on most major networks. EE, BT and Three support encrypted RCS in beta, O2, giffgaff and Tesco Mobile support standard RCS on iPhone, and Vodafone UK is not listed as of September 2026. Business messages to unsupported subscribers fall back to SMS.
Person-to-person RCS between iPhone and Android can be E2EE since iOS 26.5, when both carriers support Universal Profile 3.0; Apple still labels the feature beta. Business (A2P) RCS is delivered through the operator's RBM platform, so it is encrypted in transit but not device-to-device.
The big BSG team is proud to announce the major BSG platform interface design update
It’s that time of the year again when the world’s top mobile operators, technology companies,
The SIGMA Eurasia event is set to hold on the 13th to the 16th of
