RCS Business Messaging Setup Guide — Launch Verified RCS Campaigns (2026)

RCS Business Messaging (RBM) is the application-to-person (A2P) extension of the RCS protocol. While standard RCS handles person-to-person (P2P) messaging between consumers -- delivering read receipts, typing indicators, and high-resolution media as a replacement for SMS -- RCS Business Messaging adds a layer specifically designed for brands and enterprises communicating with customers.

The core difference is the verified business profile. When a business sends an RBM message, the recipient sees the company's brand name, logo, brand colors, and a verification badge directly in the message thread header. This is not a contact card the user has to save -- it appears automatically because the carrier and Google have verified the sender's identity. The recipient knows immediately that the message is from a legitimate business, not a random phone number or a spoofed sender.

RBM operates through Google's RBM platform, which acts as the intermediary between businesses and mobile carriers. Google manages the agent model: businesses create an "RBM agent" (essentially a verified business identity) that is then submitted to individual carriers for approval. Once approved, that agent can send rich messages to subscribers on that carrier's network.

The growth trajectory has been significant. RCS traffic grew roughly 50% in 2025, driven by two major factors. First, Android adoption of Google Messages as the default SMS/RCS client continued to climb, with over 1 billion monthly active RCS users globally. Second, Apple's iOS 18 added RCS support, meaning iPhone users now receive RCS messages from Android senders instead of falling back to legacy SMS. This expanded the addressable audience for RCS Business Messaging dramatically -- businesses can now reach both Android and iPhone users with RCS-level features.

However, it is important to understand the distinction clearly. Standard RCS is what consumers use when they text each other. RCS Business Messaging is what companies use to send transactional notifications, marketing campaigns, appointment reminders, and interactive customer service flows. The two share the same underlying transport protocol, but RBM adds business-specific capabilities that standard P2P RCS does not support: verified profiles, rich cards, carousels, suggested replies, suggested actions, and structured message templates.

Understanding the differences between these three messaging channels is essential for choosing the right approach. Here is a detailed feature comparison:

SMS remains the universal fallback. Every phone on every carrier can receive an SMS. But SMS has no rich features, heavy A2P carrier filtering (especially post-10DLC), and the 160-character limit forces message segmentation that increases costs and reduces readability.

Standard RCS replaces SMS for consumer-to-consumer texting. It provides a modern chat experience with read receipts, typing indicators, high-resolution media, and reactions. But it is not designed for business use -- there is no verified sender profile, no rich cards, no interactive action buttons.

RCS Business Messaging takes the RCS transport layer and adds business-grade capabilities. The verified profile eliminates sender ambiguity. Rich cards and carousels enable product showcases, appointment confirmations, and interactive flows. Suggested replies and actions turn passive text messages into structured conversations. The trade-off is the registration and approval process, which adds weeks to the launch timeline compared to just sending SMS.

Setting up an RBM agent involves six steps, from initial registration through carrier approval and go-live. The process requires patience -- carrier verification is the bottleneck, often taking 2-4 weeks per carrier.

Step 1: Register with Google's RBM platform

Navigate to business.google.com/rcs and create a developer account. You will need:

• A Google account (personal or Google Workspace)
• Your business name and website URL
• A contact email for verification correspondence
• Your company's legal entity name and registration details

Google will review your account application, which typically takes 2-5 business days. Once approved, you gain access to the RBM Developer Console where you create and manage agents.

Step 2: Create an RBM agent

An RBM agent is the verified business identity that appears in recipients' message threads. When creating an agent, you configure:

• Brand name -- the display name shown in the message thread header (e.g., "Acme Healthcare")
• Logo -- a square image (224x224 px minimum, PNG or JPEG) displayed alongside your brand name
• Hero image -- a banner image (1440x448 px recommended) shown at the top of the conversation
• Description -- a short text describing your business (up to 100 characters), visible when the user taps your profile
• Contact information -- phone number, email, and website associated with the agent
• Brand color -- a primary hex color that tints UI elements in the conversation (suggested action buttons, etc.)
• Privacy policy URL -- required for compliance; links to your data privacy policy
• Terms of service URL -- required for compliance

Take time to get these right. The agent profile is your first impression in every message thread, and changes require re-verification after initial approval.

Step 3: Configure message types

Before submitting for carrier approval, configure the message types your agent will use. This determines what capabilities you request from the carrier:

