[null,null,["最后更新时间 (UTC):2024-12-21。"],[[["\u003cp\u003eAutomation and live agents work best together in conversational commerce, with automation handling initial queries and live agents addressing complex issues or Google-owned entry point interactions.\u003c/p\u003e\n"],["\u003cp\u003eImplement fallback responses to gracefully handle situations where automation doesn't recognize user input, offering options like rephrasing or connecting to a live agent.\u003c/p\u003e\n"],["\u003cp\u003eHuman handoff is essential in specific scenarios, such as user requests, repeated questions, or consecutive failed intent detections, ensuring a smooth transition to live support.\u003c/p\u003e\n"],["\u003cp\u003eDuring handoff, clearly communicate the expected response time and consider offering alternative contact methods if necessary, while acknowledging the asynchronous nature of Business Messages.\u003c/p\u003e\n"],["\u003cp\u003eConversations initiated from brand-managed entry points do not necessitate human backup, though it can enhance the user experience.\u003c/p\u003e\n"]]],[],null,["# Use both automation and live agents\n\nAutomation and live agents are the dream team of conversational commerce. Automation can be your brand's first line of support by providing immediate customer service at scale. Numerous queries can be handled by automation, which enables live agents to be more efficient.\n\nFor Google-owned entry points, a human back-up is a must. Live agents should step in to handle any issues that automation isn't designed for or to help users complete a particularly complex task.\n| **Note:** Conversations started from [brand-managed entry points](/business-communications/business-messages/guides/concepts/entry-point#brand) do not require human backup. But it's helpful.\n\nPrepare fallback responses\n--------------------------\n\nUsers can type freely, and they may say something the agent doesn't\nrecognize or support. Don't let this be the end of the conversation. Plan an\nappropriate fallback response.\n\nYour fallback can be reactive or proactive. Both approaches allow you to\n[fail gracefully](/business-communications/business-messages/guides/how-to/design/language#fail_gracefully).\n\n- A reactive fallback is useful when the user types something the agent doesn't recognize. This approach gives the agent one more chance to detect the user's intent.\n- A proactive fallback is useful when the user asks for something that automation isn't designed for. This approach relies on live agents as the best support option and connects the user directly.\n\n### Reactive fallback\n\nWhen the user types a message that strays from the [happy path](/business-communications/business-messages/guides/how-to/design/happy-path),\nyou can try to get them back on track. If a typed message doesn't trigger a\nknown response, do the following:\n\n- After the first missed intent, ask the user to rephrase their question, and\n suggest some things they can ask about. Provide suggested replies or\n actions.\n\n \"Can you rephrase that? You can ask me about store hours, order status, or\n pickup and delivery.\"\n- After the second missed intent, acknowledge the error and\n [connect the user to a live agent](/business-communications/business-messages/guides/how-to/message/conversations/bot-live-agent-handoff).\n Include an FAQ suggestion as an additional fallback.\n\n \"Sorry, I don't understand. Would you like to chat with a live agent?\"\n\n### Proactive fallback\n\nBefore the agent has a chance to fail, you can shift to human support. If a\ntyped message doesn't trigger a known response, connect the user to a live agent\nright away. Include an FAQ suggestion as an additional fallback.\n\nHere are some examples of proactive responses:\n\n- \"Do you want me to connect you with our product specialist?\"\n- \"That's a good question for our tech expert. Let me transfer you now.\"\n- \"I'm still learning, but our customer care team can help you.\n\n| **Note:** You can display a [Dial action suggestion](/business-communications/business-messages/guides/how-to/message/send#dial_action), but this should be a last resort. The best conversational experiences satisfy the user's needs without switching to a different medium.\n\nHand off at the right time\n--------------------------\n\nA [human handoff](/business-communications/business-messages/guides/how-to/message/conversations/bot-live-agent-handoff)\nis needed in the following circumstances:\n\n- The user types a message requesting a person.\n- The user taps a live agent request suggestion.\n- The user repeats a question, indicating they didn't get the answer they needed.\n- The agent detects the wrong intent twice in a row.\n- The agent fails to detect the user's intent twice in a row.\n\nTransition smoothly\n-------------------\n\nBuild out various responses leading to handoff. For more options, see the guides\non [acknowledging the user](/business-communications/business-messages/guides/how-to/design/language#acknowledge_the_user)\nand [failing gracefully](/business-communications/business-messages/guides/how-to/design/language#fail_gracefully).\nWhen it's clear the user needs to speak to a human, transfer them as soon as\npossible.\n\nHere are a couple of ways to ease the transition:\n\nWhen a live agent joins the conversation,\n[update the representative display name and avatar](/business-communications/business-messages/guides/how-to/message/send#representatives)\nso the user knows they're interacting with a person.\n\nState the response time\n-----------------------\n\nIn Business Messages, conversations are asynchronous. That means a response is\nnot needed immediately, but users tend to expect a prompt reply. State the\ntimeframe in which the live agent is expected to respond. Remember to\n[set messaging availability](/business-communications/business-messages/guides/how-to/agents/availability)\nfor the agent so users know if humans aren't available.\n\n- \"Thanks for your response. I've passed this query to one of our live agents. They'll get back to you within five minutes. You'll see a notification when they reply.\"\n- \"I'll connect you with one of our experts. It will be 3 minutes before they join the conversation. We'll notify you then. Thank you 🙂\"\n- \"I'm happy to connect you with a live agent. It will be about 10 minutes.\"\n\nIf needed, offer alternative methods of contact. You can direct users to call a\nsupport number or visit a website when appropriate.\n\nUsers are likely to come and go from the conversation and may not reply\ninstantly. When they do re-engage, the conversation history is visible to them."]]