new_releases 更新:查看
版本資訊瞭解新功能和產品更新。
驗證並發布虛擬服務專員
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
如果服務專員已完成全面測試,且可供使用者使用,你就可以開始進行推出程序。您可以在一或多個電信網路中提交代理程式以供發布。發布程序包括:
- 品牌驗證:
授權品牌代表會確認服務專員資訊,以及你代表品牌管理服務專員的權利。
- 啟用核准:Google、電信業者或兩者皆核准你的代理程式和啟用資訊。
代理程式通過啟用審查後,就能在核准的電信業者網路上,與支援 RBM 的使用者互動。
Google 管理的發布與電信業者管理的發布
部分發布作業由 Google 管理,其他則由電信業者直接管理:
- Google 管理的發布程序:Google 會管理電信業者的品牌驗證和發布核准程序。
- 電信業者管理啟用:電信業者直接管理自家網路的品牌驗證和啟用核准程序。
如果是電信業者管理的發布作業,你必須先與電信業者簽訂直接協議,他們才會核准發布服務專員。如果電信業者與你沒有合約,就會拒絕發布,並可能與你聯絡以建立合作關係。
如要瞭解這些電信業者,請參閱 Business Communications 開發人員控制台的「發布」頁面。「選取電信業者」表單 (如「提交啟用要求」一節所述) 會列出可啟用服務專員的電信網路。
- 標有「資訊」圖示 info 的電信業者會執行電信業者管理的啟用程序,且可能設有額外規定。如需瞭解詳情,請直接與對方聯絡。
- 未標示資訊圖示 info 的貨運公司
會遵循 Google 管理的發布程序。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-27 (世界標準時間)。
[null,null,["上次更新時間:2025-08-27 (世界標準時間)。"],[[["\u003cp\u003eLaunching an agent involves submitting it for approval on carrier networks, which includes brand verification and launch approval by Google, carriers, or both.\u003c/p\u003e\n"],["\u003cp\u003eThere are two types of launches: Google-managed, where Google handles verification and approval, and carrier-managed, where the carrier handles these processes directly.\u003c/p\u003e\n"],["\u003cp\u003eBrand verification requires an authorized representative to confirm the agent's information and management rights, and it only needs to be done once per agent before the first launch request.\u003c/p\u003e\n"],["\u003cp\u003eBefore launching, you must complete prerequisites such as filling out agent information, testing agent functionality, and implementing an opt-out flow.\u003c/p\u003e\n"],["\u003cp\u003eThe launch request process involves submitting agent details, selecting carriers, and confirming, after which the agent's launch status can be tracked in the Business Communications Developer Console.\u003c/p\u003e\n"]]],[],null,["When your agent is fully tested and ready for users, it's time to launch. You\ncan submit the agent for launch on one or more carrier networks. The launch\nprocess includes:\n\n1. [Brand verification](/business-communications/rcs-business-messaging/guides/launch/brand-verification): An authorized brand representative confirms your agent information and your right to manage the agent on their behalf.\n2. [Launch approval](/business-communications/rcs-business-messaging/guides/launch/launch-approval): Google, carriers, or both approve your agent and launch information.\n\nOnce your agent is approved for launch, it will be able to reach RBM-capable\nusers on the approved carrier networks.\n\nGoogle-managed vs. Carrier-managed launches\n\nSome launches are managed by Google and others are managed directly by\ncarriers:\n\n- **Google-managed launch:** Google manages brand verification and launch approval for the carrier.\n- **Carrier-managed launch:** The carrier directly manages brand verification and launch approval for their network.\n\nFor carrier-managed launches, you must have a direct agreement with the carrier\nbefore they will approve your agent for launch. The carrier will reject your\nlaunch if they have no contract in place with you, and they may contact you\nto establish a relationship.\n\nTo identify which carriers these are, refer to the **Launch** page in the\nBusiness Communications Developer Console. The **Select carriers** form\n(described in\n[Submit a launch request](/business-communications/rcs-business-messaging/guides/launch/launch-approval#submit-launch-request))\nlists the carrier networks where your agent can launch.\n\n- Carriers marked with an info icon info perform carrier-managed launches, and they may have additional requirements. Contact them directly for more information.\n- Carriers that **are not** marked with an info icon info follow the Google-managed launch process."]]