> Fetch clean Markdown by appending `.md` to any page URL under https://signalwire.com/docs or requesting it with the HTTP header `Accept: text/markdown`. The root index at https://signalwire.com/docs/llms.txt lists the available documentation indexes.

# RCS

## Docs

- [Register an RCS agent](https://signalwire.com/docs/platform/messaging/rcs/onboarding.md): Register a branded RCS agent from the Dashboard, test it on your own devices, and launch it with mobile operators.
- [Receive RCS messages](https://signalwire.com/docs/platform/messaging/rcs/receive-messages.md): Assign an RCS agent to a Resource to handle inbound RCS messages, view them in your message logs, and track the delivery status of the messages you send.
- [Send RCS messages](https://signalwire.com/docs/platform/messaging/rcs/send-messages.md): Send plain-text and rich RCS messages, including media, locations, suggestions, cards, and carousels, through the SignalWire Messaging API.


> **Note:** This page contains both a page directory (above) and the landing page content (below). The page directory is generated for agent use and does not appear on the landing page.

> Fetch clean Markdown by appending `.md` to any page URL under https://signalwire.com/docs or requesting it with the HTTP header `Accept: text/markdown`. The root index at https://signalwire.com/docs/llms.txt lists the available documentation indexes.

# RCS messaging

> Send and receive Rich Communication Services (RCS) messages, including cards, carousels, and suggested replies, from a branded RCS agent through SignalWire.

Rich Communication Services (RCS) messages arrive in the recipient's default messaging app from a
branded sender: your brand name, logo, color, and description appear alongside the conversation. On
top of plain text, an RCS message can carry rich content such as cards, carousels, media, locations,
and suggestions the recipient taps to reply, open a link, call you, or add an event to their
calendar.

RCS messages go through the same [Messaging API](/docs/apis/rest/messages/create-message) endpoint
you use for SMS, MMS, and WhatsApp, so RCS becomes one more channel alongside the ones you already
run. The pages in this section cover what's specific to RCS. For how sending, receiving, and delivery
tracking work for SMS and MMS, which RCS builds on, start with
[Send and receive messages](/docs/platform/messaging/send-and-receive-messages).

## How it works

The sender of an RCS message is an **RCS agent**, not a phone number. You register an agent from the
Dashboard with your brand details, and SignalWire takes it through approval with you:

1. **Set up.** You submit the agent's registration form. The agent's status is `pending`.
2. **Test.** SignalWire provisions the agent for testing and its status becomes `in_review`. You can
   send messages through the API to the test device numbers registered on the agent, using the
   agent's ID as `from`.
3. **Launch.** SignalWire applies to the mobile operators in the United States and the status
   becomes `launching`. Once the operators approve it, the agent is `launched` and can message any
   US subscriber on those networks.

> **Note**
>
> RCS messaging is available only from your agent to US phone numbers for now. Sends to any other
> country, including Canada and US territories such as Puerto Rico, are rejected.

Inbound RCS messages reach your application the same way inbound SMS does: assign the agent to a
[Resource](/docs/platform/resources) and the Resource handles messages sent to the agent, for
example by replying from a SWML script.

## Prerequisites

To register an RCS agent, have these ready:

* Your organization's name and legal entity name.
* A contact for the registration: name, title, email address, and phone number.
* Your brand name and description, and a brand color, as a hex code, with a contrast ratio of at
  least 4.5:1 against a white background.
* Image URLs for a 224 × 224 px logo and a 1440 × 448 px banner.
* URLs for your privacy policy and terms and conditions.
* At least one way for recipients to reach you, shown on the agent: a phone number, an email
  address, or a website.
* The phone numbers of the devices you want to test with before launch, in E.164 format.
* Your billing category and agent use case.
* Launch details for mobile operators to review: how users opt in, what triggers your messages,
  the interactions you expect, and the confirmation message sent when a user opts out.
* A way for a reviewer to try the experience: a tester opt-in URL, an opt-out video URL, or a
  screenshots URL.

When you submit, you also confirm that you're authorized to register the agent on behalf of your
organization.

## Next steps

#### [Register an RCS agent](/docs/platform/messaging/rcs/onboarding)

Submit your agent's brand details and follow it from testing to launch.

#### [Send RCS messages](/docs/platform/messaging/rcs/send-messages)

Send plain text and rich content through the Messaging API.

#### [Receive RCS messages](/docs/platform/messaging/rcs/receive-messages)

Handle inbound messages and track delivery status.