created a skill that got certified and waiting to market it via our channels but the skill cannot be invoked by saying, "Alexa, open Skill Name Here..." as it pulls up a skill that was last updated a year+ ago. i understand that to me this must be an invocation utterance conflict and it is routing to the similar named skill (no way of really knowing as we as 3P devs dont have an invocation db or list to review).
so instead i am being told that the user must 'enable' it first and then it will be active. then they will be able to say the normal words. the problem is that support is not being clear that it is an invocation utternace problem they just keep insisting on the skill having to be 'enabled' first.
i feel i should alter the invocation until i get one that doesn't carry a conflict when uttered so i can actually get a clean and 'normal' invocation route of "Alexa, open Skill name here..." and it works. 4 words and it works!
Any thoughts, input or feedback would be greatly appreciated as i am literally at wits end. going around in circles with alexa support (which is usally awesome as heck!). i can't market this skill by saying "Hey first, you need to say Enabled Skill Name Here" and then after that, you can say "Alexa, open Skill Name Here..." (that doesn't look to good in an email signature etc...) but don't worry there is no issue here because almost all other skills are opened and invoked a lot eaiser and cleaner...
thanks in advance for your time,