> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Prerequisites
> Complete the registration, testing, and launch verification steps required before sending RCS messages through MoEngage. Full onboarding guide.
To use RCS for business communication, you must follow the official procedure as shown in the following chart:
Prerequisites can be summarized as follows:
* [Register](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/rcs/getting-started-with-rcs/prerequisites#registration) with MoEngage using the onboarding form.
* [Test the connection](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/rcs/getting-started-with-rcs/prerequisites#test-the-connection) by sending RCS messages.
* [Verify the launch](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/rcs/getting-started-with-rcs/prerequisites#verification-and-launchn) using the launch request form.
# Registration
The registration process starts with you providing the necessary information to MoEngage in the onboarding form, which your account manager can share with you:
The information requested can differ depending on the carrier.
| Info | Details |
| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Company name** | This is the company name displayed to customers in RCS conversations. |
| **Recipient countries** | These are the countries where the messages are intended to be sent. |
| **Company description** | This is the company description displayed to customers in RCS conversations. The text of the company description must have a minimum 4.5:1 contrast ratio relative to white. |
| **Brand color in hexadecimal code** | This is the hexadecimal code of your brand color. For example, if your brand color is red, the hexadecimal code for red is #FF0000. |
| **Customer-facing phone number** | This is the phone number displayed to customers in RCS conversations. |
| **Customer-facing email address** | This is the email address displayed to customers in RCS conversations. |
| **Company website** | This is the company web address displayed to customers in RCS conversations. |
| **Logo image** | The logo image represents your brand. This is displayed to customers in RCS conversations. Make sure the logo image has the following specifications: - Image size: 224 x 224 px
- Format: JPG/PNG
- Maximum file size: 90 KB
|
| **Hero image** | The hero image is a larger, more prominent image that enhances the message content within the RCS conversation. Make sure the hero image has the following specifications: - Image size: 1440 x 448 px
- Format: JPG/PNG
- Maximum file size: 360 KB
|
| **Privacy Policy URL** | A privacy policy URL links to your company's privacy policy and informs users about how your company collects, uses, and protects their data. This URL is displayed to customers in RCS conversations. |
| **Terms of Service URL** | A *Terms of Service URL* links to your company's terms of service and provides users with access to the legal terms and conditions governing their use of your services. This is displayed to customers in RCS conversations. |
| **Mobile phone numbers for the testing phase** | These mobile phone numbers will be added for testing purposes, and they must include the country code, such as +19999999999. |
| **Sender billing category** | This refers to the classification used to determine the cost of sending RCS messages. This classification is based on the type of messages sent and their usage. - **Conversational**: A charge for a conversation that consists of multiple A2P (Application to Person) and P2A (Person to Application) 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 (RCS Business Messaging) content, like a message with a rich card. 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.
**Note**: The single message and basic message categories never result in conversational billing events. Carriers will charge a basic or single message price for each message based on the content being delivered. This process ensures a clear and straightforward billing system. |
Your RCS service provider submits an official registration request to the RCS technology providers (such as MNOs). The registration process typically takes 2–3 business days. The RCS technology provider will notify you when your registration is successful. After that, you can test the connection.
# Test the Connection
You can test the connection using the following ways:
* Send text messages using your RCS service provider dashboard.
* Create an RCS campaign in MoEngage using the allowlisted test mobile phone number.
# Verification and LaunchN
Provide the following information in the relevant launch request form, which your account manager will share with you:
The information requested can differ depending on the carrier.
| Info | Details |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Branding** | This includes the legal name and the website of the brand's parent company. |
| **Brand point of contact** | Name, job title, and email address of the designated individual or team responsible for managing and representing a brand's communication through RCS. |
Your RCS service provider requests the mobile network operator (MNO) to verify the sender. Some MNOs require you to complete additional checks to use their services. Contact your RCS service provider 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.