Get started with RCS

To send RCS messages, you must create an RCS Business Messaging sender. Follow our guide below to create your sender and verify your business identity. You must be a registered sender before you can send messages to end users.

You can create a sender in two ways:

1. Infobip web interface (opens in a new tab): Guided self-service with smart validation. The system checks your inputs, including file formats and image sizes in real time. If you upload a logo or banner that does not meet the required specifications you will receive an immediate prompt to fix it, preventing any submission delays.
2. Infobip API for RCS (opens in a new tab): Use the Create RCS sender API (opens in a new tab) to automate registration or integrate it into your systems.

How to create an RCS sender

Follow these steps to register your RCS sender.

1. In the web interface (opens in a new tab), navigate to Channels and Numbers > Channels.
2. From the list of available channels, select RCS Business Messaging.
3. In the Create RCS Business Messaging sender section, select Create sender to open the sender creation form.
4. Complete the sender creation form.

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

RCS sender details

Field	Description
Sender name	Unique sender identifier on the web interface. The sender name cannot be blank, include whitespaces, or be changed after creation.
Brand	Brand associated with the sender. Select an existing one or create a new one. Brand names are limited to 40 characters*.
Billing category	Non-conversational: Billed per message (SMS-style). Ideal for one-way messages, including one-time passwords (OTPs), alerts, and promotions and upgraded SMS use cases that primarily send plain text up to 160 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. Select this if your sender is designed for two-way communication and complex user interaction.
Use case	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

On the right side of the form, you can see a live preview of how your sender will appear to the end user.

Display and visual identity

Field	Description
Display name	Sender name shown to end users.
Description	Short text displayed on user devices.
Color	Main icons 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 on contrast requirements, refer to the W3C accessibility guidelines on minimum contrast (opens in a new tab).
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. Must be in E.164 format (for example, +1234567890).
Label for phone	Display label for the phone number.
Primary email	Sender'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 sender's privacy policy. Must be public and start with http:// or https://.
Terms of service URL	Direct link to the sender's terms of service. Must be public and start with http:// or https://.

Save or register

Once all required fields are filled in, you can choose two options:

1. Select Create sender on the Infobip web interface and create an Agent on the Google platform (opens in a new tab).
2. Save as draft to finish later.

Track sender status

You can monitor your sender in any of the defined sender statuses.

To check the status of your sender:

• In the web interface (opens in a new tab), go to Channels and Numbers > Channels > RCS Business Messaging.
• Open the Senders tab.
• Locate your sender and check its status.

Possible sender status:

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 successfully completed launch, and the launch process with other providers is still underway. Properties are locked (except platform parameters). Test traffic is still allowed.
Launch - Partial success	All providers have completed their launch process, with mixed results—some approved and others rejected. Properties remain locked (except platform parameters). Testing is still allowed.
Launched	The sender is fully live and approved for launch in at least one country. Production traffic is enabled for approved countries. Test devices can no longer be added or edited.
Failed	Registration or launch has failed. Contact Support for assistance.

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 once your sender has been successfully tested (In testing status).
  • Go to the Senders tab, select your sender, and choose Request launch.

Test your RCS sender

When the sender status is set to In testing, you can validate the RCS sender by registering test devices and initiating test message flows. This stage also allows you to record the sender demonstration video required for launch approval.

This process includes:

• Preparing your test device.
• Adding its number for safelisting within Infobip.
• Sending a test message.

1. Prepare your test device

   Before adding a test number for safelisting, ensure the physical device is set up correctly:

   • Enable chat features: On your Android testing device, go to your Messages app settings and confirm RCS chats are enabled and connected. See Google's documentation (opens in a new tab) for more information.
   

