new_releases 更新:查看
版本说明,了解新功能和产品动态。
代理使用场景和业务规则
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
每个 RBM 代理都需要预定义用例。这有助于对代理进行分类,并应用合适的业务规则,从而提供良好的用户体验。
RBM 支持以下四种用例:
每种用例都有关于您可以发送的内容的规则,这些规则可能因国家/地区而异。如需详细了解每种使用情形,并找到最适合您代理的应用场景,请查看详细说明。
为代理选择合适的使用场景
动态密码 (OTP)
OTP 代理会发送一次性密码,用于安全地验证账号或确认交易。您可以使用此代理执行以下操作:
- 用于账号登录的 OTP / 2FA
- 密码重置
- 完成在线商业交易
此使用情形不得包含以下内容:
- 商品信息或通知
- 与商品和服务相关的优惠、促销、折扣、升级或信息
交易消息
事务性代理会发送通知、更新或提醒,以直接分享与客户现有服务或产品相关的信息。例如:
- 欺诈和可疑活动通知
- 商品和服务的购买确认(预约和门票确认)
- 客户现有产品或服务的更新(登机牌、机场登机口、配送信息和预约更新)
- 产品或账号信息和更新(账单、客户状态、使用条款、保修或产品安全)
- 请求用户提供有关所购产品或正在使用的服务的反馈
- 编辑和媒体内容(信息流和新闻提醒)
此使用情形不得包含以下内容:
- 针对新产品或现有产品及服务的优惠、促销、折扣或升级
促销代理会向新客户或现有客户发送销售、营销和促销消息,以期提高认知度、互动度和销售额。例如:
- 针对新产品或现有产品及服务的优惠、促销、折扣、升级
- 后续跟进,以完成用户已开始与商家进行的商业交易,例如有关用户放弃购物车的提醒
此使用情形不得包含以下内容:
- 账号登录的动态密码和双重身份验证
- 时效性产品和服务信息或交易
多次使用
多用途代理会发送事务性消息和促销消息的组合,例如先发送账号通知,然后发送新产品或服务的折扣优惠或升级优惠。您只能将此代理用于同时包含交易和促销信息的对话。例如:
- 交易完成后,系统会提供相关促销或销售信息,例如航空公司在发送登机牌后,提供升舱服务。
- 促销活动促成购买交易,然后是付款确认、发货通知和客户满意度调查。
- 促使客户创建账号的促销活动,随后定期向客户发送账号更新和通知,例如预约提醒。
- 发送 PIN 码、密码和通行码,以完成对话流程中的交易。
此使用情形不得包含以下内容:
- 账号登录的动态密码和双重身份验证
- 密码重置和任何其他有助于安全访问账号的信息
- 仅限交易的使用情形
- 仅限促销活动的应用场景
您可以请求启动仅定义了一个有效使用情形(促销或交易)的多用途代理。不过,您仍需在代理发布后的 6 个月内实现第二种使用情形,并向 RBM 支持团队提供证明。如需了解详情,请参阅提交发布申请。
使用情形和业务规则
RBM 代理需要遵循特定要求,具体取决于其覆盖的订阅者所在的国家/地区。使用情形的适用范围和业务规则因国家/地区而异,并且可能会随时更新。
下表列出了专门适用于在印度运营的 RBM 代理的业务规则。
使用场景 |
业务规则 - 仅适用于印度 |
宣传 |
一天中的时间:商家只能在上午 7 点到晚上 10 点之间(每周 7 天)发起对话。
消息限额:初始每月(28 天)限额为每个品牌每个用户 4 条 A2P 消息。Google 可能会根据客服人员的表现调整此值。超出此限制的即时通讯会导致错误。
注意:此限制不包括 P2A 消息。每次用户回复后,系统会允许再显示 2 条品牌消息。 |
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-09。
[null,null,["最后更新时间 (UTC):2025-07-09。"],[[["\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. |"]]