• Text messages -- plain text with optional suggested reply chips
• Standalone rich cards -- a card with a title, description, media (image or video), and up to 4 suggested actions
• Rich card carousels -- a horizontally scrollable set of 2-10 rich cards
• Suggested replies -- predefined text response buttons that appear below the message
• Suggested actions -- deep link action buttons: dial a phone number, open a URL, create a calendar event, view a map location, or share the user's location

You also define your use case category: transactional (order confirmations, shipping updates, appointment reminders), promotional (marketing campaigns, offers, product launches), or conversational (two-way customer service).

Step 4: Submit for carrier verification and approval

This is the most time-consuming step. Each carrier must independently approve your RBM agent before you can send messages to their subscribers. For US coverage, you need approval from:

• Verizon
• AT&T
• T-Mobile (including Sprint and Metro)

The carrier verification process requires:

• Business documentation (articles of incorporation, EIN, business license)
• Use case description with sample message content
• Opt-in/opt-out flow documentation (how users subscribe and unsubscribe)
• Volume estimates (expected messages per day/month)
• Compliance attestation (TCPA, CTIA guidelines)

Each carrier reviews independently, and timelines vary. Expect 2-4 weeks per carrier for initial review, with possible back-and-forth for additional documentation. Some carriers have been known to take 6-8 weeks for first-time agents in regulated industries (healthcare, finance).

Step 5: Launch testing with test phone numbers

Before going fully live, Google provides a testing sandbox. You can designate up to 20 test phone numbers that receive messages from your agent without requiring full carrier approval. Use this phase to:

• Verify rich card rendering across different Android devices (Samsung, Pixel, OnePlus, etc.)
• Test suggested action deep links (do the URLs open correctly? does the phone dialer populate the right number?)
• Confirm carousel scrolling behavior with your actual card content
• Validate your webhook integration for delivery receipts and user responses
• Test the opt-out flow to ensure users can unsubscribe cleanly

Step 6: Go live after carrier approval

Once a carrier approves your agent, you can send messages to real users on that carrier's network. Key considerations for launch:

• Ramp gradually -- start with low volume (hundreds per day) and increase over 2-3 weeks. Sudden spikes can trigger carrier rate limiting.
• Monitor delivery rates -- track the percentage of messages that actually reach RCS vs. fall back to SMS. Not all devices on an approved carrier will have RCS enabled.
• Set up SMS fallback -- always configure a fallback path. If RCS delivery fails (device offline, RCS disabled, unsupported client), the message should automatically retry as SMS.
• Track engagement metrics -- measure read rates, suggested reply tap rates, and action button click-through rates to optimize your message templates.

RCS Business Messaging supports several rich message types that go far beyond what SMS or even standard RCS can deliver. Each type has specific structure requirements and JSON payload formats.

Text messages with suggested reply chips

The simplest RBM message type is plain text with optional suggested replies. Suggested replies appear as tappable chips below the message, allowing the recipient to respond with a single tap instead of typing.

When a user taps a suggested reply, your webhook receives the postbackData value, which you use to determine the next step in the conversation flow. The visible text ("Yes, remind me") is what the user sees; the postback data is what your backend processes.

Standalone rich cards

A standalone rich card is a single card with a title, description, media (image or video), and up to 4 suggested actions. Rich cards are ideal for product showcases, order confirmations, and appointment details.

The cardOrientation can be VERTICAL (media on top, text below) or HORIZONTAL (media on one side, text on the other). The height property for media controls how much vertical space the image takes: SHORT, MEDIUM, or TALL.

Rich card carousels

A carousel is a horizontally scrollable set of 2-10 rich cards. Each card in the carousel has the same structure as a standalone card. Carousels are perfect for product catalogs, plan comparisons, and multi-option selections.

The cardWidth controls how much screen width each card occupies: SMALL (about 40% of screen) or MEDIUM (about 60% of screen). Use SMALL when you have many cards and want users to see the next card peeking in; use MEDIUM when each card has more text content.

Suggested replies

Suggested replies are predefined text options that appear as tappable buttons below a message. They are designed for structured conversations where you want to guide the user through a flow rather than accepting free-text input.

Suggested replies disappear after the user taps one (or types a free-text response). You can include up to 11 suggested replies per message, but keep in mind that only 3-4 are visible without scrolling on most devices.

Suggested actions

Suggested actions trigger specific device functions when tapped. They look similar to suggested replies but execute deep links instead of sending text. The supported action types are:

