How to request CLASSOUND RCS on SFPC
This document describes how to request RCS on Salesforce Partner Community (SFPC)
Created: March 2026
Permalink: https://wildix.atlassian.net/wiki/x/AYDyaQ
Introduction
RCS or Rich Communication Services is a communication protocol standard for instant messaging that enhances traditional SMS by supporting rich messaging features such as high-resolution media sharing, read receipts, typing indicators, and branded messages. RCS enables businesses to communicate with customers through their native messaging apps, providing a more engaging and interactive experience than standard SMS.
To understand how RCS differs from traditional messaging formats, see the example below:
SMS: text-only messages without media or interactive elements
MMS: messages that can include images or other media along with text
RCS: rich messages that support branding, high-resolution media, and interactive elements such as buttons
Requirements
Legacy Collaboration and Collaboration 7
CLASSOUND Service activated
UC-Business subscription plan or higher
x-bees
CLASSOUND Service activated
x-bees-Standard subscription plan or higher
To activate CLASSOUND follow the instruction described here: CLASSOUND Activation Request
Note: The registration process may take 3–4 weeks
Key features
Fully-verified sender identity: messages are sent from verified business profiles that display the brand name and logo, helping reduce the risk of scams and increasing customer trust
Secure file sharing: allows sending and receiving files, images, and other media directly in the conversation.
Interactive messaging: RCS supports rich media and interactive elements, including high-resolution videos, image carousels, rich cards, buttons, quick replies, read receipts, and typing indicators
Required information
To request CLASSOUND RCS on Salesforce Partner Community submit a case via CLASSOUND Customer Care request. Below is the list of all the information you must include when submitting the case:
All fields are mandatory
Required information | Description |
|---|---|
General information | |
Display name | Max 40 characters |
Use case | Choose one option:
|
Company description | Max 100 characters |
Brand color |
|
Bot/Agent description | A brief description of the use case, including the key objectives regarding end-user behavior |
Large banner image | 1440×448px, JPG/PNG ≤ 360KB |
Small logo | 224×224px, JPG/PNG ≤ 90KB |
Contact information | |
Primary Phone Number | Up to 3 numbers |
Label for primary phone number | e.g., Contact us |
Primary website | Up to 3 URLs |
Label for primary website | e.g., Visit us |
Primary email | Up to 3 email addresses |
Label for primary email | e.g., Contact us |
Business details | |
Industry/Sector | e.g., Finance, Retail |
Estimated Monthly Volume per Country | Approximate number of messages sent monthly in each country (e.g., 50,000) |
Estimated Monthly Volume per User | Average number of messages per user per month (e.g., 2–5 messages/user) |
Branding information | |
Legal Name of Parent Company | Use the official registered legal name |
Parent Company Website | Link to the company website |
Brand Employee Name | Full name of the employee |
Title | Job title |
Work email address | |
Test device number | Phone number with RCS enabled |
Agent Experience | |
How do users opt in | Describe how users opt in and include a link or screenshot |
Message triggers | User actions, external events |
When is the first message sent? | When the first message is sent after opt-in |
Primary interactions | Describe primary interactions and include an example message |
Secondary Interactions | Describe secondary interactions and include an example message |
Use cases