What Is RCS Messaging? How It Works on iPhone and Android

RCS messaging (Rich Communication Services) is the carrier-backed texting standard that replaced old-school SMS with read receipts, typing indicators, full-resolution photos and video, and Wi-Fi messaging — and since iOS 18, it's what makes iPhone-to-Android texts look and work better than plain green-bubble SMS. If yours says "waiting for activation," won't turn on, or has vanished from Settings, the fix is almost always on the carrier or Google Messages side, not a broken phone, and the steps below walk through both.

What is RCS messaging, in plain terms?

RCS stands for Rich Communication Services. It's a messaging protocol built and maintained by the GSMA — the trade body that represents mobile carriers worldwide — as part of a specification called the RCS Universal Profile. Think of it as the long-overdue successor to SMS and MMS: instead of 160-character text snippets and heavily compressed photos, RCS carries full-size images and video, lets you see when someone is typing, confirms when a message has been read, and keeps group chats intact with proper names and replies instead of a pile of separate texts.

Unlike iMessage or WhatsApp, RCS isn't one company's app — it's a standard that carriers and phone makers implement. On Android, Google's own Messages app is the de facto RCS client almost everywhere. On iPhone, Apple built RCS support directly into the Messages app starting with iOS 18, announced alongside the rest of that release's Messages updates.

How RCS works between iPhone and Android right now

When two people are texting and both have RCS active, their messages travel over the RCS network instead of falling back to SMS/MMS. On iPhone, that conversation still renders as a green bubble — Apple reserves blue for iMessage-to-iMessage chats — but you get RCS's upgrades layered on top: delivery and read receipts, typing indicators, higher-resolution photos and videos, and more reliable group messaging. Apple's own support documentation confirms that RCS on iPhone needs a text-messaging plan from a carrier that supports RCS, and that your iPhone authenticates with the carrier's network using your phone number (and, depending on the carrier, your IP address) each time it connects.

On the Android side, Google Messages handles essentially all of this through what Google calls "RCS chats" or "chat features." If both people have RCS turned on and connected, the conversation upgrades automatically — no separate app, no account needed beyond your phone number.

The practical result in late 2026: texting between a recent iPhone and a recent Android phone, on a carrier that supports RCS, behaves a lot more like iMessage-to-iMessage or WhatsApp-to-WhatsApp than the SMS of a few years ago — just still in green.

RCS vs. SMS vs. iMessage: what's actually different

Is RCS messaging encrypted?

Sometimes, and it depends on both people, not just one. Apple's support page is explicit that encrypted RCS conversations only happen "depending on whether both you and the people you're messaging have carriers that support it," and that it currently requires iOS 26.5 or later, with the feature still labelled a beta that's "rolling out over time." When a conversation is protected, iPhone shows "Encrypted" with a small lock icon at the top of the thread; if that indicator is missing, assume the message is not protected from interception in transit.

This two-sided requirement is the single biggest reason RCS encryption feels inconsistent: your carrier can fully support it while the person you're texting is on a carrier or RCS client version that doesn't, and the conversation simply won't show the lock. The GSMA has said publicly that adding interoperable end-to-end encryption across the whole RCS ecosystem is a goal of the Universal Profile work, but it is not yet universal the way iMessage or WhatsApp encryption is.

How to turn on RCS messaging

On iPhone: go to Settings > Apps > Messages and look for the RCS Messaging toggle under the text-messaging section. It's on by default on iOS 18 and later where your carrier supports it; if you don't see the toggle at all, your carrier hasn't enabled RCS on your line or your iOS version is too old.

On Android (Google Messages): open Messages, tap your profile picture, then Messages settings, then RCS chats (older versions of the app may label this "Chat features"), and turn it on. If your number isn't verified yet, tap Verify your number and wait.

Both platforms activate RCS through your carrier in the background — there's no account to create — and Apple's own guidance notes that activation "may take a few hours" to begin working after you first turn it on or get a new SIM/eSIM.

Fixing "RCS messaging waiting for activation"

This status — sometimes shown as "Connecting," "Waiting to verify," or "Trouble connecting. Awaiting retry" in Google Messages — means your phone number is mid-verification with the carrier and hasn't been cleared yet. According to Google's own support documentation, "Connecting" simply means your number is being verified and you should wait; "Trouble connecting. Awaiting retry" means there's a problem with that verification, and if it drags on past 30 minutes you should tap Details, then Submit feedback inside the app.

Steps that resolve most stuck activations:

