new_releases 更新:查看
版本说明,了解新功能和产品动态。
RCS Business Messaging 的运作方式
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
RCS Business Messaging (RBM) 代理通过信息、
事件和请求,从而实现业务目标这些目标
简单(例如发送送货通知)或复杂(例如预订
航班),代理会使用富媒体、媒体和建议来引导用户
满足用户和代理需求的流畅对话。
工作原理
代理与用户之间的对话流类似于
两个人轮流讲话,
倾听和响应彼此的差异
RBM 代理会发起与用户对话。用户无法启动
但当代理发起对话后,
用户可以随时回复
当代理收到外部触发器时,会发送第一条消息,
配置。触发器可以是任何内容,具体取决于代理的用例:
- 包裹发货
- 是时候发送每日午餐三明治特惠了
- 用户在聊天中与客户支持团队联系

当您的代理收到触发器时,代理会发送消息
通过 RCS Business Messaging API 向用户设备发送消息。您的代理会发送
通过 RBM API 以 HTTP 格式向用户发出消息、事件和其他请求
包含 JSON 载荷的请求。用户在“信息”应用中收到信息
。
如果设备不支持 RCS,RBM 平台会返回 404
错误,并且
应改用其他技术,例如短信。
当用户响应消息或触发
event、
Google 的 RBM 服务会将响应发送到您配置的
webhook、
后者会将信息传回您的代理。Webhook 会发送
以 JSON 格式向代理发送所有用户消息、事件和其他请求。
在客服人员收到消息后,
它会解码 JSON 并解析响应。使用内部逻辑,或依赖于
自然语言理解 (NLU) 模块,
Dialogflow 后,您的代理将决定如何响应
用户的消息,并通过 RBM API 将响应发送到用户的设备。
代理和用户之间的对话会继续进行,直到达到
或用户停止响应。
示例
以下示例显示了一个简单的场景,当用户询问天气信息时
更新。
- 您的代理从外部服务收到一个触发器,指明
用户请求获取最新天气信息。
- 代理向用户发送消息,确认用户的请求,并
请求用户的位置。
- 在“信息”应用中,用户阅读该消息并使用自己的
地址。
- 代理处理响应、获取天气信息、创建
对话消息,并将信息发送给用户。此外,
代理会询问用户是否也想获取另一个
位置。
- 用户阅读消息并感谢代理。
- 代理确认用户没有请求更多信息
并结束对话。
加密
用户和代理之间发送的 RBM 消息会在 RBM 代理和
Google 服务器之间以及 Google 服务器与用户之间设备。合作伙伴不能使用
自己的加密密钥,因为 Google 需要对邮件进行
以保护所有用户和企业。
如需详细了解 RBM 数据安全,请参阅
RCS Business Messaging 的数据安全。
后续操作
熟悉这些概念后,请考虑您希望
构建您的第一个代理。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2024-09-02。
[null,null,["最后更新时间 (UTC):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)."]]