1. Introduction

VNS-RBM team handles the Business Verification and Agent Validation for VNS who has launched the RCS Business Messaging service for delivery to RCS users in India. To ensure that the RCS users in India have a safe and positive experience when interacting with brands, VNS-RBM team, acting on behalf of VNS, and with the approval of VNS, has specified the policies for business communication over RCS (“RBM Policies”). These policies also provide a guideline of restricted content and prohibited behaviors. These policies may be further refined in collaboration with VNS.

VNS-RBM team and VNS reserve the right to modify the RBM Policies at any time. VNS-RBM team, acting on behalf of VNS, will exercise its discretion in the interpretation and enforcement of these policies in conjunction with the Terms of Service.

This document is targeted for businesses and developers who wish to launch their Agents for users in India via the VNS RBM Portal, which is provided and managed by VNS-RBM team. Please follow these policies and guidelines while developing your Agents.

2. Definitions

“Agent” or “RBM Agent” means a bot that communicates with the User via RBM.

“Agent Assets” means some or all of Agent Name, Short Description, Long Description, TOS URL, Privacy Policy URL, Contact Info (Phone, Email, Website URL), Brand Logo, Banner Image, and Agent Screenshots.

"Agent Logo” means a 224 x 224 pixel image, no larger than 50 KB, that acts as the identity of the Brand/RBM Agent.  The Brand Logo is displayed next to each text message in the Chat Thread.  The Agent Logo is also overlayed on the Banner Image on the Info & Options Page.

“Agent Name” is the name for an Agent.  It is a string between 1 and 40 characters.  It is the Sender ID of the Chat Thread.

“Agent Screenshots” are 2 – 8 images showing exactly what End Users see on their mobile devices while using the Agent inside Messages.  Agent Screenshots must include one image of the Bot & Info Page of the Agent. The Agent Screenshots are used during verification and are visible to End Users on the Bot Store.

"Agent Use Case” means one of (a) OTP, (b) Transactional, and (c) Promotional use case assigned to the Agent, for application of business rules.

“Banner Image” is a 1440 x 448 pixel image, no larger than 200 KB, with an aspect ratio (45:14), that is displayed in the upper part of the Info & Options Page,  behind the Agent Logo.

“Brand” is a product or service that is publicly distinguished from other products, services, or concepts. Every Agent must be assigned to a Brand.  A Brand belongs to an Enterprise.

"Brand Name” means the name of the Brand.  It is an alphanumeric string between 1 and 128 characters.  Every Brand must have a unique Brand Name. Brand Name is entered on the VNS-RBM team Platform and is visible to the Developer.  Brand Name is not visible to the End User.

“Bot ID” is an internal ID on VNS-RBM team platform that is used to identify every Agent.  Every Agent has a unique Bot ID.  Bot ID is NOT visible to the End User on Messages.

“Chat Thread” is a conversation between the Agent and the End User.

“Contact Info” means the Phone number, Email address, and Website URL for the Agent, that will be visible to the End User under the Info tab on the Info & Options Page.

“Developer” means the aggregator who is developing and launching Agents on behalf of the Brands.

“End User” or “User” is the user with the Messages app on the Android device.

“Enterprise” is an entity, e.g., a corporation that owns one or more brands.

Info & Options Page is the screen displayed in the Messages app when clicking on the Agent Name in the Chat Thread. The Info & Options Page includes two tabs. The Info tab shows the contacts for the Agent including the Phone Number, Email and Website. The Options tab includes options to view the Privacy Policy and Terms of Service for the Agent and the option to block or report spam.

“Launched Agent” means an Agent that has been verified and is allowed to send and/or receive RCS messages to End Users.

“Long Description” a string between 1 and 3000 characters. The Long Description is used during verification and is visible to End Users on the Bot Store.

“Messages” or “Android Messages” is the Messages app by Google, that is pre-installed on Android        devices, and is the default SMS app for Android devices.

“Privacy Policy URL” is the URL pointing to the privacy policy under which the Brand offers the Agent to End Users and is visible to users under the Options tab of the Info and Options page.  Privacy policy tells End Users how and why the Brand is collecting their information. It spells out how the Brand may use the data, why the Brand uses it, and if the data is shared with others.

“Promotion Initiation Hours” means 10 am – 9pm (7 days a week).

“RBM” means RCS Business Messaging.

“Short Description” a string between 1 and 100 characters.  It is shown on the Info & Options Page to the user.

