> This page is for Platform. > 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. # Register an RCS agent > Register a branded RCS agent from the Dashboard, test it on your own devices, and launch it with mobile operators. An RCS agent is the branded sender your recipients see. Registering one starts from the Dashboard; SignalWire then provisions the agent for testing and handles the launch with mobile operators. ## Prerequisites Have the details listed under [Prerequisites](/docs/platform/messaging/rcs#prerequisites) ready, including image URLs for your logo and banner and the phone numbers of your test devices. ## Fees Setting up and testing an agent carries no registration fees. Messages sent during testing are billed at standard RCS messaging rates. Annual vetting fees apply once your agent is ready to [launch](#launch-the-agent) for production use. Resubmitting the registration or updating brand assets incurs additional fees. Fees are subject to change; see [SignalWire messaging pricing](https://signalwire.com/pricing#messaging) for current rates. ## Submit the registration ### Open the registration form In your [SignalWire Dashboard](https://my.signalwire.com), go to **Messaging Campaigns → RCS Agents** and select **Add New**. The **RCS Agents** menu item appears only once RCS agent registration is enabled for your Space. If you don't see it, contact [Support](https://support.signalwire.com/portal) to have it enabled. ### Fill in the form The form has these sections, in this order: | Section | What it asks for | | ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Organization** | Your organization's name and legal entity name, and whether you're registering on behalf of another brand. | | **Contact** | The name, title, email address, and phone number of the person to contact about the registration. | | **Branding Information** | The brand name, description, color, logo, and banner shown on the recipient's device, and your privacy policy and terms and conditions URLs. | | **Contact Methods** | At least one phone number, email address, or website shown on the agent so recipients can reach you, each with an optional label. | | **Messaging Setup** | The phone numbers of your RCS test devices, and optionally an SMS Sender ID and a callback or webhook URL. | | **Sender Agent Use** | The billing category and the agent's use case. | | **Launch Details** | How you obtain user opt-in, what triggers your messages, the interactions you expect, and your opt-out confirmation message. Mobile operators review these answers before approving the agent for launch. | | **Agent Preview** | How a reviewer can try the experience: a tester opt-in URL, an opt-out video URL, or a screenshots URL. | | **Launch Countries** | Where the agent launches, and other countries where you'd like RCS. | A preview beside the form shows how your agent appears on a device as you fill it in. Under **Launch Countries**, the United States is always selected: RCS messaging is available only to US phone numbers for now. The countries you pick under **Other Geographic Areas of Interest** are saved with your registration to tell us where you'd like RCS next. The agent doesn't launch there. ### Submit Confirm that you're authorized to register the agent on behalf of your organization, then select **Register**. The agent's page opens with the status `pending`, and the agent is listed under **RCS Agents**. ## Test the agent When SignalWire has provisioned your agent for testing, its status changes to `in_review` and the agent's page shows its **Agent ID**. Until the agent is launched, it can send messages only to the test device numbers registered on it. [Send a message](/docs/platform/messaging/rcs/send-messages) with the Agent ID as `from` and one of your test numbers as `to`, and confirm it arrives on that device with your branding. If the API returns `rcs_agent_not_sendable`, the agent isn't in `in_review`, `launching`, or `launched`. If it returns `rcs_agent_not_configured`, the agent hasn't finished provisioning for testing. ## Launch the agent After testing, SignalWire applies to the mobile operators in the United States and the agent's status becomes `launching`. Once the operators approve it, the status becomes `launched` and the agent can message any US subscriber on those networks. ## Agent statuses | Status | Meaning | Can send | | ----------- | ---------------------------------------------------------------- | -------------------------------------- | | `pending` | The registration was submitted and is waiting to be provisioned. | No | | `in_review` | The agent is provisioned for testing. | To test devices only | | `launching` | SignalWire is applying to mobile operators in the United States. | To test devices only | | `launched` | Mobile operators approved the agent. | To any US subscriber on those networks | | `rejected` | The registration was not approved. | No | | `suspended` | The agent was suspended. | No | ## Next steps #### [Send RCS messages](/docs/platform/messaging/rcs/send-messages) Send plain text and rich content from your agent. #### [Receive RCS messages](/docs/platform/messaging/rcs/receive-messages) Assign your agent to a Resource to handle inbound messages.