EasyManua.ls Logo

SoftBank Pepper - Page 64

SoftBank Pepper
87 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
www.SoftBankRobotics.com 64
HOW ?
EXAMPLE
WHY?
Pepper has to propose a fallback
if an expected action from the user
is still missing
Fallbacks help users return to a more comfortable flow of
interaction. They avoid failed interactions and ones that come
to a dead end.
Attach a timer to every expected user action. After a few
seconds without user action, Pepper should repeat the
demand. After one or two fallbacks, Pepper should oer to
help or quit the application.
If the user doesn't answer a question, repeat the question
once or twice, then ask if someone is still there. If there's no
reply, Pepper should close the application.
05 | Pepper is easy to use

Other manuals for SoftBank Pepper

Related product manuals