RCS for Business
The short answer
RCS for Business gives a B2B sender three things worth having: verified sender branding, read receipts, and rich cards. It also carries its own approvals, so registration comes with it rather than going away. RCS itself is the carrier standard built to succeed SMS, and 2026 is the year the last gap closed. Apple and Google began rolling out end-to-end encrypted RCS in beta on May 11, 2026, with iPhone support in iOS 26.5. That encryption covers person-to-person threads, not business traffic.
Key takeaways
- RCS: Rich Communication Services, GSMA standard sent over IP.
- No. E2EE in RCS covers person-to-person only.
- Verified sender branding: brand name, logo, color, verified badge in-thread.
- Brand verification: individual brand rep's email (not distribution list), mandatory Google authorization, up to five 50MB supporting PDFs.
- RCS: verified brand identity and rich cards, multi-week approval.
- Blue Reacher: iMessage first (no A2P registration), RCS then SMS fallback.
How a message falls back
RCS and business RCS are different products
RCS: Rich Communication Services, GSMA standard sent over IP. Carries full-res media, longer text, typing indicators, read receipts, interactive buttons. Universal Profile spec defines features; 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
Coverage gap closed by May 2026. Apple said Nov 2023 it would add Universal Profile support; shipped Sept 2024 (iOS 18), added business messaging Oct 2024 (iOS 18.1). GSMA published Universal Profile 3.0 in March 2025 with end-to-end encryption (MLS protocol). Apple confirmed May 4, 2026 that iOS 26.5 would add encrypted RCS.
- May 11, 2026: Apple and Google began E2EE encrypted RCS beta rollout. Encryption on by default, lock icon marks encrypted chats, requires iOS 26.5 on supported carrier. AT&T, T-Mobile, Verizon all support RCS; UScellular and many MVNOs. Google reported 1B+ RCS messages daily in US (May 2025, 28-day average). Carrier rollout of newer profile varies by network.
November 2023
- What happened
- Apple says it will add support for the RCS Universal Profile
September 2024
- What happened
- iOS 18 ships RCS on Universal Profile 2.4
October 2024
- What happened
- iOS 18.1 adds RCS support for business messaging
March 2025
- What happened
- GSMA publishes Universal Profile 3.0, adding E2EE based on MLS
May 13, 2025
- What happened
- Google reports more than a billion RCS messages a day in the US
February 2026
- What happened
- Encrypted RCS testing begins in the iOS 26.4 beta
May 4, 2026
- What happened
- Apple confirms iOS 26.5 will add end-to-end encrypted RCS
May 11, 2026
- What happened
- 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.
- Structural reason: business RCS passes through platform and carrier, both need to read it for routing, spam filtering, SMS fallback. E2EE would break all three. Business RCS has transit encryption, real but different. Trust signal is verified sender profile, not a lock icon.
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, description, tappable buttons, single or carousel. Title max 200 chars, description 2,000, four suggestions per card at 25 chars each, 250KB total payload. iPhone limitation: carousels stack as cards, only first two CTA buttons visible (others under "Other" menu). Google Wallet and location requests not supported on iPhone.
Card title
- Published limit
- 200 characters
Card description
- Published limit
- 2,000 characters
Suggestions per card
- Published limit
- 4
Suggested reply text
- Published limit
- 25 characters
Total rich card payload
- Published limit
- 250 KB
Everything above describes the mechanism. The Blue Funnel Map marks the stages where your own funnel is losing replies, and you keep the map whether or not you buy.
Map this against your funnelRCS approvals: brand verification plus launch
RCS approvals: brand verification plus launch
Brand verification: individual brand rep's email (not distribution list), mandatory Google authorization, up to five 50MB supporting PDFs. Once per agent, regardless of carriers. Launch approval: Google-managed (Google handles both on carrier's behalf) or carrier-managed (requires direct agreement with carrier first).
- Paperwork shape mirrors SMS registration. Twilio's RCS asks: legal business name, company type, registration number, US EIN/FTIN, public video showing sender functionality and opt-out, CTIA handbook acknowledgment. Timeline: 4-6 weeks, longer for multi-region launch.
- Fallback governs final cost. RCS drops to SMS when device, carrier, or settings can't take RCS. Fallback rides US carrier SMS route. A2P 10DLC governs SMS fallback even though RCS leg doesn't. Budget for RCS approvals plus whatever governs SMS fallback.
- 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 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) and revoke-all extension (Jan 31, 2027, order DA 26-12) 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.
US registration
- RCS for Business
- Brand verification with Google, launch approval per carrier, plus A2P 10DLC on the SMS fallback route
- iMessage via Blue Reacher
- No A2P registration required
Sender identity
- RCS for Business
- Verified brand agent with name, logo, brand color, and badge
- iMessage via Blue Reacher
- Named line in a blue bubble
Encryption
- RCS for Business
- Encrypted in transit; the May 2026 end-to-end rollout covers person-to-person threads
- iMessage via Blue Reacher
- Apple's encrypted messaging service; end-to-end encryption is likewise a person-to-person feature
Rich formats
- RCS for Business
- Rich cards, carousels, suggested replies and actions
- iMessage via Blue Reacher
- Blue-bubble conversation threads, no card formats
Reach
- RCS for Business
- Android and iPhone where device and carrier support it
- iMessage via Blue Reacher
- iPhone and Apple devices
Time to first send
- RCS for Business
- Twilio advises four to six weeks or longer
- iMessage via Blue Reacher
- White-glove activation, no A2P registration queue
Blue Reacher strategy: iMessage first, RCS fallback
Blue Reacher strategy: iMessage first, RCS fallback
Blue Reacher: iMessage first (no A2P registration), RCS then SMS fallback. iPhone holds B2B buying power ($85k+ median income, 40% above Android). RCS picks up Android; SMS catches RCS misses. Read that precisely: no A2P registration describes iMessage send only. RCS fallback needs brand verification and launch 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).
- Pricing and fit: $249/line/mo flat (white-glove included), priced for real pipeline. GoHighLevel, HubSpot, Close, Salesforce, Pipedrive, Follow Up Boss native. If your outbound needs verified logo to Android users, RCS is there; approval timeline comes with it.
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).
See the iMessage half of the channel working
RCS is worth adding once your brand agent clears verification and launch approval. The iPhone side of your list doesn't wait on any of that, and it's the side your paid-for leads are already on. Blue Reacher sends blue-bubble iMessage from your CRM across the full funnel, from cold outreach through reactivation, speed to lead, reminders, and no-show recovery, with no A2P registration required on the iMessage send and RCS then SMS fallback behind it. Book your Blue Funnel Map and we'll walk your list, your CRM, and the exact sequence we'd run. Want it demonstrated instead of described? Ask us to open the call by text.