Best_Practices_of_VUI_Design.pdf

Voice technology is at its infant stage. And voice user interfaces are very different from graphical user interfaces. Hence developing voice applications after having an idea of the best practices makes it very easy to understand and develop.
It covers some of the best practices that should be kept in mind while designing a voice user interface.

Transcript

1. Nimesh Solanki @NimeshS17 Best Practices of Voice User Interface Design
2. “To think creatively, we must be able to look afresh at what we normally take for granted” - George Keller • The space where interactions between humans and machines occur • Goal: allow effective operation and control of the machine from the human end
3. Evolution of UIs Image Credits: https://chatbotsmagazine.com/what-is-a-conversational-ui-and-why-it-matters-de358507b9a2
4. • Command Line Interface • Graphical User Interface • Conversational User Interface ◦ Voice User Interface
5. Command Line Interface • Only way to interact with computers • Commands with a strict format (CLI)
6. Graphical User Interface • A later evolution of human-machine interface • became extremely popular during the 90s (GUI)
7. Conversational User Interface • privilege of interacting with the computer on human terms • Conversational UI takes two forms voice assistant that allows you to talk chatbots that allow you to type. (CUI)
8. Voice User Interface • Interact with a system through voice or speech commands. • Clearly state possible interaction options (VUI)
9. What is Conversation Design?
10. “To think creatively, we must be able to look afresh at what we normally take for granted” - George Keller • Conversation design is a design language based on human conversation. • The more an interface leverages human conversation, the less users have to be taught how to use it.
11. Chatbots • Chat Solutions involved a real agent on the other side • ask questions to chatbot without needing to browse for hours for the information we are looking for • Automatically transfers the customer to a human agent the automatic interaction fails.
12. Voice Bots • IVR (Interactive Voice Response Systems) • Just say it and it happens!
13. How Not to Build Your Next Chat and Voice Bots
14. What your bot shouldn't be • Don't imitate your web functionality!
15. not too little and not too much • The "too little" scenario, where a bot offers very little and therefore has no value for the end-user • The "too much" scenario, where a bot sets high hopes for what it can do, but then fails to meet those expectations
17. Don't just build and forget • Learn from the client experience. • Track where your solution fails. and measure whether it offers any value at all to your clients. • It is a continuous evolution. • The greatest challenge of conversational UI is in many cases less the technical constraints and more the linguistic ones ◦ Example: What is AQ ? => What is a queue?
18. Find the direct path to initial success • Help your users to ask the right questions.
19. Find the direct path to initial success • Dynamic Welcome Messages.
20. const welcome = (conv) => { // This function is used to handle the welcome intent // In Dialogflow, the Default Welcome Intent ('input.welcome' action) // In Actions SDK, the 'actions.intent.MAIN' intent if(conv.user.last.seen){ conv.ask(“Hey you're back…”); } else{ conv.ask(“Welcome to the 7th Edition of DevFest Ahmedabad”); } }
21. Find the direct path to initial success • Contextual Discovery
22. Think like a search engine, not a command line. • In case of an error, try to make provide the closest relevant response
23. Your Bot can be a Better Human • Give it the personality that best characterizes your business, through visual, semantic, and even voice methods
24. Q&A
25. Nimesh Solanki @NimeshS17 Thank you!