RCS for Business
TL;DR
RCS for Business means verified brand identity and rich cards, but registration comes with it. Person-to-person RCS got end-to-end encryption in May 2026, but business traffic did not. The approval timeline is 4-6 weeks or longer, and SMS fallback means A2P 10DLC registration still applies underneath.
On this page
- 01RCS and business RCS are different products
- 02RCS timeline and carrier support
- 03Business RCS excludes end-to-end encryption
- 04Verified branding, receipts, rich cards
- 05RCS approvals: brand verification plus launch
- 06RCS and iMessage: different halves of B2B
- 07Blue Reacher strategy: iMessage first, RCS fallback
- 08Frequently asked questions
RCS and business RCS are different products
RCS (Rich Communication Services) is a GSMA standard sent over IP. Carries full-res media, longer text, typing indicators, read receipts, buttons. Device and carrier support decide what works.
Two RCS products share one name. Person-to-person RCS got end-to-end encryption in May 2026. RCS for Business (application-to-person) did not. Confusing them is where most RCS reporting goes wrong.
- Person-to-person RCS: two people texting each other. This is what the new end-to-end encryption covers.
- RCS for Business: Google's current name for the application-to-person side, where a verified brand agent messages a consumer. The API is still widely called RCS Business Messaging, or RBM. End-to-end encryption does not cover it.
RCS timeline and carrier support
Apple confirmed May 2026 iOS 26.5 adds encrypted RCS. Universal Profile 3.0 shipped March 2025. iOS 18.1 added business messaging October 2024; iOS 18 launched September 2024.
May 11, 2026: Apple and Google began E2EE RCS beta. Encryption default, lock icon marks encrypted chats, requires iOS 26.5. AT&T, T-Mobile, Verizon all support RCS.
Google reported 1B+ RCS messages daily in the US (May 2025, 28-day average). Carrier rollout of the newer profile varies by network.
| Date | What happened |
|---|---|
| November 2023 | Apple says it will add support for the RCS Universal Profile |
| September 2024 | iOS 18 ships RCS on Universal Profile 2.4 |
| October 2024 | iOS 18.1 adds RCS support for business messaging |
| March 2025 | GSMA publishes Universal Profile 3.0, adding E2EE based on MLS |
| May 13, 2025 | Google reports more than a billion RCS messages a day in the US |
| February 2026 | Encrypted RCS testing begins in the iOS 26.4 beta |
| May 4, 2026 | Apple confirms iOS 26.5 will add end-to-end encrypted RCS |
| May 11, 2026 | Apple and Google begin the beta rollout of end-to-end encrypted RCS |
Business RCS excludes end-to-end encryption
No. E2EE in RCS covers person-to-person only. Apple and Google's May 2026 announcements describe encrypted messaging between iPhone and Android users; neither mentions business traffic.
Business RCS passes through platform and carrier for routing and filtering. E2EE would break both. Transit encryption instead. Verified sender profile, not lock icon, signals trust.
Verified branding, receipts, rich cards
Verified sender branding: brand name, logo, color, verified badge in-thread. Sender identity is cold outreach's hardest problem; RCS solves a real piece of it.
Read receipts and typing indicators come with the channel. Delivery and read events stream to your API, so you land them in your warehouse. Read rates directional; recipient settings affect whether receipts send.
Rich cards: image, title (200 chars), description (2,000 chars), single or carousel. 250KB total. iPhone carousels stack as cards, two CTA buttons visible, no Wallet or location support.
| Rich card element | Published limit |
|---|---|
| Card title | 200 characters |
| Card description | 2,000 characters |
| Suggestions per card | 4 |
| Suggested reply text | 25 characters |
| Total rich card payload | 250 KB |
RCS approvals: brand verification plus launch
Brand verification: brand rep email (not distribution), Google authorization, up to five 50MB PDFs. Once per agent, covers all carriers. Launch: Google-managed or carrier-managed (needs direct carrier agreement).
Paperwork mirrors SMS registration. Twilio asks: legal name, company type, registration, US EIN/FTIN, public sender video with opt-out, CTIA handbook ack. 4-6 weeks, longer for multi-region launch.
Fallback governs cost. RCS drops to SMS when device, carrier, or settings can't support it. A2P 10DLC governs SMS fallback. Budget for both approvals.
- Brand verification with Google, once per agent, before your first launch request
- Launch approval per carrier, with a direct agreement required wherever the launch is carrier-managed
- A2P 10DLC on the US carrier SMS route your fallback traffic runs over
RCS and iMessage: different halves of B2B
RCS: verified brand identity and rich cards, multi-week approval. iMessage: blue bubble on iPhone, no A2P registration (not carrier SMS), immediate launch. Both reach iPhone; RCS also reaches Android.
A2P 10DLC governs RCS fallback (not iMessage). TCPA consent applies to both channels. FCC revocation rules (April 11, 2025, revised by FCC 26-67 on Sep 30, 2026) apply to both.
Choose by list composition and timeline. Android-heavy or logo-critical: RCS first. iPhone-majority and month-of launch: iMessage first. Both is the normal end state.
| RCS for Business | iMessage via Blue Reacher | |
|---|---|---|
| US registration | Brand verification with Google, launch approval per carrier, plus A2P 10DLC on the SMS fallback route | No A2P registration required |
| Sender identity | Verified brand agent with name, logo, brand color, and badge | Named line in a blue bubble |
| Encryption | Encrypted in transit; the May 2026 end-to-end rollout covers person-to-person threads | Apple's encrypted messaging service; end-to-end encryption is likewise a person-to-person feature |
| Rich formats | Rich cards, carousels, suggested replies and actions | Blue-bubble conversation threads, no card formats |
| Reach | Android and iPhone where device and carrier support it | iPhone and Apple devices |
| Time to first send | Twilio advises four to six weeks or longer | White-glove activation, no A2P registration queue |
Blue Reacher strategy: iMessage first, RCS fallback
Blue Reacher strategy: iMessage (no A2P), RCS, SMS. iPhone holds B2B buying power ($85k+ median). No A2P reg describes iMessage only; RCS fallback needs verification and approval.
Channel metrics: iMessage 98% open, 90% read inside three minutes, under 3% spam vs. 85% email spam. 2-3x cold email reply rate. Cold email: 27.7% open, 0.45% reply (Belkins, 7.5M sends 2025).
$249/line/mo flat (white-glove included), priced for pipeline. Native on GoHighLevel, HubSpot, Close, Salesforce, Pipedrive, Follow Up Boss. For verified logo to Android: RCS available, approval timeline included.
Frequently asked questions
Is RCS for Business end-to-end encrypted?
No. E2EE in RCS covers person-to-person only. Apple and Google's May 2026 announcements never mention business traffic. Business RCS has transit encryption and verified sender profile as trust signal.
Do I still need A2P 10DLC registration if I send RCS?
Yes, for SMS fallback. RCS drops to SMS when device, carrier, or setting can't take it. Fallback rides US carrier SMS route (A2P 10DLC governs). RCS leg uses brand verification + per-carrier launch approval.
How long does RCS brand verification take in the US?
4-6 weeks (Twilio) or longer for multi-region launch. Brand verification once per agent; launch approval per carrier. Direct agreements with carrier-managed launches usually set the timeline.
Which US carriers support RCS?
AT&T, T-Mobile, Verizon, UScellular, many MVNOs. E2EE RCS support narrower and rolling out by network; carriers must deploy Universal Profile 3.0 before encrypted threads form.
Can businesses send RCS messages to iPhones?
Yes. Apple added RCS for business in iOS 18.1 (Oct 2024). Caveats: carousels stack as cards, first two CTA buttons visible (rest in "Other" menu), Google Wallet and location requests unsupported.
What happens when an RCS message can't be delivered?
Falls back to SMS when device, carrier, or user settings can't take RCS. Fallback rides US carrier SMS route (A2P 10DLC governs) with per-segment SMS charges.
Are RCS read receipts reliable enough to report on?
Directionally useful, not a census. Receipt send depends on recipient device settings and feature support on both sides. Treat read rate as trend line, not precise count.
Does RCS replace iMessage for B2B outbound?
No. RCS covers Android with verified brand identity and rich cards (post-approval). iMessage covers iPhone with blue bubble and no A2P registration needed (immediate launch).
Keep reading
More on a2p 10dlc
Verizon's 1 October Fee Rise, and Why Replies Now Cost You Money
Verizon raises its outbound A2P fee on SMS and RCS from $0.0045 to $0.005 on 1 October 2026, its second increase in five months. The bigger change is quieter: two carriers now bill the replies your prospects send, and RCS has added a per-conversation meter that is priced for AI support bots, not sales threads.
Toll-Free Verification: What Changed on 15 September 2026
For three years the standard advice to a team stuck in A2P 10DLC registration was to move the traffic to a toll-free number. That advice had a shelf life. As of 15 September 2026 a new toll-free verification is rejected outright unless it carries two live policy URLs, and each of those pages has a list of disclosures it has to contain.
Your A2P 10DLC Campaign Can Be Suspended After It Is Approved
Most 10DLC guides stop at the approval email. Carriers and their vetting partners do not. A registered campaign can be pulled back into review at random, suspended over a flagged link or a complaint spike, or frozen because someone edited it, and while it is down you cannot send, cannot move your numbers, and keep paying the monthly registration fee. Here is what actually triggers a post-approval suspension and how to see one coming.
Put this on your pipeline
Blue Reacher runs outbound iMessage for B2B sales teams, from your CRM, with setup handled for you.
Book a demo