RCS in HighLevel

Modified on: Wed, 11 Nov, 2026 at 5:28 AM

Messaging · Labs
RCS Messaging
Branded, interactive RCS messaging — Labs access, sender registration, approval, and pricing.
Overview

RCS gives businesses a richer messaging experience than traditional SMS by supporting branded sender identities, media, interactive elements, and enhanced delivery signals on compatible devices.

RCS is available through HighLevel Labs for selected sub-accounts. Businesses can register senders and track approval within HighLevel. Live messaging requires an approved RCS sender, and SMS fallback may be used when supported and configured.

Important

RCS Messaging is available through HighLevel Labs, not enabled by default for every account. Agencies can select sub-accounts for access. A registered sender must receive carrier and provider approval before live messaging.

1

What is RCS?

Rich Communication Services (RCS) expands business messaging beyond traditional SMS by allowing compatible recipients to receive branded and interactive messages in their supported messaging app. Understanding how RCS differs from SMS helps you design messages that take advantage of rich features while remaining effective when SMS fallback is required.

RCS on the platform can support capabilities such as:

  • Branded business identity
  • Images and rich media
  • Tappable actions such as Call , Open URL , and Suggested Reply
  • Standalone rich cards
  • Carousels
  • Delivery signals
  • Read or Opened signals when supported by the recipient's device and settings

Recipients must have a supported device, messaging app, carrier or network, and RCS configuration. When those requirements are not met, the platform can use SMS fallback when fallback is enabled.

The Core Idea

RCS adds business branding and interactive features to messaging. For contacts who cannot receive RCS, supported SMS fallback can provide an alternative when configured.

2

RCS Messaging Availability Through Labs

Labs gives agencies control over which sub-accounts can access RCS while the feature is being introduced more broadly.

RCS Messaging is available through HighLevel Labs . Agencies can introduce RCS to selected sub-accounts and let businesses register senders directly inside HighLevel. A Private Beta application is no longer required for the new Labs onboarding path.

  • Agency-level control: Enable RCS for chosen sub-accounts instead of activating it for everyone.
  • Self-service registration: Complete business details and submit sender information without leaving HighLevel.
  • Approval tracking: Monitor the sender registration process from the RCS Messaging area.
Important

A) Labs access does not mean the sender is approved. Live RCS messaging requires carrier and provider approval. Availability also depends on supported countries, carriers, and recipient devices.


B) RCS is currently available only for customers using LC Phone (LeadConnector Phone System). Customers using other phone providers must switch to LC Phone to enable and use RCS in HighLevel.

For general agency feature controls, see Labs Features - Complete Overview .

3

Key Benefits of RCS

RCS combines familiar business messaging with richer branding and interaction options. These capabilities can make messages easier to recognize, act on, and measure while SMS fallback provides an alternative for contacts who cannot receive RCS.

Branded Messaging — Display a recognizable business identity in supported RCS experiences instead of relying only on a phone number.
Rich Content — Add supported images, cards, carousels, and structured content to create more engaging messages.
Interactive Actions — Give contacts tappable options such as calling your business, opening a URL, or selecting a suggested reply.
Flexible Sending — Use RCS in supported 1:1 Conversations, RCS Snippets, Bulk Actions, and supported Workflow experiences.
Delivery Visibility — View delivery states such as Sent, Delivered, and Opened when the recipient's device supports the applicable signal.
SMS Fallback — Deliver an SMS alternative when the recipient cannot receive the intended RCS experience and fallback is configured.
Agency-Controlled Labs Access — Choose which sub-accounts can access RCS while introducing the feature gradually.
In-Platform Sender Onboarding — Complete registration, save progress, and track approval directly within HighLevel.
4

What You Can Send with RCS

RCS gives you a set of tools that plain SMS simply doesn't offer. Depending on your plan and configuration, you can send:

  • Branded messages — your business name appears in the inbox instead of a phone number
  • Images and rich media layouts
  • Tappable action buttons — Call, Open URL, or Suggested Replies
  • Standalone rich cards with titles, descriptions, images, and buttons
  • Carousels — multiple swipeable cards in a single message
  • Read receipts and delivery signals where the recipient's device supports them
Two Ways to Send

Send RCS as a 1:1 message directly from a contact's Conversations thread, or as a campaign via Bulk Actions using pre-built RCS Snippets. Both are covered in the companion article — How to Create RCS Snippets and Send RCS Messages .

5

How RCS Compares to SMS and MMS

Before using RCS, it helps to understand exactly what it adds — and where its limits are. The biggest one: RCS reach is growing but not yet universal. That makes it important to design every message so the SMS fallback version is just as clear and useful as the rich version.

FeatureSMSMMSRCS
Text messaging✅✅✅
Images and media❌✅✅
Branded sender experience❌❌✅
Rich cards❌❌✅
Carousels❌❌✅
Suggested replies and actions❌❌✅
Delivery statusLimitedLimited✅
Read/Open status❌❌✅ when supported
Requires RCS-compatible recipient❌❌✅
SMS fallback supportN/AN/A✅
Design Tip: Design for Both

