We're currently going through beta testing with our custom skill, and it's been less than friendly to our Invocation Name, "Apex Fusion". Depending on the voice and enunciation of our beta testers, we're either seeing near perfect recognition for some users, or closer to 50% recognition for others. I've been collecting video feedback where our invocation name is spoken, but Alexa acts as if she didn't hear the invocation name at all.
Here are some examples where the enunciation was clear, but Alexa still ignored our invocation name and either chose a different skill or didn't respond at all (All of our Intent requests respond with voice responses, so any "audio-only" or canned responses you hear in the videos are from the Alexa Services failing to recognize our invocation name):
In this video, our user's intent is first ignored with the canned "Hmm, I don't know that" and the second time the intent is mistaken for an audio player command:
In all of these examples, our sample phrases are formatted as such:
"turn on <AMAZON.SearchQuery>"
"turn off <AMAZON.SearchQuery>"
So I would expect ANY command which has the words "Apex Fusion" followed by "feed", "turn on", "turn off", or "restart" should match this custom skill. Are we missing something here? Will publishing our skill increase the odds of Alexa choosing our skill instead of thinking I said "LifX" every 5th command?