Why is RCS messaging not working?

RCS messaging almost never fails because of the network. Every US carrier carries it, so when chat features will not turn on the cause is nearly always the handset or the line: the wrong messaging app, a secondary SIM, a number still registering after a port, a carrier that has not enabled RCS on that plan, a rooted or work-managed device, or an iPhone on iOS 17 or earlier. Read the status line first, then toggle RCS off and back on and let the number re-verify. That fixes the majority of cases on both platforms.

Why is RCS messaging not working after a SIM swap or number port?

Because the number has to register again. RCS registration is tied to the line, so a new SIM or a freshly ported number goes back through the carrier handshake, and Google Messages shows Setting up or waiting for activation until it completes. Give it up to 24 hours with a real data connection, then toggle RCS chats off and on to force a re-registration.

Why did RCS stop working after it was fine before?

The usual causes are a change to the line rather than to the phone: a port, a SIM swap, a new eSIM becoming the default data SIM, or a plan change with an MVNO. A messaging app update that reset the default app does it too. Registration is per line, so anything that alters which number the app registers against will drop RCS until it re-verifies.

Does turning RCS off and on again actually fix anything?

Often, yes. The toggle forces a fresh registration handshake with the carrier network, which is what a stalled or half-completed registration needs. It is not a placebo step. What it cannot fix is a device that is refused registration outright, such as a rooted handset, or a line still mid-port.

Can my carrier see why RCS is not working on my line?

Only partly. Carriers can confirm whether the plan and line carry RCS and whether a port has finished, which covers a real share of cases. They generally cannot see handset-side causes such as the wrong default app, a VPN blocking registration, or the wrong default data SIM, so a support call is worth making after the handset checks, not before.

Is RCS not working the same as a message failing to send?

No, and the difference matters. If RCS is unavailable the message still sends, as SMS or MMS, and still arrives. What you lose is read receipts, typing indicators, image quality, and encryption. A message that genuinely fails to send is a network or account problem rather than an RCS one.

RCS Messaging Not Working? Fixes in Order

Read the status line first

Both platforms tell you which kind of problem you have, if you know where to look, and it saves working through fixes for a problem you do not have.

Android. In Google Messages tap your profile icon, then Messages settings, then RCS chats. The line at the top reads Connected, Setting up, Connecting, Not supported, or RCS chats has been disabled by your carrier. Connected means registration is fine and anything still wrong is on the other end of the conversation. Setting up or Connecting means registration has not finished. Not supported means the app cannot see a data connection, or a carrier that carries RCS. The carrier-disabled line means the number itself is not provisioned, and Google's own advice is to contact the carrier and then tap Retry (Google Messages help).
iPhone. Open Settings, then Apps, then Messages, and look at the RCS Messaging switch. No switch at all means iOS 17 or earlier, or a carrier that has not shipped RCS for iPhone. The words Waiting for activation under the switch mean the carrier has not yet confirmed the line, which has its own page: RCS messaging waiting for activation.

Fix it on Android

Google Messages is the only Android RCS client on US networks, so every step below assumes it. Work through them in order and stop when the status changes to Connected.

Confirm you are in Google Messages and it is the default. Since AT&T retired Advanced Messaging and Samsung discontinued Samsung Messages in July 2026, a legacy app will report no support because it genuinely has none left. Install Google Messages from the Play Store, open it, and accept the prompt to make it your default messaging app.
Confirm you have a real data connection and can receive SMS. Registration needs internet access and it confirms the number by text message, so the phone needs both mobile data or Wi-Fi and a working cellular line. Wi-Fi calling is not a substitute, and a phone that has been offline since setup will sit unregistered indefinitely.
Check which SIM is default. RCS registers against one SIM. On a dual-SIM or eSIM handset the setting follows the default data SIM, so the other line reads as unsupported even on a fully capable network. Switch the default data SIM to your messaging line if they differ.
Verify the phone number shown is yours. Under RCS chats the app displays the number it registered. After a SIM swap this occasionally still shows the old one, which produces messages that appear to send and never arrive.
Allow 24 hours after a port or activation. Registration runs after the port completes. During that window the status genuinely reports unavailable and there is nothing to fix.
Toggle it off and back on. In RCS chats, turn the toggle off, wait a few seconds, turn it back on, and let the number re-verify without switching apps. Google warns that toggling removes you from any RCS group chats you are in, so do it once rather than repeatedly.
Update the app and Play Services. An out-of-date Google Messages, or an old Google Play Services, is on Google's own checklist. Update both from the Play Store and reopen the app.
Clear the app cache and restart. If it is still stuck after a full day, go to Android Settings, Apps, Messages, Storage, and clear the cache but not the data. Restart the phone and let it register from a stable connection.