• Open URL -- opens a webpage in the device browser
• Dial number -- opens the phone dialer with a pre-populated number
• View location -- opens Google Maps to a specific latitude/longitude or address query
• Create calendar event -- pre-fills a calendar event with title, description, start time, and end time
• Share location -- prompts the user to share their current location back to you

Suggested actions are the most powerful feature of RCS Business Messaging because they reduce friction to near zero. Instead of asking a user to copy an address and paste it into Maps, or save a phone number and dial it, the action executes with a single tap.

RCS Business Messaging pricing is not standardized -- it varies by carrier, country, and message type. Here is what US businesses should expect in 2026:

Per-message costs

In the United States, per-message RBM pricing typically ranges from $0.01 to $0.05 per message, depending on the carrier, message type (text-only vs. rich card), and your negotiated volume tier. For context:

• A2P SMS costs $0.005-$0.02 per segment in the US via most aggregators
• RCS Business Messaging costs $0.01-$0.05 per message (text or rich card)
• iMessage via Sendblue is included in Sendblue's per-message rate with no separate channel surcharge

Rich card messages and carousels typically cost the same as text-only RBM messages, which makes them significantly more cost-effective on a per-impression basis. You get a product showcase with action buttons for the same price as a plain text message.

Carrier reach in the US

All three major US carriers support RCS Business Messaging:

• Verizon -- full RBM support via Google's Jibe platform
• AT&T -- full RBM support, transitioned from their proprietary RCS implementation to Google Jibe
• T-Mobile (including Sprint and Metro) -- full RBM support, the earliest US adopter

This covers roughly 95%+ of US wireless subscribers. The remaining 5% are on MVNOs and smaller carriers, some of which inherit RCS support from their host carrier (e.g., Visible inherits from Verizon).

Device reach

The addressable RCS audience has expanded substantially:

• Android -- over 1 billion devices globally use Google Messages with RCS enabled. In the US, roughly 46% of smartphone users are on Android, and the vast majority support RCS.
• iPhone -- since iOS 18, iPhones can receive RCS messages. However, RBM-specific features (rich cards, suggested actions, carousels) have limited rendering support on iPhone as of early 2026. Basic RCS features (read receipts, typing indicators, high-res media) work cross-platform.

Combined, RCS can reach 70%+ of US smartphone users at a basic level (text + read receipts), with full rich card support on Android devices. The remaining users receive SMS fallback.

The carrier-by-carrier challenge

Unlike SMS (where you register once via 10DLC and reach all carriers), RBM requires independent approval from each carrier. This means:

• Approval timelines stack -- getting approved on all three US carriers can take 6-12 weeks total
• Content policies vary -- a message template approved by T-Mobile might be rejected by AT&T
• You cannot send RBM messages to a carrier's subscribers until that specific carrier approves your agent
• International expansion requires country-by-country carrier approval

RBM is a powerful channel, but it comes with meaningful limitations that businesses need to factor into their messaging strategy.

Carrier-by-carrier approval process

This is the biggest operational friction point. Unlike SMS (register once for 10DLC) or iMessage (no registration needed), RBM requires separate approval from every carrier you want to reach. In the US, this means three independent approval processes with different review teams, timelines, and content policies. Internationally, the complexity multiplies -- each country's carriers must approve independently.

For businesses that need to launch messaging campaigns quickly, this multi-week approval process is a significant disadvantage. Many companies discover that by the time their RBM agent is approved, the campaign window has passed.

No guaranteed delivery

RCS delivery requires the recipient to have an RCS-capable device, an RCS-enabled messaging app (Google Messages on Android), an active data connection, and RCS service turned on. If any of these conditions fail, the message cannot be delivered via RCS and must fall back to SMS. In practice, roughly 15-25% of messages sent to US Android numbers fall back to SMS due to device or network conditions.

Limited analytics compared to web channels

While RBM provides read receipts and delivery confirmations, the analytics are basic compared to web and email channels. You get delivered/read/responded status, but you do not get:

• Time-spent-reading metrics
• Scroll depth or card impression tracking within carousels
• A/B testing infrastructure built into the platform
• Attribution tracking for suggested action clicks (you must build this with UTM parameters)

iPhone RCS support is basic

While iOS 18 added RCS support, the implementation is limited for business messaging:

