Home/HighLevel/Features/Phone System/How to onboard an RCS sender ID in HighLevel

Conversations and Inbox

How to onboard an RCS sender ID in HighLevel

In short

Onboarding an RCS Sender ID requires a Twilio account enrolled in RCS, creating the sender, configuring webhooks, building a Messaging Service, attaching the sender to that service, and then sharing the generated IDs with the HighLevel team. The process works only with LC Phone enabled accounts.

AreaPhone System · Messaging
Used forDigital marketing agency, Ecommerce retailer, Healthcare clinic
Setup steps9 steps in 1 task
Last updatedNovember 17, 2026

01Who this is for

  • Founders who run agencies need RCS to support richer messaging experiences for their clients.
  • Marketing managers can use RCS branding features to deliver interactive content within chat threads.

02RCS sender IDs, explained

The RCS onboarding feature lets a HighLevel subaccount connect a Twilio registered RCS Sender ID to the platform’s LC Phone system. Once linked, HighLevel can route incoming RCS messages and delivery status updates through its backend endpoints.

The setup lives entirely in the Twilio console. Users create the sender, set required webhook URLs, build a Messaging Service, and attach the sender to that service. After the Twilio side is finished, the user provides the generated IDs to the HighLevel team, who completes the final activation.

RCS messaging is only available to accounts that have switched to LC Phone. Carriers and Google must still approve the Sender ID; the onboarding steps do not perform that approval.

03How businesses use the RCS Sender ID

  • Digital marketing agency. The agency creates an RCS Sender for each client brand, configures the required webhooks, and attaches it to a Messaging Service. They then send branded carousel messages to prospects through HighLevel.
  • Ecommerce retailer. The retailer registers an RCS Sender, adds product images and a banner, and links it to a Messaging Service. HighLevel then delivers interactive order status updates using the RCS channel.
  • Healthcare clinic. The clinic sets up an RCS Sender with its logo, configures inbound and status webhooks, and shares the IDs with HighLevel. Patients receive appointment reminders that include clickable actions.

04The numbers and rules that matter

  • Incoming Messages URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/incoming (POST).
  • Fallback URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/incoming (POST).
  • Status Callback URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/status (POST).
  • Messaging Service Incoming Request URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/incoming (HTTP POST).
  • Messaging Service Fallback URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/incoming (HTTP POST).
  • Messaging Service Delivery Status Callback URL: Https://backend.leadconnectorhq.com/Phone System/cpaas/v1/messages/status.

05Before you start

  • An active Twilio account enrolled in RCS.
  • Access to the specific HighLevel subaccount where the Sender ID will be used.

06How to set up and use the RCS Sender ID in HighLevel

Onboard RCS Sender ID

  1. Verify you are in the correct Twilio subaccount, as Sender IDs are account specific.
  2. Log in to the Twilio subaccount that will host the RCS Sender.
  3. Navigate to Develop > RCS > Senders and click Create RCS Sender.
  4. Enter the Sender Display Name, Description, Logo Image, Banner Image, and Accent Color.
  5. Open the Configuration tab of the new sender and set all webhook URLs to POST as specified.
  6. Go to Develop > Messaging > Services and click Create Messaging Service, naming it appropriately.
  7. Within the Messaging Service setup, configure the Incoming Messages and Status Callback URLs as instructed.
  8. Open the created Messaging Service, go to the Sender Pool tab, click Add Senders, select RCS Sender, and add the previously created sender.
  9. Gather the Account SID, Messaging Service SID, RCS Sender SID, RCS Sender ID, and image URLs and share them with the HighLevel onboarding team.

07What it looks like in HighLevel

08Settings that matter

  • Sender Display Name. Controls the name shown to recipients in the RCS chat thread.
  • Description. Provides a brief use case description for the sender.
  • Logo Image. Sets the brand logo that appears inside the message UI.
  • Banner Image. Defines a larger banner shown on the sender’s profile.
  • Accent Color. Specifies the brand color used in the RCS interface.
  • Incoming Messages URL. Routes incoming RCS messages to HighLevel’s backend.
  • Fallback URL. Provides an alternate endpoint for incoming messages if the primary fails.
  • Status Callback URL. Delivers delivery status updates to HighLevel.
  • Request URL. Configures the Messaging Service’s inbound message endpoint.
  • Delivery Status Callback. Sets the URL for the Messaging Service to report message status.

09Things to know before you rely on it

  • RCS is supported only for accounts using LC Phone; other phone providers cannot enable it.
  • All webhook methods must be set to POST; GET is not allowed.
  • Carrier and Google approval of the Sender ID is required after Twilio setup.
  • If Messaging does not appear in the Twilio navigation, it must be added via Explore Products.

10If something goes wrong

  • Created the sender in the wrong Twilio subaccount.. Recreate the RCS Sender in the correct subaccount and repeat the steps.
  • Messaging option is missing from the Twilio navigation.. Click Explore Products in the Twilio console and add Messaging, then return to Develop > Messaging > Services.
  • Webhook method set to GET.. Change the method to POST for every webhook URL.

11How it connects to the rest of HighLevel

  • Review HighLevel SMS compliance settings for opt out handling. SMS compliance
  • Check the SMS delivery troubleshooting checklist for related issues. SMS troubleshooting
  • Read best practices to avoid SMS carrier restrictions that may affect RCS. SMS deliverability

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

RCS onboarding can feel like a maze, especially if you’re new to Twilio’s console and the carrier approval steps. It’s easy to waste time creating a sender in the wrong subaccount or forgetting that every webhook must be POST, which can cause messages to bounce inside HighLevel.

When it works, you get a branded messaging channel that shows your logo and colors directly in the conversation.

If I were to test it, I’d verify the webhooks fire correctly before sending any live campaigns.

Get More InformationOpens on HighLevelPublished November 2, 2026 · Updated November 17, 2026

Common questions

Common questions about the RCS Sender ID.

Can I start sending RCS messages immediately after completing the steps?

No. The Sender ID still requires approval from Google and the carriers before messages can be sent.

Why must the webhook methods be POST?

Twilio only accepts POST for the URLs used by HighLevel, ensuring proper delivery of incoming messages and status updates.

What happens if I use the wrong Twilio subaccount?

The Sender ID will not be visible to the intended Messaging Service, and you will need to recreate it in the correct subaccount.

Where can I find the Messaging Service SID?

Open Messaging > Services, select your service, and view the SID on the Properties page; it starts with MG.

Is there a difference between the RCS Sender SID and the RCS Sender ID?

Yes. The SID begins with XE and is used for API calls, while the Sender ID begins with rcs: and identifies the sender in messages.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.