# GoHighLevel RCS Support in 2026

> GoHighLevel’s native LeadConnector SMS channel does not support RCS as of April 2026; Blooio adds RCS, iMessage, and SMS fallback to HighLevel conversations and workflows.

Source: https://blooio.com/guides/gohighlevel-rcs-2026

## Does GoHighLevel Support RCS?

As of April 2026, GoHighLevel’s built-in LeadConnector messaging infrastructure sends 10DLC SMS and MMS in the United States. Its default SMS setup does not send Google RCS Business Messaging or iOS 18+ RCS Universal Profile messages.

GoHighLevel has not published a dated roadmap for native RCS. Teams that need RCS inside HighLevel can add an RCS-capable messaging provider.

RCS commonly involves separate provider agreements, brand verification, sender registration, and pricing outside a standard SMS connection.

## What RCS Adds

RCS provides messaging capabilities beyond traditional SMS and MMS for compatible recipients:

- Delivery and read receipts
- Typing indicators
- Verified sender badges
- Rich cards and carousels
- Suggested reply buttons
- Attachments up to 100 MB
- Data-connection delivery rather than carrier SMS segment delivery

On Android devices with RCS enabled, recipients can receive these richer features. On iPhones running iOS 18 or later, RCS appears in a green-bubble thread and can support read receipts, typing indicators, and higher-resolution media. iMessage remains the richer experience when both participants use iMessage.

## How Blooio Adds RCS to HighLevel

Blooio provides a native GoHighLevel integration that makes RCS available in the HighLevel conversation view alongside iMessage and SMS fallback.

When a workflow sends a message, Blooio detects the recipient’s capabilities and routes the message accordingly:

| Recipient capability | Channel used |
|---|---|
| iMessage available | iMessage |
| RCS available | RCS |
| Neither available | SMS fallback |

The same workflow action can route across these protocols without separate workflow branches. SMS fallback can optionally use an existing Twilio account.

Blooio runs alongside the existing LeadConnector SMS setup. Teams can use Blooio only in workflows where they need iMessage or RCS, while leaving other SMS workflows unchanged.

## Setup in Four Steps

1. Install the Blooio integration from the HighLevel marketplace and authenticate with a Blooio account.
2. Select the HighLevel sub-accounts or locations to enable, and choose a Blooio dedicated or shared number for each sub-account.
3. In an existing HighLevel workflow, replace the applicable SMS action with the Blooio send-message action. Select RCS, or use automatic detection for iMessage, RCS, and SMS fallback.
4. Test with an opted-in Android contact with RCS enabled. Where supported, delivery and read receipts appear in the HighLevel conversation view.

The guide states that most agencies complete end-to-end setup, including the marketplace installation, in under 30 minutes.

## Delivery Expectations and Edge Cases

RCS adoption is not universal. The guide estimates that roughly 70–80% of Android users in North America have RCS enabled by default.

RCS may be unavailable when:

- The recipient uses an older device
- The recipient has disabled RCS
- The recipient’s carrier does not support RCS
- The recipient otherwise cannot accept RCS messages

When RCS is unavailable, Blooio can automatically fall back to SMS so the workflow can still deliver.

For regulated messaging, teams can pair RCS with Twilio 10DLC fallback and send delivery-status webhooks into HighLevel custom events. Blooio webhooks identify the protocol actually used: `rcs`, `sms`, or `imessage`.

## Pricing

The guide states that RCS through Blooio is included in the applicable Blooio plan rather than billed per message. Traditional LeadConnector SMS is billed per segment.

See the pricing page for current plans, limits, and inclusions.

## Frequently Asked Questions

### Does GoHighLevel support RCS messaging in 2026?

No. As of April 2026, GoHighLevel’s native LeadConnector SMS channel does not include RCS support, and GoHighLevel has not published a dated roadmap for it.

### How do I add RCS to GoHighLevel?

Install the Blooio app from the HighLevel marketplace, authenticate, enable the relevant sub-accounts, and use the Blooio send-message action in the workflows where RCS is needed. Automatic detection can route messages over iMessage, RCS, or SMS fallback.

### Can an agency offer RCS without rebuilding workflows?

Yes. Blooio works alongside LeadConnector SMS. Agencies only need to replace the message action in workflows where they want to use Blooio channels.

### Does Blooio work with iMessage too?

Yes. Blooio’s HighLevel integration supports iMessage, RCS, and SMS fallback through the same channel, with recipient capability detection.

### What RCS events can appear in HighLevel?

When available, RCS conversations can include delivery receipts, read receipts, typing indicators, and verified sender presentation.

## Links

- HTML page: https://blooio.com/guides/gohighlevel-rcs-2026
- Markdown page: https://blooio.com/guides/gohighlevel-rcs-2026.md
- GoHighLevel integration: https://blooio.com/integrations/high-level.md
- iMessage in GoHighLevel: https://blooio.com/guides/imessage-gohighlevel.md
- iMessage vs. RCS: https://blooio.com/blog/imessage-vs-rcs-2026
- iMessage for business: https://blooio.com/guides/imessage-for-business.md
- All integrations: https://blooio.com/integrations.md
- Pricing: https://blooio.com/pricing.md
- Site index: https://blooio.com/llms.txt