Each RBM agent is required to have a predefined use case that reflects the nature of the conversations it is intended to have with end users and to help businesses comply with business rules. RBM supports four use cases:
OTP |
One-time passwords required to securely authenticate an account or confirm a transaction. |
Transactional |
Notifications, updates or alerts to share information directly relevant to a 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 and service. |
Refer to the Choose the right use case article on the Google developers site, for a more details about when to use each use case.
Watch the video below to learn how to start sending RCS messages with Sinch:
After registering your sender agent with Sinch, the video tutorial guides you through the set up process on the Sinch Dashboard.
You can learn how to send different types of RCS messages from the developer perspective and review what that looks like in real-time when it comes to what your customer will be seeing on their handset.
To learn more you can read our comprehensive developer documentation for RCS, which shows you how to build your business' RCS experience.