Allow voice conversation to continue after a user touches the screen
On devices with screens when you use the List template we observe the following: Once a list is displayed, it puts the Echo in a state where you can’t continue voice commands. For example, if a user invokes an intent that brings up a menu of options on the screen that is displayed with the List template and the user touches the screen to scroll, the voice interaction with the user comes to an end. They have to say “Alexa” first to return to the voice conversation. This should not be the case - please remove the need to say "Alexa", it is not conversational, is not intuitive, and makes no sense when you are inside a skill.
8
votes
Dana Young
shared this idea