We spend time discovering, detailing and building UX design skills using Skill or Action templates, refining them into detailed conversion flows before developing.
Data and Analytics
Designing your voice app journey begins by having your users in mind as your focus. Always think of how your voice app will add value to your user whether it is a conversion voice app or it is just one of many touchpoints for your customers. Take into account why and where people use voice apps and its benefits and design it specifically for scenarios why people will most likely have a need to use voice apps. Leverage on the primary use of voice interfaces and its benefits such as, hands-free interaction, the speed of interaction and the ease of use whilst they are in their homes, their offices or in their cars with a common behaviour. This all has something in common, the user want faster results.
Utterance is defined by Amazon as "a structured text file that connects the intent to the likely spoken phrases and containing as many representative phrases as possible". Hence, making an "Utterance" simply as the questions that users asks Alexa. One of the many rookie mistakes is creating one utterance, and not making many variations of the question to anticipate the many variations that the end user would most likely use. Best practice is to create multiple utterances to account for every version of a phrase. An example would be if you build an Uber-like voice skill for a user to arrange for a ride using utterances, "Alexa, I need a ride", "Alexa, book me a ride", "Alexa, I need to schedule a ride" etc.
When designing voice interfaces, developers don’t have the convenience of having assistance from visual elements available for use in web and mobile interfaces to show a personality. The challenge is for the developer to make use of the device's personality to convey a new skill but consistent to its "tone of voice". This can best be proven when asking Alexa a question and it responds to a witty character, to even a borderline cheeky response. By creating a voice interface that can be consistent to Alexa's personality, the developer will be adding skills to make Alexa smarter and respond to a wider variety of user questions as oppose to changing the way it normally responds to users.
Linking your skill/action to your existing system will give a deeper integration with a user of your system. This would allow the user to order taxi’s, pizza’s, request updates to bank statements, deliveries etc, because they would be linked to their personal accounts form that service. This service uses a token that can be used to authenticate the user with the backend system.
We have partnered with VoiceLabs to integrate VoiceInsights:
VoiceInsights is the voice analytics product provided by VoiceLabs, free of charge.
VoiceInsights provides accurate, real-time data to developers about how consumers use their Amazon Alexa skills and Google Assistant Actions, as well as uncover actionable insights about how to improve the voice experience.
With this data, developers can identify issues and opportunities, create a more informed product roadmap, increase retention and grow their user base.
After you have your voice interface designed and built, the next phase will be to move on to the build-test-submit phase. Starfish helps in your development process by creating a beta tester of your app, monitor it and then refine before submitting to Amazon for final approval.
Lastly, refer to your skill "metrics" (users, sessions, utterances, intents) within your developer account for insights and feedbacks. This will give you insightful information about how people use and engage with your masterpiece!
At this point, you have built and tested your app and now ready for Amazon final approval. The process can be broken down in two phases. Initially, it will go through a bunch of standard scripts that tests your skill for common errors, such as how you handle good intents, bad intents and how you handle passing in a bad application ID. The second phase is when an Amazon employee looks at your app to determine if it meets their standards, terms and conditions, basically..if it your skill will generally be a good fit for Alexa. If you have followed the guidelines and best practices, then it shouldn't take you too long for a response. Note that each platform has detailed guidelines and tutorials to help anyone build and test skills including Alexa Skills Kit, Develop Actions for Google, and Cortana, which offers to reuse your custom Alexa skill code.
While you may get lucky, you should allow yourself seven days from submission to final Amazon approval of your Alexa Skill. If you followed Amazon’s best practices - and make sure you handle intents well, the process should be pretty smooth.
SKILLS DEVELOPMENT STEPS
We can build your skill in five easy steps..
Speech prompts/possible responses/success conditions/Error conditions/Data source
Design and Develop
Our skilled design team get to work building your new voice skill
Marketing and Legal
You work with our marketing experts on logo design, policies
Apply for skill certifications
Once tested we apply for the skill certifications on your selected platforms
It's launch day
We made it and your skill is now live and you have happy customers. Enjoy!
Speak to us today!!
To see how we can design and develop that perfect for you.