Create your RCS sender

View as Markdown

To send RCS messages, you must create an RCS Business Messaging sender. Follow the steps below to create a sender and verify your business identity.

You can create a sender in two ways:

Infobip web interface: Guided self-service with smart validation. The system checks your inputs, including file formats and image sizes, in real time. If a logo or banner does not meet the required specifications, the system prompts you to correct it before submission.
Infobip API for RCS: Use the Create RCS sender API to automate registration or integrate it into your systems.

Watch the demo video below to see how to create an RCS sender and safelist your test number:

How to create an RCS sender

Follow these steps to register your RCS sender.

In the web interface, go to Channels and Numbers > Channels.
From the list of available channels, select RCS Business Messaging.
In the Create RCS Business Messaging sender section, select Create sender to open the sender creation form.
Complete the sender creation form.

The sender creation form includes required details for the RCS sender setup.

RCS Business Messaging overview showing Create Sender, Request Launch, and Discover launch requirements options

RCS sender details

Field	Description
Sender name	Unique sender identifier on the Infobip web interface. The sender name cannot be blank or include whitespace. The sender name can be up to 40 characters long and is not visible to end users. You cannot change the sender name after creation.
Brand	Business entity that owns or operates the RCS sender. Select an existing brand or create a new one. Brand names are limited to 40 characters. The brand field must not be blank and cannot be changed after the sender is created. This field is not consumer facing and is used for internal identification only.
Billing category	Defines how messages from the sender are billed: Non-conversational: Billed per message (SMS-style). Ideal for one-way messages, including one-time passwords (OTPs), alerts, and promotions. Supports plain text up to 3,072 characters. Richer content is allowed, but billing continues to follow a per-message model. Conversational: Billed per conversation within a 24-hour window, with unlimited messages, including multiple application-to-person (A2P) and person-to-application (P2A) messages. Suitable for two-way communication and complex user interaction. If the end user does not reply within 24 hours, messages are billed per message. NOTE If the end user does not reply within 24 hours, messages are billed per message. Non-conversational message types never trigger conversational billing. Billing is based solely on the content type delivered.
Hosting region	Physical location where your RCS sender’s backend services are hosted with Google. This ensures data residency, privacy compliance, network latency optimization, and carrier regulatory compliance. You cannot change the hosting region after sender creation.
Use case	Defines the message type: One-time password (OTP): Used for account authentication or secure transaction confirmation. Transactional: Notifications, alerts, and updates related to a customer's existing services or activities, such as purchase confirmations, delivery updates, or suspicious login alerts. Promotional: Sales-driven and marketing content sent to promote awareness, engagement, or purchases. Includes limited-time offers, product announcements, and campaign messages. Multi-use: A combination of transactional and promotional flows. For example, notifying a user about account activity and then offering a discount or upgrade for a related product or service.

RCS public profile details

The profile preview panel shows how your sender appears to the end user.

Display and visual identity

Field	Description
Display name	Sender name shown on the end user’s device. Use a sender name that clearly represents your brand so end users can easily recognize who the message is from. If your brand uses multiple sender names, add details to distinguish each sender. Follow channel-specific requirements when setting sender names.
Description	Short text summary displayed on user devices that explains the use case of your RCS sender.
Color	Main icon theme color in hex format (for example, `#000000`). The color must meet accessibility contrast requirements with a ratio of at least 4.5:1 against white text. For more information, see the W3C accessibility guidelines on minimum contrast.
Banner image	JPEG/JPG format, 1440 × 448 px, max 200 kB. Appears at the top of the sender profile.
Logo image	JPEG/JPG format, 224 × 224 px, max 50 kB. Appears as the sender’s avatar.

Contact details

Field	Description
Primary phone number	End-user support number. Accepts E.164 format (for example, `+1234567890`) or local/national format (for example, `1234567`). Numbers with `+` must be valid E.164 with known network prefix. Numbers without `+` must be 3-20 digits. Spaces, dashes, parentheses, and dots are automatically removed. Emergency numbers are not allowed.
Label for phone	Display label for the phone number.
Primary email	Brand's email address in a valid email format.
Label for email	Display label for the email address.
Primary website	Public website for the brand. Must start with `http://` or `https://`.
Label for website	Display label for the website.

