Getting started>Conversation design>Best Practices>Formatting
I think the formatting might make following the content harder.
What about something like
below? The page here doesn't allow me to align things properly but the ide is there. I also added a screenshot of the current formatting.
Design natural, intuitive conversations
- Understand and implement the rules of Turn-taking, Reciprocity, and the Cooperative Principle.
Note: Most conversational use cases require that your bot assumes the onus of progressing the conversation, rather than the user. This is particularly important when leveraging generative AI.
- In general, a conversational copy should be brief, and low cognitive load.
- Use progressive disclosure. Provide “just enough” information for the conversational turn.
- Re-adapt long website FAQ copy for conversational interfaces.
- Be mindful of channel-specific actions, like “click” or “tap.” Replace with “choose” or “select.”
Note: For voicebots, follow the “rule of 3” when listing choices, and end your dialog turns with a direct question or call to action. Voice commands should be simple and intuitive.
- Determine if you will use NLU, Generative AI, or both to power your conversational AI’s understanding.
- Plan for how you will handle small talk and other conversational situations and commands.
Small talk:
- Hi, hello
- Thank you, thanks
- Are you a human?
- Can you repeat that? Come again?
- Go back, main menu, start over
- End, Close, Stop
- Agent, I want to speak to a human
- Hold on, wait
Situations:
- Are there any highly sensitive topics you will auto-escalate to a human immediately?
- How will you handle repetitive abusive sentiment or pranksters?
- Inactivity / Abandonment
- Be on the lookout for any potential looping that could occur in your conversation design, and remove it.
- Check that error messages are written in a helpful manner, enabling users to progress and get back on track.
Comments
-
Thanks @owilliams - I've made an update to this one. There are some formatting quirks i'm learning about. @kprobeck this might be something to keep in mind for the "style guide" article we discussed previously cc @Sue @blamm
0