This article outlines the information required to create an RCS agent and successfully launch RCS for Business with Bandwidth. These requirements apply regardless of the brand, campaign provider or aggregator partner. Please note that both new RCS agent registration and commercial launch requests should be submitted via email to [email protected].
Agent attributes for the Brand Information page
Agent attributes are part of the visual representation of an RCS agent on a mobile handset. They’re displayed on the Brand Information page, also known as the public profile, when a mobile user clicks on the brand logo from the RCS message body.
Attribute | Instructions and Parameters | Example |
Agent display name (1) | An agent display name is limited to 40 characters. It should be unique and descriptive, clearly reflect the agent's specific purpose, and ensure scalability and in-app searchability.
Note: A single agent shouldn’t be used for multiple unrelated use cases, as it may cause user confusion and make opt-out handling more complex. | Bandwidth Special Events |
Agent description (2) | An agent description is limited to 100 characters. It should be concise and specific, clearly state what users can expect from the agent, and avoid vague marketing phrases or general taglines. | Bandwidth special event and promotion information updates |
Brand color (3) | A brand color must have a minimum 4.5:1 contrast ratio relative to white. | #4A626D |
Customer-facing phone number and label (4) | The desired customer-facing phone number and label. | +1 800 808 5150 Call Us |
Brand's company website and label (5) | The desired brand's company website and label. | Bandwidth |
Customer-facing email address and label (6) | The desired customer-facing email address and label. | Event Information |
Agent banner (7) | An agent banner, also known as a hero image, is displayed in the agent's Info & Options screen. It partially overlaps with the logo, so it should be designed accordingly for a visually pleasing result.
It must be accessible via a public URL and have the following parameters:
| |
Agent logo image (8) | An agent logo image overlaps with an agent banner and is cropped into a circle (even if the original is a rectangle).
It must be accessible via a public URL and meet the following parameters:
| |
Privacy Policy URL (9) | It must be an online page or a PDF file accessible via a public URL that starts with http:// or https://
Privacy policy must be linked in the call to action and include a statement indicating:
| |
Terms of Service URL (10) | It must be an online page or a PDF file accessible via a public URL that starts with http:// or https://
Terms and conditions must be either fully displayed beneath the CTA or accessible using a clearly labeled link near the CTA and must include:
|
Brand details for verification
This information is submitted to the verification agent and thoroughly vetted.
Brand details | Example |
Brand’s legal company name | Bandwidth, Inc. |
Address Line 1 | 2230 Bandmate Way |
Address Line 2 (if applicable) | n/a |
City | Raleigh |
State | NC |
ZIP Code | 27607 |
Legal form (Public, Private, Government, Non-Profit, Sole Proprietor) | Public |
Stock exchange (mandatory for public companies) | Nasdaq |
Stock symbol (mandatory for public companies) | BAND |
Federal Employer Identification Number (FEIN) | xx-xxxxxxx |
Official company website | |
Primary business phone number | +1 800 808 5150 |
Brand name | Bandwidth |
Brand industry sector (Entertainment, Shopping & Retail, Games, News, Health, Utilities, Finance, Sports, Social, Food & Beverage, Travel, Productivity, Other) | Other |
Brand contact (this person will receive an email from the verification entity and must respond in order to complete the brand verification process) | First name Last name Job title Email address Phone number |
Agent use case and behavior details
This information is submitted to carriers for approval to launch.
Requirements | Description |
Agent use case detailed description | Detailed description of the agent use case. The more information the better. |
Opt-in method detailed description | Detailed description for obtaining opt-in, or terms and conditions for user consent/registration (opt-in, buy-in). |
Opt-in URL, Call-to-Action (CTA) text, or a publicly available link to a screenshot of the CTA. | This should reflect:
|
Confirmation message for opt-in | This should include:
|
Opt-out method detailed description | Detailed description of the end user opt-out process. This should include:
|
STOP response message | Should include:
|
HELP response message | Should include:
|
Agent launching video recording / use case screenshots | Some carriers require the video while others require screenshots. For commercial launch, you must submit a video and screenshots (recorded from a phone) showing how your RCS agent interacts with the mobile user for key requirements like opt in, opt out, help and use case messages. Please refer to the diagram below, which shows what carriers want to see. |
Use case types
Agent | Definition | Allowed use cases | Prohibited use cases |
One Time Password (OTP) | The OTP agent sends a one-time password required to securely authenticate an account or confirm a transaction. |
|
|
Transactional | The Transactional agent sends notifications, updates, or alerts to share information directly relevant to a customer's existing services or products. |
|
|
Promotional | The Promotional agent sends sales, marketing, and promotional messages to new or existing customers, with the goal of increasing awareness, engagement, and sales. |
|
|
Multi-use | The Multi-use agent sends a combination of transactional and promotional messages, such as sending an account notification followed by a discount offer or upgrade for a new product or service. You can only use this agent for conversations that include both transactions and promotions.
Note: You can request to launch a multi-use agent with only one active use case defined (either promotional or transactional). However, you are still required to implement the second use case and provide proof to the RCS for Business support team within six months of the agent's launch. |
|
|