New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle requests for "help" #16

martincostello opened this Issue Feb 12, 2017 · 1 comment


None yet
1 participant
Copy link

martincostello commented Feb 12, 2017

When users ask for “help” within the skill, it must return a prompt which instructs users how to navigate the skill’s core functionality. Additionally, the help prompt must end with a question for users and leave the session open to receive a response. Please see test case 4.12 from our Submission Checklist for guidance on the help intent.
User: "Alexa, open london travel"
Skill: "Welcome to London Travel. You can ask me about disruption or for the status of any tube line, London Overground or the D.L.R.."
User: "help"
Skill: "{plays disruption intent}"

@martincostello martincostello self-assigned this Feb 12, 2017

@martincostello martincostello added this to the 1.0.2 milestone Feb 12, 2017

martincostello added a commit that referenced this issue Feb 12, 2017

Add intents for "help", "stop" and "cancel"
Add intent to handle "stop" and "cancel" for #17.
Add intent to handle "help" with placeholder text for #16.

This comment has been minimized.

Copy link
Owner Author

martincostello commented Feb 12, 2017

The help response:

  • Provides instructions to help the user navigate the skill’s core functionality.
  • Is more informative than the prompt users hear when launching the skill with no intent. For example, the help prompt could explain more about what the skill does or inform users how to exit the skill.
  • Educates users on what the skill can do, as opposed to what they need to say in order for the skill to function.
  • Ends with a question prompting the user to complete their request.
  • Leaves the session open to get a response from the user.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment