[null,null,["最后更新时间 (UTC):2024-12-21。"],[[["\u003cp\u003eIn conversation design, the happy path is the optimal route a user takes to achieve their goal with minimal effort.\u003c/p\u003e\n"],["\u003cp\u003eGuide users with clear and concise instructions, rich features like suggestions and cards, and by setting expectations for the task's length.\u003c/p\u003e\n"],["\u003cp\u003eProvide fallback options for unsupported inputs or older devices to ensure a smooth experience for all users.\u003c/p\u003e\n"],["\u003cp\u003eKeep the conversation flowing by offering prescriptive guidance and always providing a clear next step, even upon task completion.\u003c/p\u003e\n"],["\u003cp\u003eUse rich features like suggested replies, suggested actions, rich cards, and carousels to enhance user interaction and keep them engaged.\u003c/p\u003e\n"]]],[],null,["# Guide the interaction\n\nIn conversation design, the **happy path** is the optimal route from the start\nto the end of the user journey. Define the happy path for your use case. This is\nthe shortest sequence of steps that users can follow directly to their goal,\nwith the least effort on their part.\n\nProceed with simple steps\n-------------------------\n\nA good conversation flows as a quick back-and-forth read. Each message should\nprovide a small chunk of information and prompt the user to take the next step.\nWhen a task involves multiple steps, set the user's expectations for how much\ninformation they will need to move through.\n\n- \"Let's get started. I have three questions for you.\"\n- \"We can get that done in three easy steps.\"\n- \"Just three steps to go.\"\n\nThe more steps between the user and their end goal, the more likely they are to\ndrop off. However, setting expectations helps people stay engaged.\n\nBe prescriptive\n---------------\n\nThe more direction you give, the smoother the journey will be. Avoid vague or\nopen-ended questions. When asking the user for information, make it clear what\nyou're looking for.\n\n- \"I've got your name and email from your account. All I need is your phone number.\"\n- \"When is your preferred move-in date? You can give me a day, a time, or both.\"\n\nDefine the options with rich features\n-------------------------------------\n\nRich features, like suggestions and rich cards, make the conversation more\ndynamic. They also serve as anchor points. Suggestions and cards keep users on the\nhappy path by providing options the agent supports.\n| **Note:** Even if your design relies on suggestions, users can type freely. Create a [fallback strategy](/business-communications/business-messages/guides/how-to/design/fallback#prepare_fallback_responses) for any text inputs the agent is not designed to handle.\n\n### Suggestions\n\n[Suggested replies](/business-communications/business-messages/guides/how-to/message/send#suggested_replies)\nand [suggested actions](/business-communications/business-messages/guides/how-to/message/send#suggested_actions)\nhelp users move quickly through the conversation. By defining the options,\nsuggestions make it easy to take the next step.\n\nA message can have a maximum of 13 suggestions. If this isn't enough, display up\nto 12 suggestions in one message and add a suggested reply to show more (for\nexample, \"Show other options\"). When the user taps this suggested reply, send a\nmessage with the other suggestions.\n\nOnce the user taps a suggestion, the untapped suggestions disappear. If you want\nthem to remain in the conversation, embed the suggestions in rich cards instead\nof text messages.\n\n### Rich cards and carousels\n\nUse [rich cards](/business-communications/business-messages/guides/how-to/message/send#rich-cards)\nto combine visual media, text, and suggestions. Don't use images or video alone.\n\nEach standalone rich card should include text or suggestions to keep the\nconversation going.\n\nA [carousel](/business-communications/business-messages/guides/how-to/message/send#rich-card-carousels)\nof cards can inspire users with a range of products and allow them to compare\noptions. Frontload the carousel with the items you most want users to see; they\nmay not scroll to the end of the list. Use suggestions below a carousel to\nextend the journey or pivot to something else.\n\nA carousel can have a maximum of ten rich cards. If this isn't enough, display\nup to ten cards in one carousel and include a suggested reply to see more\n(for example, \"Show me more plans\"). When the user taps this suggestion, send\nthem another carousel with the remaining cards.\n\n### Fallback for rich features\n\nProvide [fallback text](/business-communications/business-messages/guides/how-to/message/send#fallback_strategy)\nfor rich features that don't display on older devices.\n\nState the suggestion options within the message so users know how to move\nforward.\n\nFor rich cards and carousels, include the rich card title and URL within the\nmessage.\n\nAlways offer a next step\n------------------------\n\nSometimes users follow a path that doesn't meet their needs. To keep them from\ngetting stuck, offer the option to go back. Periodically surface suggested\nreplies that return the user to key decision points. For example,\n\n- \"Choose a different date\"\n- \"View other models\"\n- \"Go back to menu\"\n\nMake sure every conversation offers a next step and never dead ends. This\napplies to [fallbacks](/business-communications/business-messages/guides/how-to/design/fallback#prepare_fallback_responses)\nas well as completed tasks. When a user reaches the end of a journey, display\nthe conversation starters again, so the user can start a new task."]]