Google's role is why RCS reaches Android users even when a carrier has not built its own implementation: Jibe provides the backend, and Google Messages provides the app. It is also why US carriers have been able to standardize on Google Messages for RCS.
RCS messaging on Android, what you actually get
Inside Google Messages, RCS replaces SMS and MMS on any thread where both ends support it. In practice that means full-resolution photos and video instead of the compressed MMS versions, typing indicators, read receipts, group chats that behave properly rather than degrading to a mess of individual texts, messages up to 3,072 characters instead of 160 per segment, and sending over Wi-Fi when there is no cellular signal.
The switch is per conversation and automatic. There is no separate app, no account to create, and no button to press per message. A thread with someone who does not have RCS stays on SMS and looks exactly as it always did.
Which Android phones have it
Effectively all of them, in the US. Google Messages is the default texting app on Pixel and on most carrier-sold Android handsets, and it is a free install on the rest. Manufacturer messaging apps are the exception rather than the phone: a Galaxy running Samsung Messages can look like it has no RCS when the handset is entirely capable of it.
Turning RCS on in Google Messages
Open Google Messages, then the profile menu, then Messages settings, then RCS chats, and turn Turn on RCS chats on. The phone then registers with the carrier and the status reads Connected when it is done. How to turn RCS on and off has the full walkthrough, including how to turn it back off.
If it hangs on "Setting up", that is the registration handshake rather than the app. RCS waiting for activation covers the fixes in order.
What Google's position means for business senders
Google runs the verification programme as well as the pipes. An RCS Business Messaging agent is approved by Google, and it is that approval that produces the verified name, logo, and checkmark a recipient sees. There is no separate per-carrier brand approval on top of it in the US, which is one of the practical reasons RCS is faster to launch than short codes.
The flip side is concentration: one backend and one client carry most Android RCS, so a change Google makes to Google Messages is a change to the channel. See what is the Google Jibe platform for how the backend fits together, and what is an RBM agent for the sender side.
- Google operates the Jibe RCS backend used by most carriers and by Google Messages.
- Google Messages is the primary Android RCS client and is rolled out in most countries.
- Google Messages offered Android-to-Android E2EE for years; cross-platform E2EE arrived in 2026.
- RCS on Android upgrades a thread automatically when both ends support it, and falls back to SMS when they do not.
- Business sender verification is granted by Google, not per carrier, which is why US RCS launches faster than a short code.