Alexa Skills - Developer Voice And Vote

Welcome to the Alexa Skills Feature Request site! This site enables Alexa Skills Developers to request and vote on features you’d like to see in the developer toolset and services for Alexa.

To keep this site purpose-driven and actionable, we moderate requests. Here’s some guidance on how to create great feature requests that can be evaluated by our development teams. For conversation, dialogue or help, you should visit our Alexa forums. We appreciate your input.

-Alexa Skills team

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Ability to send back a variable, in the SSML response, which will convert t the user's first name.

    Ability to send back a variable, in the SSML response, which will convert to the user's first name. This allows for the identity to remain hidden to the skill's developer, however, enables the developer to personalize the skill. This can be done for a specific voice profile. If the first name is not available, then it is gracefully ignored. For example:

    <speak>@fname, here is your quote of the day.</speak>
    would either convert to
    "Sebastien, here is your quote of the day"
    Or
    "here is your quote of the day"

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  2. One button to get skill summary since the day of publishing.

    There should be a button to get the summary of skill since the first day of publishing.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  3. increase session time out

    Increase the session time at-least for the developers account. We need to give quality of code right? Some times we may need to debug the code .

    "The requested skill took too long to respond"

    5 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

    Received  ·  1 comment  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  4. Developer console: display all option

    The ADC now loads only in chunks of ~20 skills. I have 300 skills, and each has two versions. I need to scroll and scroll to see the entire list, which important when I need to see the parent/child relationship between the prod + dev versions.

    Can you offer a display-all direct link?

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix translation

    Don't use machine translation to translate the dev interface to other languages. The page on Intent History in the Alexa Console is awful in German and does not make much sense. For example the level of confidence in an utterance (High, Medium, Low) becomes "Vertraulich" in German which happens to mean confidential …

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  6. automatic skill endpoint switching when the development skill goes live

    Add automatic skill endpoint switching when the development skill goes live.

    It will be great to have the possibility to make Live version work with lambda.arn:PROD and Development with lambda.arn:$LATEST aliases. Every time when I want to update my skill I need to do back and forth switching.

    15 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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enhance the dashboard

    Please provide the stat about public comments, rating, post and county wise enabling data in map.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  8. multilingual UI

    Hi,
    while alexa skill development ,i found that create skill in multilingual quite complicated.
    so make it simple UI if possiable

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  10. Automated Test Suite on developer.amazon.com

    Just a bit of feedback on the certification process before an Alexa Skill gets published.
    It now takes 5 business days.
    My skill failed two test cases so after correcting it and re-submission on the same business day I am assuming it will take another 5 business days for certification after re-submission.

    So I would like to suggest that as part of developer.amazon.com a suite of automated test cases can be run by developers as part of submission so that they immediately get a test report which also goes to the Alexa Skill Certification Team.
    This will reduce the developer…

    4 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

    Received  ·  1 comment  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  11. Incorporate handlers into Alexa console for more accurate NLP

    Alexa should only have to decide between the intents available inside of a handler. By integrating handler groupings into the Alexa Console the build process and NLP can take into account these more specific situations and will become more accurate deciding between the 3 intents in a specific handler as opposed to the 18 intents that are available.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add language drop down to Test tab

    Hi. It would be nice if we could toggle between the different supported languages in the Test tab. Currently you need to go back to the build tab, switch languages, then go back to test tab.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  13. Extend of option to entend session duration

    I work 8 hours a day like most developers, so I have to login 3 to 4 times a day because amazon developers log you off automatically every 2 hours? I understand its a security issue but I would like the option to maintain the session a little longer, or at the very least, extend the session duration if the developer is using the console.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  14. Endpoints per intent

    It would be VERY helpful if each intent within a skill can have its own endpoint.
    If you have a company that wants several intents under the one skill, but each intent is really quite seperate functionality, you want to be able to call a different endpoint for each intent so that you can have some sanity over your code organisation.
    Either an web hook per intent, or a lambda per intent.
    Currently you have to but a stack of unrelated code (different intents) into the same lambda.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  15. Intent confirmation doesn't allow $

    I have the following Intent Confirmation:

    Ok, got it. Let me confirm. You want to pick up a car on {startDate} at the {pickupLocation} and return it on {endDate} for a daily rate of ${rentalRate} , right?

    The slot type for rentalRate is number. In order to say the decimal value of rentalRate as "thirty-nine dollars and ninety-nine cents", I need to use the $ before it. There is no SSML say-as to make a decimal number into a currency.

    The UI gives me the following error when I try to add the dollar sign: "You have invalid characters"

    This…

    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

    Received  ·  1 comment  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  16. Build model upon saving endpoint

    Change behaviour when saving endpoint.
    When saving a new endpoint, e.g. to a new lambda version a green pop-up appears. This most likely represents success for most users. But the text says, that the skill has to be build before the change becomes effective. This might easily be forgotten. For example, before I submit a skill for certification I always publish a new version of my lambda endpoint. If I forget to build the skill after adding that endpoint to the skill it might point to $LATEST. That means changes to the lambda would affect the skill in certification or…

    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

    Received  ·  1 comment  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  17. Fix the dev console to allow lambda ARNs with aliases

    For some reason I cannot specify a Lambda endpoint which has an alias qualifier at the end. For example, I want to have two aliases: TEST and PROD that point to different versions of the lambda function.

    When I am trying to save the endpoint, it shows a "manifest error" message.

    It worked fine before. My other skills that were created using the old developer portal UI still have their endpoint

    4 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

    Received  ·  2 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  18. Intent Confirmation Does Not Support SSML and Question Mark

    There is a bug in the new Console. I cannot include both SSML and a question mark because validation says: "You can only have a '?' at the end of a prompt" but for SSML you need to have the closing </speak> tag.

    5 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

    Received  ·  3 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  19. Help and instructions

    When you send your skill for certification at amazon they say that if the skill is not certified they will send you feedback and instructions for how to fix those problems, but when you do what they. You submit again but it caused more problems. All I am saying is that when you fix the problem, you fix the problem. Also if its your first time doing any sort of programming then amazon should directly help you with your skill.

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  20. Improvement suggestions

    Hello, the new interface for Alexa skill is not as good as before, because
    1. The session expired too soon, when user was just starting to fill the Utterance, it took time as user need to fill one by one ( before we can just fill it without pressing adding one. (When session expire, every utterances that I just keyed in went nothing!!! If Amazon wants to keep this UI, please adding the longer session expiression time!
    2. Amazon has to choose if you really want to have developer interface or user interface especially this is called developer tool. However,…

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base