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. 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. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. The simulator only offers display-based devices to simulate, meaning that multimodal skills that behave differently for display vs non-display devices can't be tested. The "Device Display" menu should have an option for "No display".

    7 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)
  5. Have a configuration for the REDIRECT_URI to NOT be passed as part of the URL parameters from Alexa Skill linking. Since we know the possible URIs to redirect to, we would keep these URIs in our app configuration to use when sending back instead of getting the URI as a parameter attribute.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. When speaking with Alexa and specifying a clients name for search in our system. Alexa is able to pick up common English names like “Smith”, “John”....etc.

    Though as soon as you say something different like “Aitken”, “Hannam”, “Arundel”… It has a close to 0% chance of translating speech to the correct text spelling.

    If I load these unique names as slot values in the static interaction model json, it would work very well. However this model has a limit file size of 1.5MB. We have hundreds or millions of variations if we combine all the firms using our software. So…

    7 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. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. When you navigate to Certification Tab after making a change in Code or Distribution tab
    Expected:
    It should launch validation automatically and display only remaining errors after validation checks with new changes.
    Observed:
    I was been displayed all errors and need to press run to run the validation.

    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)
  12. My desire: To use slots of one type in values for slots of another type.

    My reason: I am using an API that also process language. I must send a string to the API detailing an initial condition; let's call that slot X. The slot that gathers the initial condition reuses a specific word (let's call it Y) and several of it synonyms over and over again. So if i could enter values for slot X such as "my head {Y}" or "my arm {Y}", it would save me a great deal of time.

    Counter Argument: Why not just concatenate…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Add version control to the Alexa-hosted Skills environment

    9 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. When on the dev console it is hard to tell if the project you have open is the dev or live version of a skill without going to specific pages and seeing if the save button is disabled or not.

    This could be solved by putting this status somewhere on the page. I think this could be done by putting this info (dev vs live) on the dev console's top bar (so you can see it everywhere), and maybe even color-coding the info to draw the eye.

    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. The Intent History page in the developer console is a great tool for anyone trying to refine their voice model. The one thing it lacks, when viewing misfiring intents, however, is any indication of the scale of the problem. The output is just a giant list of utterance-to-intent mappings, without any context of how often those failed mappings are happening.

    In the case of my skill CompliBot, for example, a recent look at the Intent History output gave me 13000+ unique entries, many of which were hitting the fallback intent when they needed to be hitting actual intents. Searching through…

    10 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)
  16. My desire: An API to upload a CSV to Edit or Upload Sample Utterances in Bulk

    My reason: We have a daily update set of ~ 15000 slot values and it would be very helpful if there was an API to automatically update the slot values using a CSV instead of manually updating them.

    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. 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)
  18. At the moment ASK-CLI can only be implemented using your CLI, but as I do not use it at all it'd be really cool if you could add a possibility to activate Procative Events using only web interface.

    I personally think all features should be accessible from the web even before they are implemented in CLI.

    8 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. A way to gather Alexa Reporting KPI's like Sessions, Utterances and Visitors without having to log into the Developer Console. Something I could access from an API would be ideal. I'm managing 15 skills and flash briefings and don't want to pull each number manually when it could be easily automated.

    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. The editor should keep the position of where each tab is being edit, so that when we move from one tab to another and then come back to the initial tab, we go to the same place.

    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)
  • Don't see your idea?