This document discusses building customized apps for Google Assistant using Dialogflow. It provides an overview of the Google Assistant workflow and how Dialogflow is used to build agents with intents, contexts and fulfillment. It also covers basics of conversation design, building blocks for conversations and considerations for real-life user conditions. The document includes an agenda, background on Google Assistant, statistics, diagrams of the workflow and integrations available through Dialogflow. It demonstrates an example using Dialogflow and references additional resources.

1. APPS ON GOOGLE
ASSISTANT USING
ACTIONS
GAURAV BHATNAGAR

2. AGENDA
• Background
• Google AssistantWorkflow
• How Assistant provides customized response.
• Dialogflow and all its main components
• Demo of an example
• Basics of Conversation design
• GUI vsVUI

3. BACKGROUND
• Google Assistant is currently available on more than 400 million devices around the
world.
• It is available in phones(iOS or android), tablets, cars, Chromebook & Home Devices.

4. GOOGLE ASSISTANT STATS

5. GOOGLE ASSISTANT WORKFLOW
Source : https://dialogflow.com/docs/agents

6. DIFFERENT APPROACHES FOR CUSTOMIZED
ASSISTANT APPS

7. GOOGLE ASSISTANT WORKFLOW (USING
DIALOGFLOW)
Source : https://dialogflow.com/docs/agents

8. DIALOGFLOW
• Agents
Agents are NLU Modules built with the 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…..

9. INTEGRATIONS PROVIDED BY DIALOGFLOW
Source : https://dialogflow.com/docs/integrations

10. SHOWING AN EXAMPLE
DEMO

11. CONVERSATION DESIGN
• It is basically a design language based 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.

12. BUILDING BLOCKS FOR CONVERSATION
• Expect users to give more 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.

14. ALWAYS KEEPING REAL LIFE USER CONDITIONS IN
MIND
Interrupted Cut 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”.

15. REFERENCES
• Actions on Google Developers : https://developers.google.com/actions.
• https://developers.google.com/actions/design/
• https://dialogflow.com
• https://caster.io/courses/google-assistant-app-with-zero-code