help of contexts, intent priorities, responsibilities, and fulfillment via webhook. • Intents They represent a mapping between what a user says and what action should be taken by your customized software. • Contexts They are designed for passing on information based on user’s preferences, geographic location. • Fulfillment This component connects your Dialogflow agent to your services, APIs and/or databases. It connects to webhooks via Actions on Google. • Entities, Actions, Parameters…..
on human conversation. • We are providing an experience and merely not just an application. • Creating a System and User persona. • Conversation Design should be built on cooperative principle. Conversations should always be designed to provide comfortable, frictionless and user centric experience. • Group devices by the components used in conversation : For e.g. Google Home/ Pixel.
information. • Try to always keep the dialog towards the use case you are trying to solve. • Try to always move the conversation forward. • Try to keep the conversation optimized for relevance and provide clarity in answers. • Try to understand the context and listen between the lines. • Follow-up conversations should have the context attached. • Keep the conversation going by taking turns and not try to monopolize.
off too soon No way out Accent Language understanding Self Correction Confused Side Speech Valid but not in grammar Didn’t Understand Background noise Ask a question back. Coughs Talked too long Too quiet Hesitate Know options by some other manner Stutter Start Too many choices Poor connection In Conversations, there are no “Errors”.