RCS arrives on iPhone: what CRM teams should do about it

The message arrives in the CRM channel within a day of an Apple event. Are we doing RCS now. Usually it comes with a screenshot of a competitor's branded message with a logo and a carousel, sent to an Android handset, and a question about why our SMS still looks like a telegram.

It is a fair question with an unsatisfying answer. Apple is adding support for RCS in iOS 18, and that is a real change to how a large part of your list receives messages. It is not, on its own, the thing that puts your logo in an iPhone inbox.

The gap between those two statements is where most of this quarter's planning mistakes will happen. So it is worth being precise about what is changing, what is not, and what a CRM team should actually do in the next three months.

What is actually changing on the handset

iOS 18 brings support for RCS to Messages. In practice that means conversations between an iPhone and an Android phone can carry what people expect from a modern chat app. Higher quality images and video, typing indicators, read receipts, and better group behaviour.

Two details matter for planning.

The first is that availability depends on carriers. RCS on iPhone is enabled network by network, so the rollout will not be uniform across your markets or even across all subscribers within one market. Treat it as a gradual change in the installed base rather than a date on which everything switches.

The second is that this implementation follows the Universal Profile, the carrier standard, and that standard does not currently include end-to-end encryption. If your messaging carries anything sensitive, the security conversation has not changed as much as the marketing coverage suggests. Keep your existing rules about what goes in a message body.

Consumer RCS and business messaging are two different products

This is the distinction that gets lost, and it is the whole thing.

What is arriving is person-to-person RCS. What marketers usually mean when they say RCS is RCS Business Messaging: verified sender profiles, brand logos and colours, rich cards, carousels, suggested replies and structured analytics. That is a separate product, sold through aggregators, with its own availability by country and by carrier.

Apple has not said that it supports business messaging, and no aggregator is currently able to deliver a verified brand message to an iPhone over RCS. If a vendor tells you otherwise in a pitch this autumn, ask them to name the carrier, the country and the handset, and to run a live test to a phone you supply.

There is a reasonable case that this changes. A large installed base of RCS-capable handsets is exactly what a business messaging ecosystem needs. But "reasonable case" is not a roadmap item, and budget committed against it now is budget spent on a vendor's optimism rather than your own plan.

Keep SMS as the fallback, and keep it good

The practical advice for the rest of this year is dull. SMS remains the channel you can actually buy, in every market, to every handset, with delivery you can account for.

Anything you eventually send over RCS will need an SMS fallback anyway, because some share of your audience will never be reachable over RCS and because RCS delivery can fail back to SMS mid-conversation. The fallback is not a legacy path you plan to retire. It is permanent infrastructure.

So the highest-value work available right now is work you would do regardless:

• Consent records that stand up to scrutiny, with timestamp, source and wording captured per number.
• Number hygiene, including ported numbers, disconnected numbers and international format normalisation.
• A frequency cap that applies across SMS and email together, not per channel.
• Sender identity sorted out properly in each market, including short codes, long codes and alphanumeric sender IDs where they are permitted.
• Clear separation between marketing messages and transactional ones, in routing and in reporting.

Every item on that list improves your programme this quarter and is a prerequisite for anything richer later.

Where a rich format would actually help you

It is worth deciding now where richer messaging would earn its cost, because the answer shapes what you test when the option exists.

Rich formats pay off where a picture removes a decision, or where a reply saves a call. Delivery tracking with a map. An appointment with a confirm or reschedule button. An order problem where two photographs settle the question of which item arrived damaged.

They pay off much less in the places brands instinctively reach for first, which is broadcast promotion. A carousel of six products in a messaging thread is a banner ad in someone's private conversation, and the complaint response to that is not gentle.

The lifecycle moment worth looking at is the one just after a first order, where the job is to remove friction rather than to sell again. We have written about how to build that stretch of the journey in the welcome series that aims at a second purchase. The same logic applies when the channel gets richer: pick the obstacle, remove it, stop.

The measurement questions to settle before you need them

Richer channels bring metrics that look familiar and mean something different, and this is where omnichannel reporting quietly breaks.

Read receipts are the obvious example. If a channel reports that a message was read, somebody will compare that number to an email open rate, and the comparison is meaningless. They measure different behaviours with different mechanics and different biases.

Decide now, while there is no pressure, how you would handle three things. How a read in one channel and an open in another combine into a single engagement definition. How a conversational reply is attributed when it leads to a purchase days later. Which channel gets credit when a fallback fires and the message is delivered by a different route than the one you chose.

Write the answers down. It is much easier to agree a definition before there is a number attached to it.

What to watch between now and the new year

Track three things and resist doing more. Watch the share of your own audience on RCS-capable handsets, which your aggregator can report by market once the rollout progresses. Watch carrier enablement in the countries that matter to you. Watch for any statement from Apple about business messaging specifically, rather than inferring it from consumer features.

Then spend the time you saved on consent, hygiene and fallback quality. When the channel does open properly, the teams that move first will be the ones whose number data was already clean, not the ones who spent this autumn writing a strategy deck about it.