Setting a required predefined Use Case during the RCS Agent registration process

✅ One-time passwords for authentication, account login, password resets, and completing or confirming transactions

❌ Cannot include product updates, notifications, offers, promotions, discounts, upgrades, or information related to goods and services

✅ 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. 

❌ Cannot include marketing or promotional messages

✅ Sales, marketing and promotional messages to new or existing customers, with the objective to increase awareness, engagement and sales

❌ Cannot include OTP and 2FA, time-sensitive product and service information, or transactions

✅ 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 (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).

❌ Cannot include OTP messages, password resets, or only promotional/only transactional use cases