2. Add test device number(s) for safelisting

   • Accept RBM tester invitation: You will receive a Google tester invitation message on your device once the number is added for testing. If you receive this invitation, select Make me a tester and wait for confirmation.
   • Add the phone number(s) of your prepared test device(s) to your sender configuration in Infobip.
   IMPORTANT

   Only safelisted numbers can receive test messages while the sender is in the In testing phase.

   You can add test devices in the initial flow after creating a sender.

   

   The web interface:

   • Navigate to Channels and Numbers > Channels > RCS Business Messaging > Senders.
   • Select your sender (status must be In testing).
   • Go to the Test devices tab.
   • Select Add device and enter the phone number(s) in E.164 format (for example, +1234567890).

   API:

   • Call the Add RCS test number API (opens in a new tab) endpoint.
   • Refer to the API documentation (opens in a new tab) for request structure and parameters.

3. Send test messages

   Once your test device is added and the end user has accepted the invitation to test your sender:

   • Using the web interface (opens in a new tab) (Broadcast):

     1. Go to Moments > Broadcast.
     2. Select Create broadcast, choose RCS as the channel, and add your sender.
     3. Enter your safelisted test number(s) as recipients.
     4. Compose messages using RCS features (text, rich cards, carousels, buttons).

   • Using prepopulated messages:

     • On the web interface select Channels and Numbers > Channels > RCS Business Messaging.
     • Select the Senders tab and click on a sender In testing, then select Test devices.
     • Choose Send test message.
   
   • Using RCS API:
     • Call the Send RCS messages API (opens in a new tab) endpoint.
     • Target your safelisted test number(s). Refer to the API details for request structure and parameters.

Configure inbound actions and keywords

Set up actions and keywords for inbound messages to automate message processing, reduce manual handling, and improve message management. You can configure specific actions, such as forwarding to an HTTP endpoint, and define keywords to trigger those actions with this feature.

To configure inbound actions and keywords for RCS, follow the steps below:

1. In the web interface (opens in a new tab) , go to Channels and Numbers > Channels.
2. Select RCS Business Messaging and navigate to the Senders tab.
3. Choose the sender and select the ⋮ (three dots) menu > Edit configuration.
4. Configure the inbound actions and keywords as needed.

Supported actions for RCS:

• Forwarding actions: Forwarding to HTTP, No action
• Non-forwarding actions: Conversations, Auto response, Blocking action

For more information, refer to Messaging actions and Keywords documentation.

Launch your RCS sender

To initiate the launch, click Request launch, then select the country in which you intend to activate your RCS sender. Next, choose the appropriate Traffic origin based on the selected country.

Submitting this request triggers an offline process involving you and your account manager, who will coordinate the exchange of all required information to complete the sender launch.

Examples of information required for launch

Info	Details
Branding	Legal name of the brand's parent company. Website of brand's parent company.
Brand point of contact	Full name Job title Email address
Agent experience	Proof of opt-in (opens in a new tab): Provide the source of your customer opt-in data. The opt-in must come from the same brand you registered for your agent. Otherwise, your request will not be approved. If the opt-in source is a website or an app, provide the relevant URLs. Actions that trigger MT messages (opens in a new tab): Identify the events that cause MT (mobile terminated) messages to be sent to users. Examples include purchase confirmations or delivery notifications. Specify the time interval after each event when an MT message is sent to the user. Interaction types: Define the primary and secondary interactions expected to occur between your agent and end users. Proof of opt-out action: Specify the actions that occur if a user requests to opt out of receiving further communication. IMPORTANT If a user responds with STOP, confirm that no additional messages will be sent unless the user opts back in.
Usage	Message traffic spikes: Specify peak time intervals for your RCS communications. Number of users and messages per month: Provide the number of users and user interactions per campaign each month. Start date: Indicate the campaign launch date.

Sender verification and launch approval

Infobip will request the RCS technology provider or MNO to verify your sender. Some MNOs require you to complete additional checks to use their services. Contact Support for more information.

After launch approval:

• Your sender is live and approved for production traffic.
• You can send unlimited RCS messages and campaigns without further testing or clearance.
• You do not need to invite the contacts as testers or safelist their numbers.