Before finalizing any RCS message, ask: if this arrives as plain text with no image and no buttons, does it still make sense? If yes, you're ready. If no, revise the copy first.

6

Who Can Receive RCS?

RCS delivery depends on four things aligning on the recipient's end: their device , their messaging app , their carrier , and their app settings . In practice:

  • Most modern Android devices using Google Messages or a carrier-supported app are ready to receive RCS
  • iPhone support depends on iOS version and carrier — many iPhone users still receive SMS fallback today
  • Even within Android, some carrier configurations limit certain RCS features
  • Recipients can disable RCS features in their app settings, which also triggers fallback

The platform handles detection and routing automatically. You send one message — the platform determines whether to deliver it as RCS or fall back to SMS based on what the recipient can actually receive.

What Fallback Means in Practice

When a message falls back to SMS, the recipient gets your fallback text instead of the rich card. Billing reflects SMS pricing for that message. Opt-outs apply across both channels — a contact who opts out via SMS is suppressed on RCS too.

7

Compliance and Consent

RCS is a branded, high-visibility channel — which means the same compliance principles that govern SMS apply here, just with higher stakes. Getting this right protects your deliverability, your sender reputation, and your customers.

Requirement 1
Opt-In

Only send RCS to contacts who have explicitly opted in. Your opt-in must tell them what type of messages they'll receive, how often, how to opt out, and how to reach support.

Requirement 2
Opt-Out

Honor these keywords immediately and without exception — they must suppress all future messages across both RCS and SMS:

STOP  •  UNSUBSCRIBE  •  CANCEL  •  END  •  QUIT

The opt-out notice is appended to the first 1:1 RCS message sent to a new contact — unlike SMS, it doesn't repeat periodically after that. Texas blocking rules apply the same as SMS and MMS.

Requirement 3
Content and Sending Frequency

Avoid deceptive, misleading, or spammy content. Keep sending frequency consistent with what you promised at opt-in. Reminders, confirmations, and genuinely useful updates perform best — they feel like service, not noise. For regulated industries, ensure your messaging aligns with your specific legal obligations.

Pro Tip: Sender Identity

Use a sender name that matches your business or website exactly. Inconsistency in your sender identity erodes trust and increases opt-outs over time.

8

Before You Set Up RCS

Preparing your business details in advance helps you complete sender registration accurately and reduces unnecessary approval delays.

Before you enable RCS, gather the business details needed for brand verification and make sure the sub-account has the required access. Registration now takes place in the RCS Messaging settings rather than through a standard Support-led request.

  • Business information: Brand name, business website, address, and contact details.
  • Brand assets: Business logo and other sender branding details as requested.
  • Messaging use case and consent: Information about what the business sends and how recipients opt in.
  • Target countries: Countries where the business intends to send RCS messages.
  • Additional verification: US-specific information when applicable.
Important

You can save registration progress and return later. Exact requirements vary by country and business. See How to Register Your RCS Sender for the full five-stage form.

9

US Sender Registration Fees

Before an RCS sender can message US recipients, it must complete a United States registration in addition to Google RCS registration. US registration comes with third-party fees that are separate from per-message charges. Twilio does not set these fees — they come from the brand verification provider and the US carriers.

FeeCharged ByAmount (USD)Frequency
Brand VerificationAegis (third-party brand verifier for the US)$200Annual
Carrier Onboarding (T-Mobile submission)US carriers, e.g. T-Mobile$500One-time, per new RCS sender
Example — First-Year Cost

A brand registers one new US RCS sender.

  • Year one: $200 + $500 = $700 in registration fees
  • Each following year: $200 for brand verification renewal

Per-message RCS charges and carrier fees are billed on top of this — see Pricing and Billing .

Outside the US?

Registrations are also available for several other countries. See the most up-to-date list of supported regions: RCS Sender Registration & Verification Guide .

Setup Guide
From Labs Activation to Your First RCS Message
Five steps to enable RCS, register, obtain approval, and start sending.
10

How to Enable RCS and Register Your Sender

Enable RCS through Labs, complete self-service registration, and wait for sender approval before sending live customer messages.

Step 1
Enable RCS Through Labs

In Agency View → Settings → Labs , locate RCS Messaging . Use the available feature controls to enable access for the intended sub-accounts. For supported assignments, use the Sub-account tab and Manage . Where RCS is exposed in sub-account Labs, it can also be enabled under Sub-account Settings → Labs .


Step 2
Open Sender Registration

Open an enabled sub-account and go to Settings → Phone System → RCS Messaging . Start the guided sender onboarding process.

Step 3
Complete and Submit Registration

Provide the requested information across Brand Identity, Countries, Sender Details, US Carrier Registration (if applicable), and Review and Submit . Save your progress if you need to return later. Submit the application when the details are complete.

