new_releases 更新:查看
版本資訊瞭解新功能和產品更新。
服務專員用途和業務規則
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
每個 RBM 代理程式都需要預先定義的使用案例。這有助於分類代理程式,並套用正確的業務規則,提供良好的使用者體驗。
RBM 支援四種用途:
每種用途都有相關規定,說明可傳送的內容,且各國家/地區的規定可能有所不同。如要進一步瞭解各個用途,並找出最適合您代理程式的用途,請參閱詳細說明。
為虛擬服務專員選擇合適的用途
動態密碼
動態密碼代理程式會傳送一次性密碼,用於安全地驗證帳戶或確認交易。這個代理程式可用於:
- 帳戶登入的動態密碼 / 雙重驗證
- 重設密碼
- 完成線上商業交易
這個用途不得包含:
- 產品資訊或通知
- 商品和服務的優惠、促銷活動、折扣、升級或相關資訊
交易
交易型代理程式會傳送通知、最新消息或快訊,直接分享與顧客現有服務或產品相關的資訊。例如:
- 詐騙和可疑活動通知
- 商品和服務的購買確認 (預約和票券確認)
- 更新顧客現有產品或服務的資訊 (登機證、機場登機門、運送資訊和預約更新)
- 產品或帳戶資訊和更新 (帳戶對帳單、客戶狀態、使用條款、保固或產品安全)
- 要求提供有關已購買產品或持續性服務的意見
- 編輯和媒體內容 (動態消息和新聞快訊)
這個用途不得包含:
促銷活動代理程式會向新客或現有顧客傳送銷售、行銷和促銷訊息,以提高知名度、參與度和銷售量。例如:
- 新舊產品和服務的優惠、促銷活動、折扣、升級
- 後續追蹤使用者與商家進行的商業交易,例如提醒使用者購物車中有未結帳商品
這個用途不得包含:
- 帳戶登入的動態密碼和兩步驟驗證
- 時效性產品和服務資訊或交易
多次使用
多用途代理程式會傳送交易和宣傳訊息,例如傳送帳戶通知,然後提供新產品或服務的折扣優惠或升級方案。您只能將這個代理程式用於包含交易和促銷活動的對話。例如:
- 交易後續有相關促銷活動或銷售,例如航空公司傳送登機證後,提供升等座位。
- 促銷活動促成購買交易,接著確認付款、傳送出貨通知,並進行顧客滿意度調查。
- 宣傳活動會引導使用者建立帳戶,然後定期提供帳戶更新和通知,例如預約提醒。
- 傳送 PIN 碼、密碼和驗證碼,以完成對話流程中的交易。
這個用途不得包含:
- 帳戶登入的動態密碼和兩步驟驗證
- 密碼重設和任何其他可確保帳戶安全存取權的資訊
- 僅限交易用途
- 僅限宣傳用途
您只能要求啟動定義單一有效用途的多用途代理程式 (宣傳或交易)。不過,您仍須在代理程式發布後六個月內,實作第二個用途並向 RBM 支援團隊提供證明。詳情請參閱「提交發布要求」。
用途和業務規則
RBM 代理商必須遵守特定規定,具體規定視觸及的訂閱者所在國家/地區而定。用途和業務規則因國家/地區而異,且可能會隨時間更新。
下表列出在印度營運的 RBM 代理商須遵守的具體業務規則。
用途 |
業務規則 - 僅適用於印度 |
宣傳 |
時間:商家只能在上午 7 點到晚上 10 點之間發起對話 (全年無休)。
訊息上限:每位使用者每個月 (28 天) 的 A2P 訊息上限為四則。Google 可能會根據服務專員的成效調整這項設定。如果超出這項限制,系統就會傳回錯誤。
注意:這項限制不包括 P2A 訊息。每則使用者回覆最多可觸發兩則額外品牌訊息。 |
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-07-09 (世界標準時間)。
[null,null,["上次更新時間: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. |"]]