We have shipped a number of new features recently, and wanted to share ways customers are using VoiceInsights to evolve their applications.

Two critical questions we hear are:

  1. Where are consumers getting confused in my app/what is not working?
  2. What should I fix first?

By using both the Voice Pathing dashboard and Speech Finder dashboard, you can answer these questions.

3 Steps to Improve your App:

  1. Use Path Finder to Find Issues by Intents
  2. Find out how you typically respond to this error case, i.e. what language do you use?
  3. Use the Intent and unique phrase to search Speech Finder, and find most common issues

 

1. Use Speech Finder to Find Issues by Intents

Navigate to the Pathing screen and review your Paths. Do any look problematic?

In this example (my sample application), a user Searches for a Recipe but does not Pick one, and instead invokes the Stop Intent.

VoiceLabs Voice Pathing

Select this path, then scroll down to the Sessions tab below the Paths and look at the user sessions?

What is going on?

From reviewing a few sessions, it is clear that users are looking for recipes that the application does not support:

Example Session #1:

cheese burger salad

Example Session #2:

pizza dough

 

2. Find out how you typically respond to this error case, i.e. what language do you use?

In this case, my app responds with “I’m sorry, I’m not finding any recipes for the dish you requested.”

What is unique in this response that I can search with?

I actually have a few cases where I say “I’m sorry,” but I only say “not finding” in this error case.

 

3. Use the Intent and unique phrase to search Speech Finder, and find most common issues

From the previous two steps I know:

  1. The Intent where I am having an issue: SearchRecipes
  2. The unique phrase I can use to search: “not finding”

I now navigate to Speech Finder and use these two things to create my to-do list:

Speech Finder Header

In looking at the results, it looks like I forgot to support salad:

Speech Finder Body

From this ranked list, I see that I should fix “taco salad” first. “pizza dough” is there, but it is not in the top three. (it is #8 in this example, hence I am not prioritizing the fix)

By executing these searches every few weeks, you can keep track of what user speech is causing issues, and prioritize app updates.

We encourage everyone to give this a try, and share learnings and feedback on the Slack channel!

To recap:

  1. Use Path Finder to Find Issues by Intents
  2. Find out how you typically respond to this error case, i.e. what language do you use?
  3. Use the Intent and unique phrase to search Speech Finder for most common issues.