Make Alexa check for intents *inside* the skill before searching for a native/keyword function
It's increasingly common and frustrating to have Alexa ignore intents provided by the skill and instead pivot to a native function / keyword function.
For example, in a cooking skill I've included various intents for calling up the list of recipes offered by the skill. But as soon as Alexa hears the word "recipe", she quits the skill and says, "Sure. I can search by dish name and ingredients. What would you like?"
Alexa obviously did not check my list of intents, because if she did she would've read the list of recipes in my skill to the user.
The same problem exists with any intent that includes the word "list". As soon as Alexa hears the word "list" she assumes the user wants to view their Alexa shopping list---even if there are custom intents in the skill to handle user requests with the word "list" in them.
By default Alexa should always check for a matching intent within the skill first, and only resort to native / keyword functions if she doesn't find a match within the skill.
Ken Reiss commented
Corey Cole commented
I definitely think Amazon needs to do more work on something like this. Some sort of heuristic should be used in finding which skill to invoke, like the most recently invoked skill? Also, when the audio player is playing in our skill, it should try to match an intent in the skill for which the audio player is playing.
David Castro commented
April, this is interesting, I've never seen this happen. Can you give me the name of your skill and the steps you are following to reproduce it?