“Terms of Service URL” is the URL pointing to the terms of service under which the Brand offers the Agent to End Users and is visible to users under the Options tab of the Info and Options page.

“VNS” means Virtuoso Netsoft Pvt Ltd, a company incorporated under the laws of India having its registered address at 3rd Floor, Netsmartz House,Plot No 10,Rajiv Gandhi IT Park Chandigarh, Chandigarh – 160101, India.

“VNS RBM portal” means the portal provided to CPaaS providers or Aggregators or Developers by VNS for onboarding, Agent creation, Template creation and reports download. Link to the portal is https://virtuosorbm.com/

3. RBM Agent Details

RBM Agents enable one-way A2P (Application to Person) or two-way conversational messaging (A2P and P2A) between Brands and End Users. Agents can use any of the RCS advanced messaging services, including animated or static images, audio, video, suggested replies, and suggested action buttons. Please see the whitepaper titled “Revolutionize Business Messaging with RCS”, available here, free of cost, for an introduction to RCS Business Messaging.

This section defines the guidelines for the Agent Assets to submitted.

3.1 Agent Name

Developers can use any name (up to 40 Characters) for their Agent keeping in mind its association with the Brand. The Agent Name can be a catchy phrase or a simple name. Each Launched needs to have a unique name, different from the Agent Name of any other Launched Agent. Duplicate names will not be accepted.

3.2 Short Description

The Short Description (up to 100 Characters) of the Agent is the text shown on the Info & Options Page just below the Agent name. This should primarily indicate the main use case of the Agent. Any description which misleads the user about the primary use case of the Agent will not be accepted.

3.3 Agent Logo

The Bot Logo is a 224 x 224 pixel image no larger than 90 KB that acts as the identity of the Brand/RBM Agent. It is shown on the bot’s chat tile, conversation screen and info page. The user should be able to associate to the brand with the RBM Agents logo. The logo of the agent needs to adhere to the brand’s guidelines. The logo must not belong to another brand or be trademarked/owned by another brand. Any logo that is misleading the user about the brands association with the Agent will not be accepted.

3.4 Banner Image

The Banner Image is a 1440 x 448 pixel image, no larger than 200 KB, that is shown in the Info & Options Page. This can be any image adhering to the brands branding guidelines. It can depict the Agents use case, promotional offers, tag lines etc. The Brand must have rights to the image. The image must not belong to another Brand or be trademarked/owned by another Brand. Any image that is misleading the End User about the Brands association with the Agent will not be accepted.

3.5 Long Description

The long description of the Agent will be used during verification process and shown on the Agent’s Bot Store Listing. This description is a space to elaborate on the use case of the Agent. Developers/Marketers can explain in detail the bot’s functionality, list its promotional offers, details of the brand, provide a support URL etc.

Any Long Description that misleads the user about the brand or the functionality will not be accepted.

3.6 Agent Screenshots

The Agent Screenshots are used for verification and shown on the Agent’s Bot Store listing. The Agent Screenshots let End Users see how the Agent looks and feels and help the End User understand the Agents functionalities.

The screenshots should only have the screens of the Agent as seen inside the Messages app on a mobile device. These screens should correctly capture the different functions of the agent and should be the same as seen in the Agent.

The minimum number of screenshots to be submitted is 2, and the maximum is 8. Its recommended that the screenshots include one screenshot of the Info & Options Page of the Agent.

3.7 Agent Use Case

Use cases provide Agent insights and provide customized application of business rules. These use cases fulfill specific functions for End Users and help ensure the Agent has appropriate business rules applied. Every Agent is required to have an Agent Use Case assigned to it. Please choose the Agent Use Case carefully, as it cannot be changed after the Agent is launched.

The following three Agent Use Cases are supported for Agents to be launched in India.

1. One Time Password (OTP) - The OTP agent sends a one-time password required to securely authenticate an account or confirm a transaction.
2. Transactional - The Transactional agent sends notifications, updates, or alerts to share information directly relevant to a customer’s existing services or products.
3. Promotional - The Promotional agent sends sales, marketing, and promotional messages to new or existing customers, with the objective to increase awareness, engagement, and sales.

The business rules applicable for Promotional Agents are listed in the following section.

3.8 Business Rules for Promotional Agents:

1. Brands can initiate conversations only during Promotion Initiation Hours.
2. Brands can send four (4) A2P messages per Brand per End User per month (across all Promotional Agents of the Brand), subsequent messages will result in an error. The limitation does not apply to P2A messages. Further, each time an End User responds, the Brand will be allowed two (2) additional messages.