Legal details

Field	Description
Privacy policy URL	Direct link to the brand's privacy policy. Must be public and start with `http://` or `https://`.
Terms of service URL	Direct link to the brand's terms of service. Must be public and start with `http://` or `https://`.

Create your sender or save draft

After you complete all required fields, select one of the following options:

Create sender: Submits the sender for registration. This action creates an Agent on the Google platform.
Save as draft: Saves your progress so you can complete the registration later.

Track sender status

After you create a sender, you can monitor its progress through the following statuses.

To check the status of your sender:

In the web interface, go to Channels and Numbers > Channels > RCS Business Messaging.
Open the Senders tab.
Locate your sender and check its status.

Sender statuses:

Status	Description
Draft	Sender details saved but not submitted for registration. Sender is editable.
Pending	A registration or update request has been submitted and is being processed. Sender is locked during processing.
In testing	The sender has been approved for testing. The sender is unlocked for editing, and you can add test devices and send test messages. If a launch attempt fails (all providers reject), the status returns here.
Pending launch	Launch has been requested. The sender is locked and cannot be edited.
Update required	After a launch request, an update to the sender is required before launch can proceed. The sender is unlocked for editing.
Launched – In progress	At least one provider has completed the launch process, and launch with the remaining providers is in progress. • Properties are locked, except for platform parameters. • Adding test devices and sending traffic to test devices is enabled.
Launch – Partial success	All providers have completed the launch process, with some approved and others rejected. • Properties remain locked, except for platform parameters. • For countries where the sender is not launched: you can add test devices and send test traffic. • For countries where the sender is launched: adding test devices and sending test traffic is not available. Any test devices previously added in those countries are removed.
Launched	The sender is live and approved for launch in at least one country. • Production traffic is enabled for approved countries. • For countries where the sender is not launched: you can add test devices and send test traffic. • For countries where the sender is launched: adding test devices and sending test traffic is not available. Any test devices previously added in those countries are removed.

Edit or submit your sender for launch

Edit sender: Available when status is Draft, In testing, or Update required.
- Go to the Senders tab, select your sender, and choose Edit sender.
Request launch: Available after your sender has been tested (In testing status).
- Go to the Senders tab, select your sender, and choose Request launch.

Before requesting a launch, review the launch requirements for your target countries.

Configure inbound actions and keywords

Configure actions and keywords for inbound messages to automate message processing and reduce manual handling. You can set up specific actions (such as forwarding to an HTTP endpoint) and define keywords to trigger those actions.

To configure inbound actions and keywords for RCS:

In the web interface, go to Channels and Numbers > Channels.
Select RCS Business Messaging and go to the Senders tab.
Choose the sender and select the ⋮ (three dots) menu > Edit configuration.
Configure the inbound actions and keywords as needed.

Supported actions for RCS

You can configure different types of actions to handle inbound messages from RCS. Expand each section below to view the available actions and their descriptions.

Action	Description
Follow subscription	Forward inbound messages to configured subscriptions. One subscription can cover inbound messages for multiple numbers. Use this option for simpler management and better security when authentication configuration is needed.
Forward to HTTP	Forward inbound messages directly to a specified HTTP endpoint.
No action	Do not forward inbound messages.

Action	Description
Conversations	Route inbound messages to Conversations for agent handling.
Auto response	Send an automatic response message to the end user when they send an inbound message. Configure the message text and optionally specify the sender name.

Action	Description
Add to blocklist	Automatically add end users to your sender blocklist when they send a specific keyword (such as STOP). Configure the blocklist level: From this sender: Block the end user from receiving messages from this specific sender only. Common use case: Opt-out management for compliance. When an end user sends "STOP", they are added to the blocklist and receive an auto-response confirmation.
Remove from blocklist	Automatically remove end users from your sender blocklist when they send a specific keyword (such as START). Configure the blocklist level: From this sender: Remove the block for this specific sender only. Common use case: Opt-in management. When an end user sends "START", they are removed from the blocklist and can receive messages again.

For more information, see Messaging actions and Keywords.

Was this page helpful?