[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-07-09 UTC。"],[[["\u003cp\u003eRBM agents are categorized into four distinct use cases: One-time passwords (OTP), Transactional, Promotional, and Multi-use.\u003c/p\u003e\n"],["\u003cp\u003eEach use case has specific rules and limitations regarding the type of messages that can be sent, which may vary by country.\u003c/p\u003e\n"],["\u003cp\u003eThe Multi-use agent is unique in that it can send a combination of both transactional and promotional messages within a single conversation flow.\u003c/p\u003e\n"],["\u003cp\u003eAgents operating in India have specific business rules, including time-of-day restrictions for promotional messages and a monthly message limit per user.\u003c/p\u003e\n"],["\u003cp\u003eOTP, Transactional, and Promotional use cases are available globally, whereas the Multi-use use case is not available in India.\u003c/p\u003e\n"]]],[],null,["Every RBM agent needs a predefined use case. This helps categorize your agent\nand apply the right [business rules](#businessrules) for a good user experience.\n\nRBM supports four use cases:\n\n- One-time passwords (OTP)\n- Transactional\n- Promotional\n- Multi-use\n\nEach use case has rules about what you can send, which may vary by country. To\nlearn more about each use case and find the best fit for your agent, review the\ndetailed descriptions.\n\nChoose the right use case for your agent\n\nOne-time passwords (OTP)\n\nThe OTP agent sends a one-time password required to securely authenticate an\naccount or confirm a transaction. You can use this agent for:\n\n- OTP / 2FA for account login\n- Password resets\n- Completing online commercial transactions\n\nThis use case can't include:\n\n- Product information or notifications\n- Offers, promotions, discounts, upgrades, or information related to goods and services\n\nTransactional\n\nThe Transactional agent sends notifications, updates, or alerts to share\ninformation directly relevant to a customer's existing services or products.\nFor example:\n\n- Fraud and suspicious activity notifications\n- Purchase confirmations for goods and services (appointment and ticket confirmations)\n- Updates to a customer's existing products or services (boarding pass, airport gate, shipping information, and appointment updates)\n- Product or account information and updates (account statement, customer status, terms of use, warranty, or product safety)\n- Requesting feedback about a purchased product or ongoing service\n- Editorial and media content (newsfeeds and news alerts)\n\nThis use case can't include:\n\n- Offers, promotions, discounts, or upgrades for new or existing products and services\n\nPromotional\n\nThe Promotional agent sends sales, marketing, and promotional messages to new or\nexisting customers, with the goal of increasing awareness, engagement, and\nsales. For example:\n\n- Offers, promotions, discounts, upgrades for new or existing products and services\n- Follow-ups to complete commercial transactions that the user has started with the business, such as a reminder about an abandoned shopping cart\n\nThis use case can't include:\n\n- OTP and 2FA for account login\n- Time-sensitive product and service information or transactions\n\nMulti-use\n\nThe Multi-use agent sends a combination of transactional and promotional\nmessages, such as sending an account notification followed by a discount offer\nor upgrade for a new product or service. You can only use this agent **for\nconversations that include both transactions and promotions**. For example:\n\n- A transaction that's followed by related promotions or sales, such as when an airline sends a boarding pass, then offers a seat upgrade.\n- A promotion that leads to a purchase, followed by payment confirmation, shipping notifications, and customer satisfaction survey.\n- A promotion that leads to account creation, followed by regular account updates and notifications, such as appointment reminders.\n- Sending pins, passwords, and passcodes for completing transactions that are part of the conversation flow.\n\nThis use case can't include:\n\n- OTP and 2FA for account login\n- Password resets and any other information for secure account access\n- Transactional-only use cases\n- Promotional-only use cases\n\nYou can request to launch a multi-use agent with only one active use case\ndefined (either promotional or transactional). However, you are still required\nto implement the second use case and provide proof to the RBM Support team\nwithin six months of the agent's launch. For more information, see\n[Submit a launch request](/business-communications/rcs-business-messaging/guides/launch/launch-approval#submit-launch-request).\n\nUse cases and business rules\n\nRBM agents need to follow specific requirements depending on the country of\nsubscribers they are reaching. Use case availability and business rules vary by\ncountry and may be updated over time.\n\n| Use cases | Available countries |\n|---------------------------------|------------------------|\n| [OTP](#OTP) | Globally |\n| [Transactional](#transactional) | Globally |\n| [Promotional](#promotional) | Globally |\n| [Multi-use](#multiuse) | Not available in India |\n\nThe following table outlines the business rules that specifically apply to\n**RBM agents operating in India**.\n\n| Use cases | Business rules - Applicable in India only |\n|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [Promotional](#promotional) | Time of day: Businesses can only initiate conversations between 7 AM and 10 PM (7 days a week). Message limits: Initial monthly (28-day) limit is **four** A2P messages per brand per user. Google may adjust this based on agent performance. Messaging beyond this limit results in an error. **Note** : This limit excludes P2A messages. Each user response allows **two** additional brand messages. |"]]
