<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Setting a required predefined Use Case during the RCS Agent registration process in RCS</title>
    <link>https://community.sinch.com/t5/RCS/Setting-a-required-predefined-Use-Case-during-the-RCS-Agent/ta-p/15730</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;Each RCS 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&amp;nbsp;&lt;A href="https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-are-use-cases#businessrules" target="_blank" rel="noopener"&gt;business rules&lt;/A&gt;. RCS for Business supports four primary use cases:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;TABLE width="698px"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;OTP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; One-time passwords for authentication, account login, password resets, and completing or confirming transactions&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include product updates, notifications, offers, promotions, discounts, upgrades, or information related to goods and services&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Transactional&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; 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. You can send OTP on transactional.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include marketing or promotional messages&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Promotional&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Sales, marketing and promotional messages to new or existing customers, with the objective to increase awareness, engagement and sales&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include OTP and 2FA, time-sensitive product and service information, or transactions&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Multi-use&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; 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. Must include a combination of transactional and promotional messages &lt;EM&gt;(note: you can declare an agent as "multi-use" in your agent launch request, even if you only have one active use case. If you declare multi-use with one use case, you must confirm that you plan to implement the second use case within the next six months).&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include OTP messages, password resets, or only promotional/only transactional use cases&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&lt;BR /&gt;Refer to the&amp;nbsp;&lt;A href="https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-are-use-cases#choose_the_right_use_case_for_your_agent" target="_blank" rel="noopener"&gt;Choose the right use case&lt;/A&gt;&amp;nbsp;article on the Google developers site, for more details about when to use each use case or &lt;A href="https://sinch.com/apis/messaging/rcs/#form" target="_blank" rel="noopener"&gt;reach out to us&lt;/A&gt; for support.&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Wed, 02 Jul 2025 14:46:21 GMT</pubDate>
    <dc:creator>Shahzad_Ismail</dc:creator>
    <dc:date>2025-07-02T14:46:21Z</dc:date>
    <item>
      <title>Setting a required predefined Use Case during the RCS Agent registration process</title>
      <link>https://community.sinch.com/t5/RCS/Setting-a-required-predefined-Use-Case-during-the-RCS-Agent/ta-p/15730</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;Each RCS 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&amp;nbsp;&lt;A href="https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-are-use-cases#businessrules" target="_blank" rel="noopener"&gt;business rules&lt;/A&gt;. RCS for Business supports four primary use cases:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;TABLE width="698px"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;OTP&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; One-time passwords for authentication, account login, password resets, and completing or confirming transactions&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include product updates, notifications, offers, promotions, discounts, upgrades, or information related to goods and services&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Transactional&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; 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. You can send OTP on transactional.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include marketing or promotional messages&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Promotional&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; Sales, marketing and promotional messages to new or existing customers, with the objective to increase awareness, engagement and sales&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include OTP and 2FA, time-sensitive product and service information, or transactions&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="131.945px"&gt;
&lt;P&gt;&lt;STRONG&gt;Multi-use&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="565.055px"&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":white_heavy_check_mark:"&gt;✅&lt;/span&gt; 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. Must include a combination of transactional and promotional messages &lt;EM&gt;(note: you can declare an agent as "multi-use" in your agent launch request, even if you only have one active use case. If you declare multi-use with one use case, you must confirm that you plan to implement the second use case within the next six months).&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":cross_mark:"&gt;❌&lt;/span&gt; Cannot include OTP messages, password resets, or only promotional/only transactional use cases&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&lt;BR /&gt;Refer to the&amp;nbsp;&lt;A href="https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/what-are-use-cases#choose_the_right_use_case_for_your_agent" target="_blank" rel="noopener"&gt;Choose the right use case&lt;/A&gt;&amp;nbsp;article on the Google developers site, for more details about when to use each use case or &lt;A href="https://sinch.com/apis/messaging/rcs/#form" target="_blank" rel="noopener"&gt;reach out to us&lt;/A&gt; for support.&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 02 Jul 2025 14:46:21 GMT</pubDate>
      <guid>https://community.sinch.com/t5/RCS/Setting-a-required-predefined-Use-Case-during-the-RCS-Agent/ta-p/15730</guid>
      <dc:creator>Shahzad_Ismail</dc:creator>
      <dc:date>2025-07-02T14:46:21Z</dc:date>
    </item>
  </channel>
</rss>