Fix it on iPhone

Apple added RCS in iOS 18, and it only works on a carrier that supports RCS for iPhone, so the two checks that come first are the OS version under Settings, General, About, and your carrier's row on Apple's list of carriers with RCS on iPhone.

Open Settings, tap Apps, then Messages. Confirm RCS Messaging is switched on. Apple's own setup note is that there can be a short delay after it is first turned on (Apple support).
Give it cellular service. Activation confirms the number over the cellular line, so a phone with cellular data off, or with no signal, can wait indefinitely on Wi-Fi. Check Settings, Cellular, and try a few minutes with Wi-Fi off.
Install the carrier settings update. Settings, General, About, then wait about fifteen seconds. If an update is offered, install it. Carriers ship RCS support for iPhone this way, and a phone that has not taken the update can be missing the switch entirely.
Toggle RCS Messaging off and on, or toggle Airplane Mode, and give it a few minutes to re-register.
Restart the phone. If it is still stuck, Settings, General, Transfer or Reset iPhone, Reset, Reset Network Settings clears the network state. That also forgets saved Wi-Fi passwords, so keep it for last.
Remember iMessage is separate. A thread with another Apple user stays on iMessage regardless. RCS only affects conversations with non-iMessage contacts, so a blue thread behaving normally tells you nothing about whether RCS is working.

Cases where it will not work at all

Some situations are refusals by design rather than faults. Rooted devices and some managed enterprise work profiles are declined at registration, because the verification step cannot trust the handset. An iPhone running iOS 17 or earlier has no RCS to enable. A prepaid brand or smaller MVNO may not have RCS on iPhone yet even where its host network does, and a few regional carriers are still catching up on Android too; the current position for each US network is kept in the RCS carrier support tracker. In each of these the status will not change no matter how many times you toggle it, and the honest answer is that the line cannot register rather than that something is broken.

One more case looks like a fault and is not. If you moved your number to a phone without RCS, or your new phone has not registered yet, and texts from Android friends stopped arriving, the old registration is still live and their phones are still sending RCS to it. Google keeps a deactivation page for exactly this at messages.google.com/disable-chat, which turns RCS off for the number without needing the old phone.

When the problem is the other person

RCS is negotiated between both ends. If your status reads Connected and one particular thread still behaves like SMS, the recipient is the constraint: they are on an older iPhone, a non-RCS app, a device that cannot register, or they have RCS switched off. Nothing on your side will change that thread, and the message still arrives as SMS. Group threads drop to MMS for everyone the moment one participant cannot take RCS.

If you are the sender, not the recipient

For a business this is the argument against depending on RCS alone. A share of any list will always be mid-port, on an old client, or on a handset that cannot register, and none of that is visible before you send. The answer is fallback rather than exclusion: a well-built RCS programme delivers as RCS where the device is capable and drops to SMS automatically where it is not, so the message lands either way and only the presentation changes. If the channel itself is new to you, what RCS messaging is sets out what it can and cannot guarantee on a real list.

Key facts

The carrier is rarely the cause; every US network carries RCS.
The status line, under RCS chats on Android or the RCS Messaging switch on iPhone, tells you whether it is a registration problem or a delivery problem.
Google Messages is the only Android RCS client on US networks since July 2026.
RCS follows the default data SIM, so a second line can read as unsupported.
Registration confirms the number by SMS, so it needs a working cellular line as well as data.
A ported number can take up to 24 hours to register, which is normal.
Rooted devices, some work profiles, iOS 17 or earlier, and carriers without RCS on iPhone cannot register at all.
A single thread behaving like SMS while your status reads Connected is a limit on the recipient side, not yours.