Amazon Now Allows Customer Contact Through Alexa Skills
Amazon today announced in a blog post and through Alexa Skills Kit documentation the availability of the Customer Profile API. This new feature enables Alexa skill publishers to learn a user’s name to personalize the interaction or their email and mobile number to provide interactivity through messaging. Before today, Alexa skills provided no method for linking to Amazon user profile information. User identity and contact details could only be accessed through account linking, which required an online interaction flow through another surface such as a mobile app or webpage. The account linking approach introduced a lot of user experience “friction” and have typically been avoided by developers whenever possible. Alexa skills can now request user permission to use contact information as part of the skill experience. Information that can be made available includes:
- Full Name
- Given Name (First Name)
- Email Address
- Mobile Number
So far, developers are enthusiastic about the new feature. Ami Berger, CTO and co-founder of Voiceter Pro LLC, emphasized how important this development will be while commenting:
I think it is a huge step forward for skill builders. It will greatly reduce the need to create account linking. Obviously account linking will still be necessary as a fall back, but it will be really nice to be able to streamline getting email addresses.
Restrictions of Use
There are restrictions in terms of what can be accessed and how it can be used. This is not an attempt by Amazon to enable skill developers to spam Alexa users. Amazon policy guidelines lay out several requirements of using the Customer Profile API, including:
- You may not associate an Amazon customer and their profile information with other customer account information the developer maintains outside of Alexa
- The skill must request the data from the Alexa Customer Profile API whenever it is needed and may not call it from a stored location
- The Customer Profile API may not be used in any skill designed for use by children
The restriction for use with children-oriented Alexa skills is not surprising. However, the restriction from matching an Amazon contact profile with an existing customer profile maintained by the Alexa skill owner is an important limitation as is the requirement to call the information anew each time it is needed. Amazon is permitting Alexa to facilitate user contact through means other than the voice assistant service, but it is not granting access to actually know your users’ identities in real life and add that your your CRM database.
So, this feature provides excellent one-off functionality with minimal friction, but it is not intended to introduce an opportunity to deepen a customer relationship outside of Alexa interactions. This limitation will mean that many Alexa skill developers will still want to implement account linking when possible. The open question is whether the presence of the Customer Profile API will lead Amazon to be more restrictive on account linking in skill certification under the rationale that the developer has a tool other than account linking to achieve the functionality goal.
Use Cases to Drive Re-Engagement and Voice Commerce
SnapTravel, KptnCook and Thalia Buch-Tipps have already implemented the feature using SMS or email messaging to users. KptnCook and Thalia Buch-Tipps are delivering recipes and book recommendations via email. This is an interesting use case and a new method to drive Alexa skill re-engagement rates. The emails could stand on their own and simply allow the skill to provide an extended experience beyond Alexa. However, the feature could also be used to prompt skill usage and raise the incidence and frequency of repeat use. Think of it as potentially similar to how notifications are used to drive repeat engagement with mobile apps.
By contrast, SnapTravel is using the Customer Profile API to execute a transaction that cannot be completed on Alexa alone. Hussein Fazal, Co-Founder & CEO of SnapTravel, said, “Customers can begin their hotel booking journey over voice using Amazon Alexa, and receive a link on their phone over SMS to complete the booking.” This scenario reflects the removal of a voice commerce barrier for goods that cannot be purchased today through Amazon.com. It could mean that many more product sellers can complete sales transactions outside of Amazon.com which would be good for platform adoption. However, it is unclear whether Amazon will permit this type of use case to proceed through certification if it is perceived as competing against the ability of Amazon.com to capture the purchase. Travel is different because Amazon doesn’t sell these types of services.
Regardless of potential restrictions, there are many reasons to be optimistic about the benefits of the new feature. Mark Tucker, co-founder and chief architect of VoiceXP commented:
“This is a great addition to any skill developer’s toolbox. At VoiceXP, we are already implementing solutions for clients that send an SMS text message to their mobile phone. Currently, we ask the user for the 10-digit phone number. Now we have the ability to use the API and ask ‘Would you like me to text that to you at 555-867-5309?’ without prompting for the phone number. If they answer ‘No’, we can ask if there is an alternate phone number and then prompt them for that. The Customer Profile API is a feature that is immediately useful and makes for a better voice experience.”
Developers Point Out Limitations
A number of developers have pointed out limitations of the feature. It is not fully enabled by voice like a similar feature is for Google Assistant. You must instead push a card to the user in the Alexa app that requests the permission and the user must go into the app and accept. The documentation also says this should be done when a user first enables a skill which seems like a barrier to onboarding and initial skill trial. If the user does not accept at that time, there is another opportunity for them to accept when a transaction arises that requires the contact information.
The problem is that the approach presents a clear barrier inside of the transaction flow which will lead to abandonment rates. A lower friction approach would be to enable this when needed by voice. Once permission is accepted by voice, it could be configured to not require subsequent approval but allow users to revoke the permission. Or, it could simply be a one-time authorization. The lower friction makes this reasonable. A card-based approach that takes someone from a smart speaker surface to a mobile app is not an elegant solution, nor is it an elegant user experience. Customer Profile API is a nice feature to have, but it remains to be seen whether it will be effective given the friction associated with the current implementation. I suspect this is a phase one release and Amazon will enable voice permission in the future, but until then developer adoption may be muted.
Filling Out the Voice Assistant Feature Set
You can read more about the Customer Profile API here. It reflects an important step for Amazon, particularly since Google Assistant has had similar capabilities for email contact for some time. However, the really interesting development here is not that you can present a call-to-action and then have a means for connecting with a user through a different digital channel. What is more important is that the Customer Profile API could be used to drive re-engagement, user retention and voice commerce in addition to facilitating new features with less friction for users.