The business rules in India for the three use cases are summarized in the table below for convenience.

Please go here for more details.

4. Guidelines for Agent Assets

• Use an Agent Name that can clearly be associated with your Brand and/or Enterprise, and/or service, that will help build trust with the users communicating with your Agent.
• Your Agent Assets must be the true assets of your Brand and/or Enterprise and mention these names clearly.
• Your Agent Assets cannot use words or images that infringe on a third party’s intellectual property (such as trademarks)
• Your Agent Assets, as visible to End Users cannot feature content that is mature, offensive, or illegal.
• All Agent Assets must be accurate and up to date.
• The Enterprise, Brand, and Agent Assets will be validated as per applicable laws.

5. Brand and Developer Details

Every Agent needs to be associated to a Brand. A Brand is a name or trademark that identifies a product/service or provider of the product/service. The Agent is associated with branding and business information such as colors, images, and contact information. As the Agent is the direct medium for the users to interact with the Brand there should be no ambiguity in the Brands identity. Any misinformation about the Brand will not be accepted.

Each Brand must have a unique Brand Name. Variations of Brand Names are not permitted. (e.g., 724, The 724, 724 Ltd, a 724, are variations of a single Brand Name, an only one of these can be used) Brands are not permitted bypass the Business Rules for Promotional Agents specified in Section 3.8 by using different Brand Names to register different Agents.

The Brand website should be the official online presence of the brand.

The Developer Name is the name of the entity that has developed the Agent - this can be any third-party developer or the Brand itself. The Developer Name is used for verification, reporting, billing, and, if desired, for the Bot Store listing. The Developer Name is not visible to users in the Messages app.

Brands need to provide a logo, identify the industry type they belong to and provide a set of identification documents of the Enterprise who owns the Brand, along with the Brand’s Point of Contact with official contact email as part of submitting the Agent and Brand for verification. Two of the following documents are required for verification of business -

1. PAN Card of the Enterprise
2. GST Document of the Enterprise
3. Certificate of Incorporation of the Enterprise given by Ministry of Corporate Affairs
4. Others (in case none of the above is available, please contact us to see if other available documents can be considered for verification)

6. Policies for Agent Assets

Each Agent is linked to a Brand and a Brand can have multiple Agents associated with it. The following conditions apply when onboarding and launching Agents.

7. Portability

Each Brand has full choice and freedom to work with any Developer of their choice, or even to move from one Developer to another (example, for better service, better price, or as result of M&A). The process of moving Developers is to be initiated by the new Developer (NewD) chosen by the Brand and involves a rigorous verification process to ensure the move is legitimate.

The portability process for moving a Brand’s Agents from its current Developer (CurD) to a NewD is as follows:

• Process is to be led by NewD.
• Brand requests the port in writing by issuing a letter to NewD, with copy to CurD. The letter must include name, title, email, phone number, and address of an authorized person at the Brand who is requesting the port.
• VNS-RBM team will contact the Brand by email and ask for email response to confirm porting.
• VNS-RBM team will contact the Brand by phone for a double confirmation.
• VNS-RBM team may perform additional diligence as appropriate under the circumstances.
• VNS-RBM team will contact CurD to inform CurD of the port.
• NewD can submit Brand's Agents from its account on VIRBM Portal for verification and launch.
• Charges to change the Developer from CurD to NewD will be levied as per new brand onboarding.

8. Functionality for Agents

8.1 Opt-in Functionality

Opt-in is the process of getting consent from Users before sending them messages.

When submitting an agent for verification, the Developers must provide information indicating how the business gets the opt-in from the End Users. This could be via a paper form, an online form, registration, or sign-in, wherein the End User explicitly accepts terms of service which includes the clauses for receiving information from the Enterprise and/or the Brand.

Here are some examples of what you can submit as a proof of Opt-in from the user

1. Online Registration where user explicitly accepts the clause for receiving communication from the business.
2. Offline form filled by users of the brand having opt-in information.

Note:

1. If you as a Brand already have an opt-in for sending SMS messages, it counts as an Opt-in for RCS. Just share the details of the process of getting SMS Opt-in from the users.
2. If you as a Brand already have an opt-in for sending WhatsApp message, it does NOT count as an Opt-in for RCS.

8.2 Opt-out Functionality

