new_releases 更新：查看
版本資訊瞭解新功能和產品更新。
RCS Business Messaging 的運作方式
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
RCS Business Messaging (RBM) 服務專員可透過訊息與使用者溝通，
事件，以及有助於達成業務目標的要求。這些目標
簡單 (例如傳送遞送通知) 或複雜 (例如預訂
虛擬服務專員會使用複合式資訊卡、媒體和建議來引導使用者
即時流暢對話，滿足使用者與服務專員的需求
運作方式
代理程式和使用者之間的對話流程與
兩人之間的對話，每一方輪流發言，
以及回應對方
你的 RBM 服務專員開啟了與使用者對話。使用者無法啟動
與代理程式對話，但服務專員發起對話後
使用者隨時都可回覆
代理程式會在收到外部觸發條件時傳送第一則訊息
每個 Pod 都有專屬的 IP 位址觸發條件可以是任何內容，視代理程式的用途而定：
- 包裹出貨
- 立刻送出午餐時間三明治特惠
- 使用者在即時通訊中與客戶服務團隊聯絡
代理程式收到觸發條件後，代理程式會傳送訊息
透過 RCS Business Messaging API 連線至使用者的裝置。服務專員會將所有訊息
透過 RBM API 以 HTTP 傳送的訊息、事件和其他要求
內含 JSON 酬載的要求使用者在「訊息」應用程式中收到訊息
在裝置上。
如果裝置不支援 RCS，RBM 平台會傳回 404 錯誤，且
服務專員應改用其他技術，如簡訊
當使用者回覆訊息或觸發
event、
Google 的 RBM 服務將回應傳送到
Webhook
然後將資訊傳回代理程式。Webhook 傳送
所有使用者訊息、事件，以及以 JSON 格式傳送至代理程式的其他要求。
服務專員收到訊息後，
解碼 JSON 並剖析回應使用內部邏輯或依賴
自然語言理解 (NLU) 模組，例如
Dialogflow 時，代理程式會決定
透過 RBM API 將回應傳送至使用者的裝置。
服務專員和使用者之間的對話會持續，直到觸及
或是使用者停止回應
範例
以下範例是一個簡單的情境，其中使用者要求取得天氣資訊
更新。
- 虛擬服務專員收到外部服務的觸發條件，表示
使用者要求取得最新天氣資訊。
- 您的代理程式會傳送訊息給使用者，確認使用者的要求並
要求取得使用者的位置
- 使用者在「訊息」應用程式中閱讀訊息，並回應
讓我們看看 DNS 解析
進一步探索內部和外部位址
- 代理程式會處理回應、擷取天氣資訊、
對話訊息，然後將相關資訊傳送給使用者。此外，
代理程式會詢問使用者是否也想使用其他的天氣資訊
或 HTTP/HTTPS 位置
- 使用者閱讀訊息並感謝服務專員。
- 您的代理程式確認使用者未要求其他資訊
並結束對話
加密
使用者和服務專員之間傳送的 RBM 訊息都會經過加密。
Google 伺服器，以及在 Google 伺服器和使用者裝置。合作夥伴無法使用
自己的加密金鑰，因為 Google 需要掃描郵件是否含有惡意內容
保障所有使用者和企業的安全。
如要進一步瞭解 RBM 資料安全性，請參閱
RCS Business Messaging 的資料安全性。
後續步驟
掌握這些概念後，請思考您想要
建立及建構第一個代理程式。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2024-09-02 (世界標準時間)。
[null,null,["上次更新時間：2024-09-02 (世界標準時間)。"],[[["\u003cp\u003eRCS Business Messaging (RBM) agents use messages, events, and requests to communicate with users, achieving business goals through rich cards, media, and suggestions.\u003c/p\u003e\n"],["\u003cp\u003eRBM agents initiate conversations based on external triggers such as a package shipping or a user contacting customer support, sending messages through the RBM API.\u003c/p\u003e\n"],["\u003cp\u003eUser responses and events are sent to a configured webhook, which relays the information back to the agent for processing.\u003c/p\u003e\n"],["\u003cp\u003eThe agent decodes the user's response, decides on a follow-up action, and then sends its reply back to the user through the RBM API, continuing the conversation.\u003c/p\u003e\n"],["\u003cp\u003eRBM messages are encrypted between RBM agents and Google servers and between Google servers and user devices, with Google scanning messages for malicious content.\u003c/p\u003e\n"]]],[],null,["# How RCS Business Messaging works\n\nRCS Business Messaging (RBM) agents communicate with users through messages,\nevents, and requests to achieve your business goals. Whether those goals are\nsimple (such as sending delivery notifications) or complex (such as booking a\nflight), agents use rich cards, media, and suggestions to guide users through\nfluid conversations that satisfy user and agent needs.\n\nHow it works\n------------\n\nThe flow of conversation between your agent and a user is similar to a\nconversation between two people, with each party taking turns speaking,\nlistening, and responding to the other.\n\nYour RBM agent initiates conversations with users. Users can't start\nconversations with your agent, but once the agent starts a conversation, the\nuser can reply at any time.\n\nYour agents sends the first message when it receives an external trigger that\nyou configure. A trigger can be anything and depends on your agent's use case:\n\n- A package ships\n- It's time to send daily lunchtime sandwich deals\n- A user contacts customer support in chat\n\nWhen your agent receives the trigger, the agent [sends a message](/business-communications/rcs-business-messaging/guides/build/messages/send)\nto the user's device with the RCS Business Messaging API. Your agent sends all\nmessages, events, and other requests to the user through the RBM API as HTTP\nrequests with JSON payloads. The user receives the message in the Messages app\non their device.\n\nIf the device doesn't support RCS, the RBM platform returns a `404` error, and\nthe agent should fall back to another technology, such as SMS.\n\nWhen the user responds to the message or triggers an\n[event](/business-communications/rcs-business-messaging/guides/build/events),\nGoogle's RBM service sends the response to your configured\n[webhook](/business-communications/rcs-business-messaging/guides/integrate/webhooks),\nwhich passes the information back to your agent. The webhook sends\nall user messages, events, and other requests to your agent as JSON.\n\nAfter your agent [receives the message](/business-communications/rcs-business-messaging/guides/build/messages/receive),\nit decodes the JSON and parses the response. Using internal logic, or relying on\na natural language understanding (NLU) module like\n[Dialogflow](https://dialogflow.com/), your agent decides on a response to the\nuser's message and sends the response to the user's device through the RBM API.\n\nThe conversation continues between your agent and the user until it reaches an\nintended conclusion or the user stops responding.\n\n### Example\n\nThe following example shows a simple scenario where a user asks for a weather\nupdate.\n\n1. Your agent receives a trigger from an external service indicating that a user requested a weather update.\n2. Your agent sends a message to the user acknowledging the user's request and asking for the user's location.\n3. In the Messages app, the user reads the message and responds with their address.\n4. Your agent processes the response, fetches weather information, creates a conversational message, and sends the information to the user. Additionally, your agent asks if the user also wants weather information for another location.\n5. The user reads the messages and thanks the agent.\n6. Your agent acknowledges that the user didn't request additional information and ends the conversation.\n\nEncryption\n----------\n\nRBM messages sent between users and agents are encrypted between RBM agents and\nGoogle servers and between Google servers and users' devices. Partners can't use\ntheir own encryption keys because Google needs to scan messages for malicious\ncontent to protect all users and businesses.\n\nFor more information about RBM data security, refer to\n[Data security for RCS Business Messaging](/business-communications/rcs-business-messaging/support/data-security).\n\nWhat's next?\n------------\n\nOnce you're comfortable with these concepts, consider what you want your\nagent to do and [build your first agent](/business-communications/rcs-business-messaging/guides/get-started/first-agent)."]]