• Rich cards and carousels may render as plain text with links on iPhone
• Suggested actions may not display as interactive buttons
• No end-to-end encryption for cross-platform RCS (Android-to-iPhone)
• Messages still appear as green bubbles, which iPhone users associate with "lower quality" messaging
• iPhone users cannot react to RCS messages with iMessage-style Tapback reactions

Green bubble stigma

In the US market, this is a real engagement factor. iPhone users have been conditioned to associate green bubbles with inferior messaging. RCS messages from businesses appear as green bubbles on iPhone, which can subconsciously reduce engagement. Studies have shown that iMessage blue-bubble conversations have 30-45% response rates, while green-bubble conversations (SMS or RCS) achieve 6-15%. The protocol is different, but the user perception gap remains.

Template and content review

Carriers review your message templates and use cases during the approval process, and can revoke approval if your content violates their policies post-launch. This means:

• Marketing messages may be rejected or require modifications
• Message content changes may require re-approval
• Aggressive promotional language can trigger carrier flags
• Opt-in/opt-out compliance is strictly enforced

Sendblue eliminates the complexity of managing multiple messaging protocols. Instead of registering separate RBM agents, managing carrier approvals, and building protocol detection logic, you use a single API endpoint that handles everything automatically.

The routing logic is straightforward:

1. iMessage -- if the recipient has iMessage enabled (iPhone users), deliver as iMessage. Blue bubble, highest engagement, no carrier filtering, no registration required.
2. RCS -- if iMessage is not available and the recipient supports RCS (most Android users), deliver as RCS with read receipts and rich media.
3. SMS -- if neither iMessage nor RCS is available, deliver as SMS. Universal fallback, 100% reach.

You do not need to register a separate RBM agent or go through carrier-by-carrier approval. Sendblue manages the infrastructure and routing on your behalf. Here is the API call:

The same call works regardless of whether the recipient is on iPhone (iMessage), Android (RCS), or a basic phone (SMS). The response tells you which protocol was used:

Here is the Node.js equivalent for sending messages with media:

To check which protocol will be used before sending, use the evaluate-service endpoint:

This is useful for audience segmentation. You can tailor your message content based on the channel: richer marketing copy for iMessage recipients (higher engagement), concise transactional messages for RCS/SMS recipients.

For US businesses, the choice between RCS and iMessage is not either/or -- it is both. But understanding the trade-offs helps you allocate resources and set expectations.

iMessage advantages

Engagement is the primary differentiator. iMessage blue bubbles consistently achieve 30-45% response rates in business messaging campaigns. This is not just about the color -- iMessage conversations are not filtered by carriers, appear in the same thread as personal conversations, and benefit from the trust that Apple's ecosystem provides. There is no registration process, no carrier approval, and no content review. With Sendblue, you can start sending iMessage within minutes of getting your API keys.

For US-focused businesses where iPhone users are the primary audience (enterprise sales, luxury retail, healthcare, real estate, fintech), iMessage is unequivocally the best channel.

RCS advantages

Rich interactivity is RCS Business Messaging's strength. The rich card format, carousels, and suggested actions enable structured conversations that iMessage cannot replicate natively. A shipping notification with a "Track Package" button, a restaurant reservation with a "Get Directions" action, a product catalog with a swipeable carousel -- these are use cases where RBM shines.

The verified sender profile is also valuable for brand recognition. Your logo and company name appear automatically in every conversation thread, without the recipient needing to save your number as a contact.

For businesses with a significant Android audience (international markets, price-sensitive demographics, B2C commerce), RCS provides features that SMS simply cannot match.

The optimal strategy: use both

The best approach for US businesses is not to choose between iMessage and RCS -- it is to use both through Sendblue's automatic routing. Every message you send reaches the recipient on the best available channel:

• iPhone users get iMessage (blue bubble, highest engagement, no filtering)
• Android users get RCS (rich features, read receipts, branded sender)
• Everyone else gets SMS (universal reach, guaranteed delivery)

One API endpoint, one integration, maximum reach and engagement across the entire US smartphone market.

• iMessage vs RCS vs SMS vs WhatsApp — Complete Comparison (2026) — Side-by-side analysis of all four messaging protocols
• WhatsApp Business API Setup Guide — Complete developer walkthrough for WhatsApp Cloud API
• Apple Messages for Business vs iMessage API — Which Apple messaging channel do you need?
• RCS API Complete Guide — Build rich messaging experiences with automatic protocol routing
• Sendblue API Reference — Full endpoint documentation