All agents must comply with an End User’s request to opt-out (e.g., by sending “STOP” message or equivalent in Agent’s language) and be able to promptly process and adhere to the End Users’ request to opt-out. Developers must implement an opt out functionality in the Agent. This should be explicitly shown in the Agent’s flow. Once the user selects opt-out he should not receive any further A2P messages from the Agent.

The keyword used for Opt-out is to be provided by Developers as part of the verification process. “STOP” and any additional keywords supported for Opt-out should be included when submitting the Agent for verification.

The VNS-RBM team platform also provides help for implementing Stop. The default keyword to opt-out is STOP. The default keyword to cancel the opt-out is START.

8.3 P2A Response Functionality

It is recommended that Developers implement functionality to respond to P2A messages from End Users, wherein the Agent responds to certain keywords, e.g., HI, START, MENU, HELP. Responding to P2A messages is optional. If a response to P2A messages is supported, a response to the keyword “HI” is required. Support for other keywords is optional.

8.4 Other Functionality

Developers should also implement standard commands like RESTART and HELP/MENU. Agents should support restarting of conversations by welcoming the End User with an initial message that lists the standard commands and options End Users can choose to take the conversation forward. These are optional.

9. Privacy and Security Guidelines

• VNS-RBM team and VNS wants users to trust that data about them will be respected and handled with appropriate care.
• All Agents using RBM must be transparent in how they handle End User data (e.g., information provided by an End User, collected about a user or user’s device).
• The Agents must provide a link to their privacy policy and comprehensively disclose how their Agent collects, uses, and shares user data, including the types of parties with whom it’s shared.
• The Agents must limit their data collection and use to the activities required to provide the services offered by the Agent, and as described in the Agent’s Privacy Policy.
• Please note that we prohibit the collection and use of sensitive personal and confidential information over RCDS, such as Permanent Account Number (PAN) or Aadhaar card number, payment, and financial data (e.g., credit card and bank account numbers), log-in credentials, passwords, or answers to security questions.
• When Agents are sending such information, they must appropriately obfuscate or mask it (e.g., only displaying the last 4 digits of a credit card number).
• Do not use any information about the End User’s online or offline state for any reason except to directly provide the services to the user, and under no circumstances in a manner that may surprise or disturb an End User (including, but not limited to, sending a promotion or advertisement based on them coming back online).
• Using or sharing user data without specific End User consent for the specific use of that data is strictly prohibited.

10. Content and Activities Guidelines

10.1 Illegal content and activities

• Keep it legal. Agents, users and third parties are prohibited from using RBM to engage in illegal activities or facilitate the purchases or sales of any illegal products and services.
• Examples include but are not limited to: child sexual abuse imagery, sales of human organs, sales of animal and regulated species, human trafficking activities, and terrorist content.
• It is your responsibility to comply with the applicable laws and regulations in India.

10.2 Spam

To ensure that you do not spam or facilitate transmission of spam, please follow the guidelines below:

• Ensure that you only communicate with users who have explicitly opted into receiving your messages. If the user has opted in to receive SMS messages, it also counts as an opt-in for RCS.
• Do not send unsolicited content, or aggressively message users.
• A Brand is allowed to send a maximum of 4 A2P promotional messages per user per month. The limit of 4 promotional messages per user per month per Brand is across all promotional Agents of the brand. Please see Section 3.8 for details.
• Do not sell, purchase, exchange, or distribute End User phone numbers to a third party, without consent from the End User
• Abide by any applicable local regulations, such as specific opt-in requirements before messaging mobile subscribers, record keeping and opt-out requirements.

10.3 Abuse of the product

Do not misuse RBM. We want RBM to be useful, relevant, and safe for users, thus we do not allow the following:

• Phishing scams
• Attempting to trick other users or third parties for unfair advantages or financial gains
• Circumvent the promotional limit of 4 messages per user per Brand per month by creating fake brands.
• Content or behavior that circumvents, harms, or interferes with the operation of other agents, RBM networks, servers, or other infrastructure.
• Distribution of malicious or unwanted software.

10.4 Misrepresentation and Impersonation

Users should not feel misled by RBM content, and that means Agents should be upfront, honest, and provide them with the information that they need to make informed decisions. RBM content must not represent you or your products or services in a way that is not accurate, realistic, and truthful. For example, the Agents must not:

