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. Activity Log on developer console.

    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.

    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 →
  2. Allow NLU evaluations to be case insensitive

    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:…

    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. Be able to put in breaklines in ISP JSON file for long descriptions

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  4. Have analytic scores show which Alexa device customers are using

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  5. a built-in slot for special characters

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  6. Uploading from a GitHub repo in the alexa developer console is tedious

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  7. Choosing which endpoint to hit in dev console test

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  8. Code error check before deploy

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to create sub-accounts within a developer account

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  10. Provide means for testing headless responses in Dev Console

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  11. Enable change logs for Alexa ASK console and CLI

    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

    Received  ·  0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  12. Enhancements to ASK developer console and CLI/SMAPI User Roles

    The current permissions for various roles in ASK developer console and CLI/SMAPI are very broad. Large organizations need more control over roles to effectively manage Enterprise level skills. This feature request is to give organizations the ability to configure granular level access based on the roles as shown below.

    Description Administrator Marketer Developer Analyst
    Create Skill Yes No No No
    Delete Skill Yes No No No
    Creating a new
    Intent Yes No Yes No
    Deleting Intents Yes No Yes No
    Modify Existing
    intents Yes Yes Yes Yes
    Updating
    distribution detailsYes Yes Yes No
    Skill Submission/Publishing/Hide/
    Remove the skill Yes No…

    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. Account Linking cannot be removed once enabled in a skill

    As the title suggests, we were recently made aware that Account Linking cannot be removed from a skill once enabled. Not even if the skill is removed. As we do not own the login system we were supposed to implement a page which described the 3rd party login system. When we submitted the skill again we were rejected with the following reason: "Please update the account linking URI to include “nosignup=true” as a parameter for suppressing the signup portions of the Spotify page and resubmit your skill." Where is the documentation regarding the nosignup parameter? How is it supposed to…

    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 →
  14. Other e-mails for skill certification.

    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.

    34 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  ·  7 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. Allow BETA testing once a skill has been submitted or has passed certification but not been released

    Allow users to continue to BETA test once a skill is submitted for certification or in a certified but not released state.

    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  ·  1 comment  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add Exception Intent to Alexa Skill Kit to allow developers handle unrecognized utterances

    Please add a feature to allow developers/lambda function to handle unrecognized utterances.

    It is frustrating to finetune a Fallback intent to catch all the unpredictable words/utterances that a user might say to allow me to handle it using a Lambda function. If no intent is selected by Alexa, Alexa will just re-prompt once and then do nothing and say nothing after the first re-prompt.

    My goal is to allow Alexa to re-prompt twice and for the third time, it can exit the skill when a user says something unrelated. Therefore, it is important to be able to catch all "wrong"…

    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 →
  18. problems of removing a live skill

    After a skill has gone live and gets removed, the changes to the skill cannot be made for invocation name. Everything else can be changed except the invocation name. There is document to deal with the error.

    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 →
  19. Don't cut off Alexa Client Secret on lower resolution Acocunt Linking page renders

    If this page is viewed on a small enough resolution, it will cut off the Alexa Client Secret string without any indication to the end user that they need (or even can?) scroll to the right for the complete string.

    Suggestion is to either make it explicit that the string is being visually truncated and you need to expand the window, or add a "copy to clipboard" function to eliminate any issues.

    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. Enter button on test page

    add enter button on page when typing msg for alexa on test page.

    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

    0 comments  ·  Alexa Developer Console  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 6 7 8
  • Don't see your idea?

Feedback and Knowledge Base