Get started

To use RCS for business communication, you must follow the official procedure to get approval.

Follow the instructions in each section of this page in the same sequence.

Registration

The registration process starts with you providing the necessary information in the onboarding form (which your account manager will share with you):

• Company name**
• Recipient countries
  • Countries where the traffic will be sent
• Company description**
  • Maximum 100 characters
• Brand color in hexadecimal code**
  • Minimum 4.5:1 contrast ratio relative to white (you can check the contrast here (opens in a new tab)).
• Customer-facing phone number**
• Customer-facing email address**
• Company website**
• Labels for a phone number, email address, and website
• Logo image**
  • Image size: 224 x 224 pixels
  • Format: JPG/PNG
  • Maximum file size: 90 KB
• Hero image**
  • Image size: 1440 x 448 pixels
  • Format: JPG/PNG
  • Maximum file size: 360 KB
• Privacy Policy URL**
• Terms of Service URL**
• Mobile phone numbers for the testing phase
  • Mobile phone numbers that will be added as testers
  • Must include the country code, for example +385991234567
• Sender billing category
  • Conversational - A charge for a conversation that consists of multiple A2P and P2A messages within a given period. Select this option if your sender engages in complex user interactions involving messages exchanged in both directions.
  • Single message - A charge for a single message that includes rich RBM content, like a message with a rich card or a carousel. Select this option if your sender generally sends rich messages and seldom expects to receive replies.
  • Basic message - A charge for a simple text message of up to 160 characters. Select this option if your sender has upgraded SMS to RBM and seldom expects to receive replies. Generally, the agent is expected to send plain text messages of up to 160 characters. However, the agent is not restricted - it can send richer content if programmed to do so and will be billed accordingly.

• Sender use case
  • OTP - One-time password required to authenticate an account or confirm a transaction securely
  • Transactional - Notifications, updates, or alerts that share information directly relevant to customer's existing services or products, such as alerts for suspicious account activities, purchase confirmations, and shipping notifications.
  • Promotional - Sales, marketing, and promotional messages to new or existing customers, with the objective to increase awareness, engagement, and sales.
  • Multi-use - Conversational flows that combine transactional and promotional use cases, such as sending an account notification and then offering a discount or upgrade for a new product or service.

** This information is displayed to customers in RCS conversations.

Infobip submits an official registration request to the RCS technology providers.

The registration process typically takes 2–3 business days. The RCS technology provider will email you a notification when your registration is successful.

You can now test the connection.

Test connection

You can test your registered RCS sender and connection using the web interface or the Infobip API.

Perform the following actions:

1. Turn on chat features in messages (opens in a new tab) on your Android device. The device must use a safelisted mobile number provided by the carrier you want to use for RCS communication (the mobile phone number you provided for the testing phase in the onboarding form).
2. Use the safelisted number to receive test messages. During testing, only this number can receive RCS messages. (Optional) Depending on the RCS technology provider, you may also receive a Google tester invitation. If you receive this message, select Make me a tester. You will receive a confirmation message.

Configure inbound actions and keywords

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

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, then select the three dots menu > Edit configuration. 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 sections.

Verification and launch

To initiate the launch process, provide the following information in the relevant launch request form (which your account manager will share with you):

• Branding
  • Legal name of the brand's parent company
  • Website of the brand's parent company
• Brand point of contact
  • Name, job title, and email address
• Agent experience
  • Proof of opt-in - Provide the source of your opt-in customer data. The opt-in must be from the same brand you registered for your agent. Otherwise, your request will not be approved. If the source is through a website or an app, provide the relevant URLs.
  • Actions that trigger MT messages - Identify the events for which messages are sent to users. Example: purchase or delivery notification. Specify the time interval after which the messages need to be sent.
  • Interaction types - Specify the primary and secondary interactions that are 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. If a user responds with STOP, you must confirm that you will not send them any additional messages unless they opt back in.
    • The agent MUST recognize the word STOP in English and its equivalent in all the languages that you use for RCS communications.
• Usage
  • Message traffic spikes - Peak time intervals for your RCS communications
  • Number of users and messages per month - the number of users and user interactions per campaign every month
  • Start date - start campaign launch date

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

After the launch is approved, you can send unlimited RCS messages and campaigns without additional testing or clearance. You do not need to invite the contacts as testers or safelist their numbers.