我们将于 2024 年 7 月 31 日逐步淘汰 Google Business Messages。点击
此处了解详情。
消息的生命周期
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
用户可以向代理发送信息,代理也可以向用户发送信息,但并不止如此。每条信息都可能涉及多方:
- 用户通过 Google 搜索、Google 地图以及品牌管理的链接和网站中的入口点发起与代理的对话。用户必须登录 Google 帐号,但系统只会与合作伙伴分享用户的名称。用户信息通过 TLS 进行加密。
Business Messages 充当用户与合作伙伴之间的层,以保护用户隐私。这一层通过解密并重新加密每条入站和出站信息以及将用户的 Google 帐号与对话 ID 对应起来,确保用户的 Google 帐号信息不会与合作伙伴或人工客服分享。
Google 会存储经过加密的信息,以确保能在用户的多部设备之间传递和同步。这些存储的信息无法与任何第三方分享。访问权限只能通过用户的 Google ID 获得。
代理是品牌的代表,由合作伙伴创建和管理。
合作伙伴代表品牌管理代理。合作伙伴通过指定的网络钩子接收入站信息,将入站信息传送至自动化功能或人工客服以撰写回复,并将出站信息发送到 Business Messages API。
自动化功能处理用户信息,无需人工干预。
人工客服处理需要人工干预的用户信息。
各方都会在对话中发送和接收信息。端到端信息传递流程始于用户向代理发送信息,止于用户收到代理的回复。

- 用户发起对话并向 Business Messages 代理发送信息。
- Business Messages 为对话分配一个 ID。对话 ID 是永久性的,并且对用户和代理而言是唯一的。如果同一用户联系了其他代理,该对话将具有不同的对话 ID。
- Business Messages 将经过加密的信息发送至合作伙伴的网络钩子。该信息包含唯一的对话 ID、代理 ID、信息 ID 以及有关对话起源的上下文信息。
- 合作伙伴接收该信息,并将该信息传送至自动化功能或人工客服。
- 自动化功能针对用户信息自动创建回复,或者有权访问对话的人工客服查看用户信息,并创建相应的回复。
- 合作伙伴将回复发送至 Business Messages API,接收者为对话 ID。
- Business Messages 解密并重新加密信息,将对话 ID 与用户的 Google 帐号对应起来,然后将该信息发送给相应的用户。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2024-12-21。
[null,null,["最后更新时间 (UTC):2024-12-21。"],[[["\u003cp\u003eBusiness Messages enables conversations between users and agents (representing brands) while protecting user privacy.\u003c/p\u003e\n"],["\u003cp\u003eGoogle acts as an intermediary, ensuring secure message transmission and user anonymity by encrypting messages and using conversation IDs.\u003c/p\u003e\n"],["\u003cp\u003ePartners manage agents and handle message routing to automation or live agents for response generation.\u003c/p\u003e\n"],["\u003cp\u003eThe messaging flow involves users initiating conversations, Business Messages facilitating secure delivery, and partners orchestrating responses via automation or live agents.\u003c/p\u003e\n"]]],[],null,["# Life of a message\n\nUsers can send messages to agents, and agents can send messages to users, but\nthere's more to it than that. For each message, there can be many parties\ninvolved:\n\n- **The user** begins a conversation with an agent through [entry\n points](/business-communications/business-messages/guides/concepts/entry-point) in Search, Maps, and brand-managed links and websites. Users must be signed in to a Google account, but only the user's name is shared with the partner. User messages are encrypted with TLS.\n- **Business Messages** acts as a layer between the user and the partner to\n protect user privacy. This layer ensures the user's Google account\n information isn't shared with the partner or live agents by decrypting and\n re-encrypting each inbound and outbound message and mapping the user's\n Google account to a conversation ID.\n\n Google stores encrypted messages to ensure delivery and synchronization\n between a user's devices. These stored messages can't be shared with any\n third party. Access is only available with the user's Google ID.\n- **The agent** is a representation of a brand, as\n [created](/business-communications/business-messages/guides/agent-lifecycle)\n and managed by a partner.\n\n- **The partner** manages the agent on behalf of a brand. Partners receive\n inbound messages at a [specified\n webhook](/business-communications/business-messages/guides/quickstarts/echo-agent#webhook),\n route inbound messages to automation or live agents to compose responses,\n and send outbound messages to the Business Messages API.\n\n- **Automation** handles user messages without human engagement.\n\n- **Live agents** handle user messages that require human engagement.\n\nEach party plays a part in sending and receiving messages within a conversation.\nAn end-to-end messaging flow starts with a user messaging an agent and ends\nwith the user receiving a response from the agent.\n\n1. A user starts a conversation and sends a message to a Business Messages agent.\n2. Business Messages assigns the conversation an ID. Conversation IDs are persistent and unique to the user and the agent. If the same user contacted a different agent, that conversation would have a different conversation ID.\n3. Business Messages sends the encrypted message to the partner's webhook. The message contains the unique conversation ID, agent ID, message ID, and context information for where the conversation originated.\n4. The partner [receives the\n message](/business-communications/business-messages/guides/how-to/message/receive) and routes the message to automation or to a live agent.\n5. Automation automatically creates a response to the user message, or a live agent who has access to the conversation sees the user message and creates a response accordingly.\n6. The partner [sends the\n response](/business-communications/business-messages/guides/how-to/message/send) to the Business Messages API with the conversation ID as the recipient.\n7. Business Messages decrypts and re-encrypts messages, maps the conversation ID with the user's Google account, and sends the message to the user."]]