Skip to content

Alexa Skills - Developer Voice And Vote

Welcome to the Alexa Skills UserVoice site!

This site enables Alexa Skill Developers to request and vote on features you'd like to see in the developer toolset and services for Alexa.

Please bear in mind that this site is for Alexa skill builders, not Alexa users. Additionally, we cannot guarantee each feature request will be implemented but our team reviews each request and sends to the appropriate product teams.
For more information about using UserVoice, please see our blog post here: [Vote on developer features you would like to see at Alexa Skills Kit User Voice]

-Alexa Skills team

Alexa Skills - Developer Voice And Vote

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

132 results found

  1. I have a custom alexa skill for checking road conditions from SDX. We want to send notifications to users. Could you please help?

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I recently spent two days trying to determine why I wasn't able to use the "Update live skill" button for changes to my skill that were clearly eligible for live updates. Ultimately I was able to find the change that was blocking the live update functionality, but it was an extremely frustrating experience, since the Alexa Developer Console provides no insight into what changes are making a skill ineligible for live updates.

    It would be nice to have a way to determine what changes are making a skill not eligible for the live update workflow so that skill developers can…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Both the Alexa dev console and the ASK Lambda console time out unused sessions -- which is good -- but do not provide any visual indication that this has happened. At least one of these consoles (I don't remember which) compounds that problem by then responding to user requests with 401 errors rather than explaining that the user needs to sign in again.

    The better response would be to handle this by popping up a message that the session has timed out and the user needs to log in again.

    The best response would be if that popped-up message included…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Very annoying personalization menu during skill testing.
    Therefore, the skill confirmation screen is as narrow as the pocket-handkerchief garden.
    Remove personalization menu from the test screen.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. While the Interaction Path in the dev console is very handy it does not include APL interactions. More than half my users use the Show and I'd like to see what buttons they press.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. I am a totally blind software developer and I want to learn how to develop Alexa skills. On the developer console when I go to create a new skill and enter the initial information about it, there is a visual only CAPTCHA to resolve before I can create the skill. I can't see the images so can't complete this CAPTCHA. Other CAPTCHAs I've found on Amazon have an audio option which is very good.

    Can we have an audio alternative on the CAPTCHA please when creating a new skill. Better still, maybe no CAPTCHA at all. After all, whoever is…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Is it possible for you to create a counter for tracking sobriety dates or when you quit smoking?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Presently Alexa developer console does not support federated login. We have team of developers who works on the same skill. It is better to have an activity log which keeps track of what changes are done to the skill by which user. This gives us a way to track the changes made by various users.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Because it is case sensitive, the automated NLU tester almost always fails when testing values which may be contained in an Alexa built-in slot.

    It also appears random as to whether the values in the slot are uppercase, lowercase, or even mixed between two words.

    Example: For the slot AMAZON.GB_CITY, it matches the slot values, but shows a fail because sometimes they are lowercase.

    Of course, if I submit all lowercase, then it fails on the ones which are uppercase.

    It would be very easy to make the nlu tester ignore case sensitivity, which would make it more useful.

    E:…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. When seeing your analytics for skill, put in a way to see if customers are using it on a screen or not. To see if there's more engagement with your skill if they see graphics or not (from the APL)

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Need a built-in slot that accepts special characters such as .,/@#%&$*()!"':;<>? , as Alexa couldn't read them as characters but reads them as words like (dot, at, comma, etc.)
    Please Help!

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Be able to put in breaklines in ISP JSON file for long descriptions. It works when you edit the skill.json file when you write content in the Description box on your skill so the same should be applied for description boxes of an ISP product.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Allow developers to add multiple email addresses in the Dev consul under the certification tab to receive feedback pertaining to the skill. In addition place the feedback in the certification tab instead of just having a general message that is of no value to the developer.

    40 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. It would greatly help if the Deploy button, under the Code tab, could check and warn if there were any code errors before deploying the lambda code. Right now I can deploy code with error or even an empty js file. Ideally, the Deploy operation should fail or stop with a good message.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. You would think it would be far easier to grab a project from GitHub in the alexa developer console like one button that opens to enter the git url.

    Currently these are the steps

    1. Open alexa developer console

    2. Name the skill

    3. There is Create Skill Button top right.

    Then again there are other options

    1. Choose a model with seven boxes

    2. Choose a method with three boxes

    3. Ignore all those choices

    4. Press [ Create Skill ]

    Next page

    Choose a template and 10 more boxes to ignore if you want to import from GitHub

    On this page are two boxes top…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. As everyone knows, it is possible to assign regional endpoints in dev console for skill, but testing them is really time consuming, because routing is very inconsistent. Even if I am from UK sometimes requests go to US.

    Another issue is making sure that all endpoints work. Only way I found to test them consistently is by switching default endpoint, with other regional endpoints to get consistent results, which takes a lot of time.

    My suggestion would be, that at least in the dev console, it would be possible to not only pick locale, when testing the skill, but also…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. For large organizations I would like the ability as a developer to create sub- developer accounts within my developer account so that I can give each of my business units/divisions/affiliates a developer account to work in without them having access to ALL dev and production skills in the account. They should only be able to see the skills they are working on, whereas anybody at the top level account can see everything. This is especially important when a developer account receives a particular agreement/protection (in this case our developer account is protected by a HIPAA Business Associate Agreement (BAA) so…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. I'd like the ability to change 'Developer name or company name' under my Amazon Developer Company Profile. In the Amazon Developer portal today, this isn't possible. I know that I can write a support ticket to do this, but a permanent solution where developers can make these updates themselves would be better.

    196 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently one can only simulate a device with a display in the dev console. It would be nice if Dev Console provided a means to test a headless response, given that those make up the most significant share of user requests.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Access Logs and Change history are needed to effectively monitor the changes done by various users in ASK developer console and ASK CLI. In the absence of the access logs and change history, large organizations with multiple ASK users have no way to track changes to Alexa skill in production. If the administrator of the Alexa account has the ability to view change logs, it will give the ability to effectively monitor user changes.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 6 7
  • Don't see your idea?