When you message someone who also has RCS chats turned on in Google Messages, your chat conversations automatically upgrade to end-to-end encryption. With end-to-end encryption, no one can read the content sent between you and the other person.
Messages sent between users and agents are encrypted between RCS Business Messaging (RBM) agents and Google servers and between Google servers and users’ devices. Agents can’t use their own encryption keys because Google needs to scan messages for malicious content to protect all users and businesses. Messages received on users’ devices are encrypted by any device-wide encryption that users have configured for their devices, and Google deploys on-device security models to protect message data.
For more information on RCS, visit the Sinch RCS product page.
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.