RCS in Marketing Cloud Next Summer '26: SFMC's Leap into Rich Messaging

With the Summer '26 release of Marketing Cloud Next, Salesforce ships something mobile-first marketing teams have been asking about for years: native RCS (Rich Communication Services) support. You can now send branded, interactive mobile messages — rich cards, carousels, suggested replies, verified sender logo — straight out of Marketing Cloud Next, without a third-party messaging gateway sitting in front of your subscribers. If your team has been gluing SMS Studio, MobilePush and a partner connector together, this release reshapes how you think about mobile journeys. Here's what actually changes, what it implies for your data model, and a pragmatic rollout plan so you can pilot RCS without breaking what already works.

RCS in Marketing Cloud Next: what's actually new

RCS is the carrier-supported successor to SMS. With iMessage adoption on iOS 18 and broad Android coverage, the channel finally has the reach to matter at scale. It turns a flat SMS bubble into a conversational surface: typing indicators, read receipts, rich media, suggested replies, and — critically — verified senders with a brand logo. SMS marketing has hit a ceiling on engagement and brand recognition; RCS pulls native mobile messaging closer to a WhatsApp-Business style experience, but inside the phone's default messaging app.

The Summer '26 news isn't that RCS exists. It's that RCS is now a first-class channel inside Marketing Cloud Next, alongside Email, SMS, and MobilePush. It has its own Content Builder components and its own Journey Builder activity. Previously, doing RCS from SFMC meant a partner gateway, manual consent mapping, and usually duplicated "mobile" Data Extensions. That whole stack collapses into the platform.

What changes inside the product

A new Journey Builder activity

The RCS message node now appears in the Journey Builder palette next to the classic SMS node. You can route a contact through RCS if their device and carrier support it, and automatically fall back to SMS otherwise. The capability check is platform-managed — you don't have to maintain your own list of compatible handsets, which alone saves weeks of operational drift.

New rich content components

Content Builder gains Rich Card, Carousel, Suggested Reply, and Suggested Action blocks (dial, open URL, calendar action). These are full Content Blocks, so they live in your existing library and inherit your governance model. You can roll them out progressively without a content migration.

Channel-specific engagement events

Reporting exposes granular events: RCS_Delivered, RCS_Read, RCS_SuggestedReplyClicked, RCS_SuggestedActionClicked. These feed dedicated Data Views and flow into Data Cloud out-of-the-box on most tenants, so your existing dashboards and AI training data benefit immediately.

The most common rookie mistake on RCS: treating it like a prettier SMS. RCS is a conversational surface. Design your suggested replies as the opening move of a dialogue, not as a single call-to-action button.

Data model: what to adjust on the SFMC side

RCS uses the same identifier as SMS — the mobile number — which keeps migration simple. But there are a few subtleties to bake into your data model before you scale.

Consent: treat RCS as its own opt-in

An existing SMS opt-in does not automatically extend to RCS under GDPR or most US state privacy regimes. The safe pattern is to capture an explicit opt-in for RCS, even when an SMS opt-in already exists. Add a dedicated column to your subscriber Data Extension:

-- Data Extension "Subscribers_Mobile"
-- Recommended fields
SubscriberKey         (Text, PK)
MobileNumber          (Phone)
SMS_OptIn             (Boolean)
SMS_OptIn_Date        (Date)
RCS_OptIn             (Boolean)
RCS_OptIn_Date        (Date)
RCS_Capable           (Boolean)   -- platform-maintained
Locale                (Text)
LastRCSEngagement     (Date)

A practical segmentation query

To pick the right channel for a mobile-first campaign with SMS fallback:

SELECT
  s.SubscriberKey,
  s.MobileNumber,
  CASE
    WHEN s.RCS_OptIn = 1 AND s.RCS_Capable = 1 THEN 'RCS'
    WHEN s.SMS_OptIn = 1 THEN 'SMS'
    ELSE 'SKIP'
  END AS PreferredMobileChannel
FROM Subscribers_Mobile s
WHERE s.SMS_OptIn = 1 OR s.RCS_OptIn = 1

That pattern covers most single-brand, single-market deployments. For multi-brand or multi-country tenants, add a BrandCode field and filter RCS capability by region — carrier coverage is still uneven outside the major markets.

Designing a first RCS message that actually converts

RCS gives you more real estate than SMS. That doesn't mean you should fill it. Three principles keep showing up in early field results:

1. One intent per message

Rich card or carousel, you should be able to summarize the message in a single sentence: "Confirm my appointment," "See the three offers picked for me," "Track my order." If the sentence is ambiguous, simplify the design.

2. Short, action-oriented suggested replies

Cap your suggested replies at three or four. Avoid generic labels like "OK" or "Learn more." Prefer "Book the slot," "Push it a week," "Talk to a rep." The whole point of suggested replies is to make the next step nearly cost-free for the subscriber.

3. Brand verification from day one of the pilot

Request RCS Business Messaging brand verification before your pilot, not after. Without a verified logo your message looks like a vanilla SMS and the engagement uplift evaporates. Carrier review typically takes two to four weeks, so start the process in parallel with your data work.

A progressive rollout that won't break your existing journeys

It's tempting to flip every SMS campaign to RCS. Don't. Move in phases:

Phase 1. Mirror one high-volume transactional journey (order confirmation, OTP) onto RCS for RCS-capable contacts, with SMS as fallback. Measure delivery rate and cost delta — RCS is more expensive per message than SMS in most markets.

Phase 2. Turn on RCS for one targeted promotional journey (a VIP segment or a dedicated drop) using a product carousel. Compare engagement against your equivalent SMS campaign.

Phase 3. Industrialize the RCS-versus-SMS decision in Journey Builder via a decision split on PreferredMobileChannel, and train your content team on the new rich components.

Pitfalls to avoid in the first 90 days

Three traps show up in nearly every early RCS deployment: confusing RCS with OTT (WhatsApp-style) billing, skipping the explicit RCS opt-in, and neglecting the SMS fallback path for non-eligible contacts. Each one is avoidable with a short pre-go-live checklist — exactly the kind of work CGC-Agency runs with marketing ops teams. If you're scoping an RCS activation on SFMC, get in touch for a focused kickoff.

Key takeaways

Point 1. RCS is now native in Marketing Cloud Next Summer '26: a new Journey Builder node, new Content Builder components, and dedicated Data Views.

Point 2. An SMS opt-in does not cover RCS — capture an explicit opt-in and store it in a dedicated RCS_OptIn column on your subscriber Data Extension.

Point 3. Treat RCS as a conversational surface, not as a richer SMS. Suggested replies are the lever that produces the uplift.

Point 4. Roll out in phases, starting with a transactional journey, keeping SMS as the platform-managed fallback.

Point 5. Start brand verification on day one of the pilot — without a verified logo the visual differentiator that justifies the higher cost simply isn't there.