← All posts
Industry

RCS vs SMS for Business: What to Do Now

RCS is growing, and the GSMA says the next 6-12 months matter. Here is what that means for teams sending SMS at volume, and what to do about it.

Flowtext Team8 min read

RCS is growing quickly, and the GSMA, the global mobile industry association, says the next 6 to 12 months will decide whether it leads or follows the shift to conversational messaging. If you send text messages at volume, that warning raises a practical question: does RCS vs SMS for business change what you should do this quarter? For most senders, the short answer is no. But it is worth understanding why, and what to prepare.

RCS (Rich Communication Services) is the newer messaging standard built into many phones' default messaging apps. It supports richer features than SMS, such as suggested replies and verified business names. This post explains where the two channels differ and what to do now.

Key takeaways

  • GSMA Intelligence estimates 3.2 billion RCS messages were received worldwide each day at the beginning of 2026, but RCS for Business was still a relatively small share of that total.
  • The "clock is ticking" warning is about RCS's competitive position, not an SMS deadline, and the quoted window is 6 to 12 months, not a flat 12.
  • GSMA describes SMS and RCS as the two device-native options with near-universal reach, and it recommends SMS fallback to extend RCS reach.
  • Reliable data on RCS deliverability, cost and carrier support for business senders is thin. Treat vendor claims with caution.
  • Consent, opt-out and quiet-hours practices should be treated as applying on any channel.

What the GSMA actually said

On October 28, 2026, the GSMA published a summary of its GSMA Intelligence report (opens in a new tab) on business messaging. Several headlines compressed it into "RCS has 12 months." The source is more careful than that.

The warning is a quote from Emanuel Kolta, GSMA Intelligence's lead analyst for network innovation and sustainability. He said RCS "has a real opportunity, but the clock is ticking," and that the next 6 to 12 months will shape whether RCS leads or follows the shift to conversational messaging. Some coverage, such as Android Headlines (opens in a new tab), uses "12 months" in its headline, which is the top of that range. Android Authority (opens in a new tab) reports that the GSMA is developing new conversational capabilities but has not announced specific features or release timelines.

Two points matter for planning:

  • It is not an SMS deadline. Nothing in the GSMA's summary says SMS is going away or that businesses must move by a certain date.
  • The 3.2 billion figure needs context. It is an estimate of RCS messages received per day at the beginning of 2026. It is not a live count, and it is not business or application-to-person (A2P) volume. The GSMA says RCS for Business was still a relatively small proportion of the total.

The GSMA also says adoption is forecast to grow by 25% in 2026 and 38% in 2027, and that commercial adoption is still at a relatively early stage. Its summary does not define what "adoption" measures here, so read those numbers as a direction of travel, not a precise benchmark.

RCS vs SMS for business: where they differ

Reach

The GSMA says SMS and RCS are the two device-native options capable of combining almost universal reach with an intuitive user experience. SMS works on essentially any phone. RCS depends on the device and, according to Salesmessage (opens in a new tab), a business texting vendor, on a data or Wi-Fi connection and a supported device at both ends.

Support for RCS business messaging also varies by source. Vendor blogs describe carrier and platform support differently, and none cites a carrier or other primary source. We have not verified current US carrier coverage for business RCS, so check with your messaging provider before assuming reach.

Features

This is where RCS stands out. The GSMA points to suggested replies, file transfers and verified business identities from earlier RCS standards. Newer enhancements include improved links to start conversations with businesses, copying message content to the clipboard, and more business control over how an exchange is handled.

Verified identity may matter most. The GSMA says verified business identities help users recognise legitimate messages at a time when scams, spoofing and phishing make people more cautious. Its examples include IHG Hotels & Resorts, United Airlines and Nespresso, covering guest support, travel updates, rebooking, product discovery and repeat purchases.

SMS, by comparison, is plain text and short links. It is less rich, but it is the same everywhere.

Cost and setup

The only source on this point is vendor-based. Salesmessage says RCS requires sender registration, that each carrier handles RCS Business Messaging registration separately, and that pricing runs significantly higher than SMS. It gives no figures, and we found no independent pricing data. Salesmessage adds that SMS still handles most business messaging because of reach, cost and platform support. Treat all of this as a vendor perspective, and get current quotes if you are evaluating RCS.

Encryption

Apple's iOS 26.5 added end-to-end encryption for RCS, according to the EFF (opens in a new tab), built on RCS Universal Profile 3.0 and the Messaging Layer Security protocol. That covers person-to-person chats between Android and iPhone, not business messaging, so it should not factor into a business channel decision yet.