1. Give it real time first — carrier-side provisioning, not your phone, is usually the bottleneck, and it can take several hours.
2. Check your internet connection; RCS verification needs a working data or Wi-Fi connection to complete.
3. On iPhone, confirm you're on iOS 18 or later and that your plan is on a carrier that lists RCS support — Apple maintains a current carrier list linked from its RCS support page.
4. On Android, make sure Google Messages and Carrier Services are updated to their latest versions and that Google Messages is set as your default SMS/MMS app.
5. If you recently swapped SIMs, moved to an eSIM, or changed phones, that's a very common trigger for a stuck "waiting for activation" state — re-verification has to happen again on the new line.
6. Avoid repeatedly toggling RCS on and off while troubleshooting. Google explicitly warns that doing so removes you from any group chats you were part of.
7. If it's still stuck after a day, contact your carrier directly and ask them to check RCS/IMS provisioning on your specific line — this is the step that resolves cases where the carrier's backend, not the device, hasn't finished activation.

Fixing RCS messaging that's not working, missing, or disabled

A few distinct problems get lumped together under "RCS not working." Here's how to tell them apart:

• No RCS toggle at all: your carrier hasn't turned RCS on for your account or region, or your iOS version predates 18. Check your carrier's support page or contact them directly.
• Toggle is on but conversations still show as plain SMS: the other person doesn't have RCS enabled on their end — RCS is only as good as what both sides support, and it silently falls back to SMS/MMS when it isn't available.
• "RCS chats are disabled by your carrier" (Android): this is carrier-side, not app-side. Google's support documentation says to contact your operator directly in this case.
• Message says "Not supported": Google's guidance points to your internet connection first — RCS needs working data or Wi-Fi to verify and send.
• Dual-SIM phones: the SIM you're making calls on should also be set as your data SIM, since RCS verification piggybacks on your data connection.
• Switching phones and losing RCS: if you're moving to a device without RCS, switching messaging apps, or lost your old phone while keeping the number, turn RCS off on the old line first through Google's deactivation portal (linked from both Google's and carriers' support pages) so the new setup isn't blocked by a stale registration.

If you're an AT&T customer specifically, note that AT&T is sunsetting its own Advanced Messaging RCS service in July 2026; per AT&T's support page, RCS messaging on AT&T Android lines will only work through the Google Messages app going forward, so if you were using AT&T's own Messages+ setup, you'll need to switch.

Carrier-specific notes worth knowing

Not every carrier implements RCS the same way, which is a big part of why fixes that work on one network don't help on another:

• AT&T: retiring its proprietary Advanced Messaging RCS service in July 2026; all RCS on AT&T Android devices moves to Google Messages.
• Verizon and T-Mobile: both support RCS through the Universal Profile standard via Google Messages, with the usual caveat that chat features only work when both parties have them enabled.
• MVNOs and prepaid brands: support varies widely and often lags behind the major carriers, so check your specific brand's support page rather than assuming coverage.

If RCS seems to work fine with some contacts and not others, the carrier each person is on — not your phone's settings — is the most likely explanation.

What's next for RCS, and what to do now

RCS is still actively evolving. The GSMA published Universal Profile 4.0 in February 2026, which brought native video calling and rich text formatting to the spec, followed by Universal Profile 4.1 in mid-2026, which added more granular privacy controls over who can see your name and profile photo in individual and group chats, plus a move to a gRPC-based connectionless transport aimed at faster, more stable delivery. Expect those capabilities to show up gradually in Google Messages and, eventually, in Apple's RCS implementation as carriers and both companies adopt the newer spec.

For now, if RCS is stuck, not showing up, or inconsistent: confirm your OS version and carrier support first, give carrier-side activation real time before assuming it's broken, avoid repeatedly toggling the feature, and escalate to your carrier when a status like "waiting for activation" or "trouble connecting" persists past a day. If you're also chasing down a different texting problem — like messages that won't deliver at all over Wi-Fi — the troubleshooting pattern is similar to fixing Wi-Fi Calling when it stops working, since both features depend on your carrier finishing activation in the background rather than anything visibly broken on the phone. And if an old handset is the real issue, it's worth checking whether the device itself has simply aged out of support, the same way some phones have dropped off WhatsApp's minimum OS requirements. If you're shopping for a new phone with RCS and carrier activation in mind, carrier-dependent features like eSIM-only activation are worth understanding too, since SIM swaps are one of the more common triggers for a stuck RCS activation.

Written byNadia Osei

Nadia Osei covers mobile and consumer gadgets for Pandromeda: smartphones, tablets, smartwatches, earbuds and smart-home devices. She tracks launches, software updates and pricing across Apple, Google, Samsung and the rest, and builds comparisons from the manufacturers' published specifications.

More from Nadia OseiAll Mobile & Gadgets coverage