• Be misleading (e.g., making false statement about the business or qualification, falsely affiliating with other individuals, organizations, products, and services, or making false claims which position improbable results as likely outcomes even if they are technically feasible).
• Conceal or misstate information about the business, product, or service (e.g., using a false or fictitious identity, business name or contact information, offers for products or services that are normally offered for free).
• Contain information which is not clearly relevant to the actual product or service of the Agent.
• Fail to disclose the payment model and full expense that a user will bear (e.g., shipping costs and other billing related information, recurring subscription costs).
• Prompt users to initiate a purchase, download, or other commitment without first providing all relevant information and obtaining the user’s explicit consent.
• Feature content that is provably false and could significantly undermine participation or trust in civic, electoral, or democratic processes such as census participation or public voting procedures.

10.5 Profanity and inappropriate language

Don’t use obscene, profane, or offensive language, or nonsensical content that carries no actual meaning.

10.6 Editorial and technical requirements

To facilitate high quality user experiences, do ensure that your content conforms with the editorial and professional standards as follow:

• Grammar, spelling and spacing: all business content must use commonly accepted spelling, basic grammar and be written in logical sentence form.
• Symbols: no excessive use of numbers, letters, punctuation marks or emoticons.
• Capitalization: business content must not contain excessive or incorrect capitalization.
• Gimmicky text: business content must avoid repetition of words, phrases and punctuation, and should not include any unnecessary or irrelevant text.
• Image and video quality: image and video should not be low quality, unclear, appear sideways or upside downs.
• Opt-out Keyword: STOP, plus any others of your liking.
• P2A Conversation Keyword: Hi, plus any others of your liking.

11. Content policies

Our content policies are categorized into two groups: Prohibited content and Restricted content.

We forbid businesses that operate, feature, or involve with Prohibited content.

You may not a) exclusively promote products or services in Restricted Content areas or (b) send promotional updates, advertisement, or commercial content that exclusively promote the Restricted content using RBM. You may promote products or services in Restricted content areas using RBM if such promotion takes place as part of promoting a wider set of products or services. Always remember to comply with your local laws and regulations.

You may send OTPs for companies dealing with Restricted content and have conversational agents that respond to user-initiated messages.

11.1 Prohibited content

RBM does not support unlawful, offensive, or inappropriate content. This is a non-exhaustive list of content we do not allow:

• Counterfeit goods - Products described as knock off, replica, imitation, clone, faux, fake, mirror image, or similar terms when referring to a brand name to pass themselves off as genuine products of the brand owner.
• Dangerous products or services - Products or services that cause damage, harm, or injury. These include, but are not limited to, recreational drugs, instructional content, or equipment to facilitate drug use, explosive materials, fireworks, weapons, instructions for making explosives or other harmful products.
• Products or services that enable dishonest behaviors - Products, services or content that help users to mislead others such as fake documents, aids to pass drug tests, paper-writing or exam taking services; Products, services or instruction that enable unauthorized access to systems, devices, or property.
• Dangerous or derogatory content - Content, products, or services that:
• Incite hatred against, promote discrimination of, or disparage an individual or group based on their race or ethnic origin, religion, disability, age, nationality, veteran status, sexual orientation, gender, gender identity, or other characteristic that is associated with systemic discrimination or marginalization.
• Harass, intimidate, or bully an individual or group of individuals.
• Threaten or advocate for harm on oneself or others.
• Seek to exploit others (e.g., blackmail, soliciting or promoting dowries).
• Inappropriate use of flags, national emblems, or religious icons and imagery.
• Shocking content - Content, products, or services that:
• Contain violent language, gruesome or disgusting imagery, or graphic images or accounts of physical trauma.
• Contain gratuitous portrayal of bodily fluids or waste.
• Contain obscene or profane language.
• Likely cause shock, scare or disgust
• Capitalizing on sensitive events - Content which may be deemed as capitalizing on or lacking reasonable sensitivity towards a natural disaster, conflict, death, or other tragic event with no discernible benefit to the victims.
• Animal cruelty - Content that promotes or depicts cruelty or gratuitous violence towards animals, or which may be interpreted as trading in or selling products derived from threatened or extinct species.
• Adult content - Content, products or services that are sexually explicit, sexually suggestive, or promote sexual themes, activities, or escort services. Content promoting the sexual exploitation of minors, such as child sexual abuse imagery, is strictly prohibited.
• Tobacco - Content, products or services that promote sales or consumption of tobacco, products containing tobacco, component parts of tobacco or products designed to simulate smoking behaviors.
• Political Content - Business to consumer messages may not include content or services related to political campaigns such as those that promote or undermine a political figure or party, conduct opinion polls or political surveys, discuss election integrity, or predict election results. Any other political content that is not prohibited by this policy must comply with local laws and regulations.
• Hate and Violence – Content or services promoting hate, violence, or intolerance based on race, age, gender, gender identity, ethnicity, religion, or sexual orientation.
• Unauthorized content – Content, products, or services that are unauthorized to use copyrighted or trademarked content, or other legally prohibited content.
• Firearms, weapons, or ammunition - Content, products or services that promote weapons or other ammunitions