RCS vs SMS deliverability: what we know and don't

Teams searching for RCS vs SMS deliverability usually want a number. We don't have one. We found no sourced figures comparing RCS and SMS on delivery rates, open rates or conversion, and we won't repeat unsourced claims.

Some questions are also open:

  • Whether 10DLC registration (the US registration system for business texting over standard phone numbers) or carrier spam filtering applies to RCS is not confirmed.
  • How SMS fallback is billed is not confirmed.
  • Which US carriers and devices currently support RCS for Business has not been verified against carrier or Apple sources.

Until those are answered by primary sources, the dependable baseline remains SMS, where delivery receipts, number health and failure analysis are mature. Per the GSMA, fallback to SMS can help extend reach to users who are not yet RCS capable, so businesses can send reliable communications and richer experiences where possible. That is a layered approach, not a replacement of SMS.

Should businesses switch to RCS?

Based on the evidence available today, "switch" is the wrong frame. Consider the following:

  • Switching away from SMS is not supported by the sources. The GSMA treats SMS as a near-universal channel and recommends fallback to it.
  • Testing RCS may make sense for specific programs. Programs that benefit from verified identity or richer interactions, such as travel updates, support conversations and product discovery, match the use cases the GSMA cites. Your own results would have to justify it, since there are no public performance benchmarks to lean on.
  • The standard is still moving. PhoneArena reports the GSMA published RCS Universal Profile 4.1 (opens in a new tab) around July 28, 2026, adding profile sharing, refined end-to-end encryption rules across different messaging apps, and a lighter way of moving messages between networks. It also reports that Google Messages has not yet adopted the version before 4.1. Support is uneven even among major players.

RCS compliance and TCPA: assume the same duties

We did not review FCC rules or other primary sources on how TCPA (the Telephone Consumer Protection Act, the main US law on texting consumers) applies to RCS. Vendor blogs say consent and opt-out duties carry over, but that claim is not confirmed here and should go through counsel.

The cautious operating assumption is simple: your consent records, opt-out handling and quiet-hours practices should follow the recipient, not the channel. If you add RCS, expect to apply the same rules you already follow for SMS. Don't treat a new channel as a way around them.

What to do now

  1. Don't change what works. Keep optimizing SMS: clean lists, monitor number health, and watch failures by carrier error code.
  2. Ask your messaging provider specific questions. Which carriers and devices support RCS for Business? How does sender registration work? How is SMS fallback billed? Get answers in writing.
  3. Pick one low-risk program for a test. Choose a use case that fits verified identity or richer interactions, and define success metrics before you start.
  4. Make sure SMS fallback is part of any RCS plan. The GSMA recommends it as a way to extend reach.
  5. Audit consent and opt-out records. Confirm they are channel-agnostic and ready for another channel.
  6. Have counsel review RCS compliance. Do this before you launch anything, since primary-source guidance has not been confirmed.
  7. Check back on the standard. Follow GSMA announcements, since specific features and timelines have not been announced.

Frequently asked questions

Is RCS replacing SMS for business?

Nothing in the GSMA's summary says so. It describes SMS and RCS as the two device-native options with near-universal reach, and it presents SMS fallback as a way to extend RCS reach. The "clock is ticking" warning concerns RCS's competitive position in conversational messaging, not an SMS end date.

Does the 3.2 billion messages a day figure mean RCS is mainstream for business?

Not by itself. GSMA Intelligence estimates 3.2 billion RCS messages were received worldwide each day at the beginning of 2026, and says RCS for Business was still a relatively small proportion of that total. It is an early-2026 estimate of messages received, not a current or business-only count.

Vendor blogs say so, but we have not confirmed it against FCC or other primary sources. Plan to apply the same consent, opt-out and quiet-hours practices you use for SMS, and ask counsel to confirm the rules for your program.

Next steps

SMS remains the universal baseline, so deliverability tooling still matters. Flowtext's features include carrier delivery receipts, per-number health scores and automatic benching of flagged numbers. And because consent, opt-out and quiet-hours obligations apply however a message is delivered, our compliance page explains how Flowtext handles them.

This post is general information, not legal advice. Please consult counsel about your own messaging programs.

Tags

  • RCS
  • SMS
  • business messaging
  • deliverability
  • compliance
← Back to all posts

Ready to run the playbook?

Sign up and onboarding gets you from registration to your first send on Flowtext.