Sinch Community

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. ... View more

Carriers that approve RBM content on their networks also bill for delivering RBM messages to their subscribers using the following billing framework: Conversational - A charge for a conversation that consists of multiple A2P and P2A messages within a given time-period. Single Message - A charge for a single message containing rich RBM content (such as a message containing a Rich Card or Carousel). Basic Message - A charge for a plain text message of up to 160 UTF-8 characters. Billing categories do not impact the functionality of your agent, but it’s important to understand the purpose of each one, to ensure your agents behaviour is best represented:   Conversational - This agent engages in complex user interactions where messages are exchanged in both directions. The following two categories never create conversational billing events - carriers will charge a Basic Message or Single Message price for each message, depending on the content that is delivered: Single Message - This agent generally sends rich messages or messages over 160 characters in length and seldom expects to receive replies. Basic Message - This agent implements SMS upgrade to RBM and seldom expects to receive replies. Generally, the agent is expected to send plain text messages of up to 160 UTF-8 characters. But the agent is not restricted; it can send richer content if so programmed and will be billed accordingly. When you create your agent in Sinch, you will have the option to select between two categories Transactional and Conversational. Transactional agents include both the Single and Basic message types. You are not required to pick between them.    Important Notes:  You can change your agent's billing category before you launch your agent.  Contact your Sinch Account Manager, to discuss changing to a different billing category post-launch. If an agent is registered as Basic or Single all messages sent by the agent are billed as Basic or Single, they never convert to a Conversational billing model. If an agent is registered as a Conversation it is billed as a Basic or Single unless an P2A message comes back within 24 hours. If an P2A message comes back it is billed as a Conversational agent (conversations last for 24 hours from the P2A message).  If multiple A2P messages are sent before the first P2A message only the A2P message immediately preceded by that P2A message is part of the conversation. The initial messages are billed as Basic or Single.  ... View more

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. ... View more

All RCS Business Messaging (RBM) agents must go through verification and approval as part of the launch process. This is key to the security of RBM and enables the messages to come from a verified sender.    RBM Agents can be submitted for approval and launch on one or more carriers. The steps and criteria for launch differ depending on the carriers selected: Some carriers are managed by Google. Agents submitted for launch on these carriers are reviewed by Google and if all criteria are met, approved by them for launch. Google will connect with someone who works at the brand to verify details.  Other carriers approve and manage their own agent launches. Google is not involved in this process. Each carrier has their own process for approval and launch and may require additional information beyond what Google requires.     Note that regardless of who manages the agent it will be un-launched if it is determined to violate Google’s Acceptable Use Policy.    Sinch is working closely with Google and Carriers around the world to support and manage RBM launches. Please contact Sinch if you have any questions or to get started with RBM.  ... View more

The following use cases showcase how Sinch helped customers achieve great success using RCS.   How Picard increased customer engagement by 42% with RCS   What the video to find out how frozen food retailer Picard integrated Sinch’s chatbot builder with our conversation API leveraging RCS to create an engaging customer experience:     Picard’s mission is to “continually nurture the love of good food”. They brought this to life with RCS (Rich Communication Services) by creating a conversational experience that takes the stress out of planning your holiday menu. Read the full story on sinch.com.    How EasyPark Group keeps users informed with RCS   What the video to find out how EasyPark Group, a leader in digital parking solutions, leverages Sinch's SMS and RCS (Rich Communication Services) technologies to improve customer experience for millions of monthly users across 20+ countries:     In the video, Alex Keynes, Head of Product for the driver's experience at EasyPark, shares the impact of switching to a single communications partner. By switching to Sinch for all markets, EasyPark Group simplified their messaging infrastructure without sacrificing a high-quality driver experience. “Sinch is reliable, their delivery rates are high, and they’re not taking any shortcuts,” Alex explained. “For us, this is something that we can rely on and that we don't need to spend a lot of time on.” Read the full case study on sinch.com. ... View more

Watch the video below to learn how RCS can be used to combat fraud:   RCS has many powerful capabilities to combat fraud and ensure a safer messaging experience for all: The tightly controlled ecosystem of RCS prevents spam, fraud, and phishing on SMS channels by implementing stricter controls and authentication measures. RCS messaging makes impersonation nearly impossible, unlike SMS where anyone can easily set up and send messages using any sender ID. Google only allows trusted partners to create sender agents on behalf of brands, requiring permission from both the brand and mobile operators to run messages using their brand. RCS provides an additional layer of protection for end users. By displaying the brand's logo in the message, users can validate that they are indeed communicating with the intended brand, such as their bank. For more information on RCS, visit the Sinch RCS product page. ... View more

The table below compares the features of RCS with SMS, MMS and WhatsApp:     What’s the difference between RCS and SMS? See our blog here for all the details.   What’s the difference between RCS and WhatsApp? See our blog here for all the details.   For more information on RCS, visit the Sinch RCS product page. ... View more