11.2 Restricted content

Agents cannot send advertisements, or promotional content that are related to restricted content. OTP and Transactional messages related to restricted content can be sent. Agents are allowed to respond to P2A messages that relate to restricted content, provided it is clear to the user that restricted content will be sent. Below is a non-exhaustive list of restricted content categories:

• Alcohol - Content, products or services that promote branding, sales, promotion, or consumption of alcoholic beverages. Content that promotes irresponsible alcohol consumption is prohibited.
• Gambling and games - Gambling related content, products, or services, which include but are not limited to legal gambling activities such as: physical casinos, offline and online gambling activities, national or private lottery, promotional offers for gambling sites, and social casino games.
• Healthcare related products and services - Content, products, or services that promote branding or sales of prescription drugs, over-the-counter medicines, medical suppliers, online pharmacy, HIV home test, abortion, birth control products, and miracle cures products or services.

12. Violation of Guidelines

Depending on how egregious a violation is, VNS-RBM team and VNS may respond in several different ways. Below is a list of various ways we enforce policies.

12.1 Pre-Launch - Agent Submission Rejection

VNS-RBM team verifies all Agent details when the developer submits agents for launch. The request for launch is rejected if the Agent violates any of the requirements and the Developer is notified over email.

Developers can resubmit the Agent for launch once the problem is fixed.

12.2 Post-Launch - Services suspension

VNS-RBM team may suspend RBM services on Launched Agents that violate RBM policies. This means that the Agents can no longer use RBM services until the problem is fixed and passed a policy review.

12.3 Account suspension

We may suspend your account if you have several violations or a serious violation. If this happens, all Agents from your account will be disabled. Any related accounts, including your new account, may be automatically suspended. We may report any illegal activity if required by law.

13. Verification Process

The Agent should be submitted for verification and launch by the Developer upon successful completion of the testing of the Agent. As part of verification, we check the following:

• Agent Name submitted is Unique.
• Brand Verification: The Brand Point of Contact (POC) domain matches the domains included in the Agent Assets (primary domain, privacy policy domain, terms of service domain)
• The Bot branding matches the web branding of the Brand.
• Agent should comply to the Policy Guidelines outlined in this document.
• Opt-in – Brand has obtained the opt-in from targeted End Users
• Opt-out – The agent acknowledges and respects the End User’s request for opt-out
• Agent Use Case – The Agent Use Aase should be appropriately configured according to the definitions of the Agent Use Cases
• A confirmation response by email (Reply ALL) from the point of contact at the Brand to the verification email, as per the Brand Verification Email template outlined below.

Brand Verification Email (Letter of Authorization (LOA)

Subject: VI RBM: Please approve brand use for RCS Business Messaging

To: [ BRAND POC ]

Hi [ BRAND POC ],

[DEVELOPER] has registered an RCS Business Messaging (RBM) agent with VNS RBM on behalf of your company. Registration allows [DEVELOPER] to send messages on behalf of your company to users that are reachable from VNS RBM Platform.

We have received a request from [DEVELOPER] to launch this agent, which has the following information:

Agent name: [ AGENT NAME ]
Agent logo: [ AGENT LOGO URL ]
Agent hero image: [ AGENT HERO IMAGE URL ]
Agent description: [ AGENT DESCRIPTION ]
Contact Person at [ DEVELOPER ] :
Terms of service: [ TOS URL ]
Privacy policy: [ PRIVACY POLICY URL ]
Agent ID: [ AGENT ID ]

Your approval is required in order to

(a) validate the correctness of the information above, and

(b) confirm that [DEVELOPER] has the right to control an RBM agent that represents your brand. We would like to obtain your approval to continue the launch.

To grant your approval, respond with the following: “I, [BRAND POC] as a company representative, grant [DEVELOPER] the right to operate an RCS Business Messaging agent using the information specified in this email.”

Feel free to reach out to us at rbm.virtuosonetsoft@virtuosonetsoft.in for any queries!

Thanks,

THE VNS-RBM TEAM