Step 4
Track Sender Approval

Return to Settings → Phone System → RCS Messaging to review progress and respond to any requests for additional information. Once the sender is approved and activated, its status changes to Live . Carrier and provider review are still required.

Step 5
Test and Start Messaging

You can add supported test devices to try RCS before live approval. After your sender reaches Live , send RCS through supported Conversations, Bulk Messaging, Workflows, and reusable RCS Snippets . Confirm consent and the recipient’s RCS compatibility first.

Related guides

For detailed sender fields, see How to Register Your RCS Sender . For rich messages, cards, and sending methods, see How to Create RCS Snippets and Send RCS Messages . SMS fallback may be used where supported and configured; it does not guarantee delivery to every recipient.

11

Message Statuses

After a message is sent, the platform shows delivery signals directly in the conversation view:

StatusWhat It Means
SentMessage left the platform and is in transit.
DeliveredMessage arrived on the recipient's device.
OpenedRecipient viewed the message (where the device supports read receipts).
Heads Up

Read receipts are only available when the recipient's device and messaging app support them — and recipients can turn this off. Treat it as a useful signal when it appears, not a metric you can rely on universally.

12

Pricing and Billing

RCS billing is based on message type and direction. Here's the full breakdown for US messages:

Message TypeDirectionBilling UnitPrice (USD)
Basic RCS TextOutboundPer segment$0.0083
Basic RCS TextInboundPer message$0.0083
Rich RCSInboundPer message$0.0165
Rich RCSOutboundPer message$0.0220
Carrier Fees
Billed directly by Twilio
  • Agency Accounts: standard Twilio pricing
  • Location Accounts: Twilio pricing + 5% markup
Registration Fees

One-time and annual US sender registration fees are separate from the per-message prices above. See US Sender Registration Fees .

13

Failed Message Billing

Failed RCS messages are not charged. You are billed only for messages that are successfully delivered:

Scenario A
RCS fails → SMS fallback delivers

No RCS charge. You pay only for the SMS that successfully delivered.

Scenario B
RCS fails → SMS fallback also fails (or no fallback)

No charge. A message that is not delivered on either channel is not billed.

Good to Know

Failed messages are never charged — whether the failure happens on the RCS attempt or on the SMS fallback.

14

Frequently Asked Questions

Q: Why did my test message arrive as SMS instead of RCS?
The recipient may not currently meet the device, app, network, carrier, or RCS-setting requirements for RCS. If SMS fallback is enabled, fallback in this situation can be expected behavior.
Q: Does an Opened status appear for every RCS recipient?
No. Read or Opened signals depend on the recipient's device, messaging application, and settings. Recipients may also disable read receipts.
Q: Can I send an RCS Snippet directly to one contact?
Supported 1:1 RCS messaging is available through Conversations for enabled accounts. Feature availability can vary by account and sender approval.
Q: Can RCS be automated through Workflows?
Yes. Supported RCS Workflow actions can automate messaging in enabled sub-accounts after the sender is approved for live messaging.
Q: Why does my RCS cost differ between messages?
Billing can differ based on country, message direction, whether the message contains media, message classification, and applicable segmentation or carrier rules. See Pricing and Billing above for current US pricing.
Q: Am I charged for RCS messages that fail?
No. Failed messages are not charged. If RCS fails and SMS fallback delivers, you pay only for the delivered SMS. If nothing is delivered, there is no charge.
Q: Should I put important information only inside an RCS button?
No. Some contacts may receive an SMS fallback that does not preserve the rich RCS experience. Keep critical information and calls to action understandable in the fallback text.
Q: Why can't I select an RCS Sender ID when sending?
Confirm that RCS is enabled for the sub-account in Labs. Open Settings → Phone System → RCS Messaging and confirm the sender has completed registration and is Live. Review any outstanding approval requirements.
Q: If a contact opts out via SMS, can I still reach them on RCS?
No. Opt-outs apply across both channels — a contact who replies STOP (or any other opt-out keyword) on SMS is suppressed on RCS too, and vice versa.
Q: Do I still need to join a Private Beta list or ask Support to activate RCS?
No. Agencies can enable RCS through Labs for selected sub-accounts, and businesses can submit sender registration directly in HighLevel. Carrier and provider approvals remain required.
Q: Can I test RCS before my sender goes Live?
Yes. Supported test devices can be added to try RCS during onboarding, but live customer messaging still requires an approved sender.
15

Ready to Get Started?

A clear next action helps you move from Labs activation to an approved sender and your first RCS message.

You can begin by enabling RCS for a selected sub-account in Labs. Complete sender registration under Settings → Phone System → RCS Messaging , then track the review until the sender reaches Live .

Next Step

Start with How to Register Your RCS Sender . After approval, follow How to Create RCS Snippets and Send RCS Messages to build and send your first rich message.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article