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. Change User doesn't show all accounts

    On the new Console, when I go to my profile, Change User, only 4 of the several accounts of the people I help with show up. Looks like there's a max-width property that's causing the last couple to get hidden.

    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. Searchable and continually updated list of all certified skill invocation names for developers to check

    Allow developers to easily check to see if a skill invocation name has been previously used by another skill.

    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  ·  Interaction Model  ·  Flag idea as inappropriate…  ·  Admin →
  3. Simulator Issues

    Hey I really don't like the new simulator. If there is an endpoint error the simulator just does nothing, nor does it register the error with cloudwatch. I would type out the invocation name and would get 0 response, it was as if the request was never sent. When I would then check the cloudwatch logs there would be nothing reflecting a request either. If I swap to the old version and try the simulator, it will make the request and respond with an error. This will then register in Cloud watch and point me right to where the break…

    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  ·  Skill Test Simulator  ·  Flag idea as inappropriate…  ·  Admin →
  4. New Dashboard - Locale Selection

    Although the new dashboard feels cleaner, it has lost utility. I cannot figure out how to pull a skill from a locale. We use SMAPI and push to all locales and then delete out (in the old dashboard) any locale we don't intend to publish to. In this version, not sure if it's possible, definitely can't figure it out. I also have to click and click to get to a submit button. Put a quick submit int he banner or something.

    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. Add Beta Test Info to ASK Developer Console Skills List

    We can have multiple skills (10+) running in beta test and any given moment. There is no way to know in the main skills list which skills are in beta and when the beta expires. We have 100+ skills in our list which makes it even more challenging.

    Either in a new column or under the Skill ID, add an indication that the skill is in BETA and the date it expires.

    Provide a way to filter the list to only show those in Beta. This could be part of the request to tag and filter skills in the list.…

    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 →
  6. Make the dance between ask cli and web gui better.

    Working between the ask cli and the web gui is fraught with danger. I lost lots of "web gui" Intent work, because I used "ask deploy" which overwrote the model. So I have to be very careful to call "download model" first, check to make sure it has the changes... THEN I can upload my new lambda code without overwritting. Very risky business. (:

    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  ·  ASK SDK  ·  Flag idea as inappropriate…  ·  Admin →
  7. New Console Beta Test in a different section

    Putting the Skill Beta Testing section into Availability is confusing to find. I would have expected it to be under Test or somewhere under a Testing header.

    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  ·  Skills Beta Testing  ·  Flag idea as inappropriate…  ·  Admin →
  8. Option to show SSML tags in chat transcription (ASK Dev Console Beta)

    Provide option to display SSML tags in chat speech bubbles. Currently some words stick together because they're seperated by tags, which are not shown. With the option to display SSML tags it would be easier to analyze the speech output and the effect of certain SSML tags.

    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. Change "Permissions" nav menu button to "Your Users"

    Change "Permissions" nav menu button to "Your Users"

    In the Alexa Console, the "Permissions" button in the left menu makes me think I can provide permissions (e.g. beta testers and administrator access) to the particular Alexa Skill, not user's access to addresses and read/write lists. Might make sense to change the wording to "Your Users" that way the submenu can contain all info pertain to your uses using your Skill and "Permissions" is uses to give certain permissions access to the app on a tester, administrative, business user or marketing permissions to the Skill

    I'm assuming this feed back forum…

    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  ·  Permissions  ·  Flag idea as inappropriate…  ·  Admin →
  10. Alexa App Builder Bug

    BUG:
    When using LITERAL types the editor creates invalid json. If I add a slot of type LITERAL to an intent it automatically adds an invalid object to the types list:

        "types": [
    
    {
    "name": "LITERAL",
    "values": []
    }
    ]

    The model validator complains that the values list can not be empty for a type, but there are not values for a LITERAL type. If I remove the object completely it fixes the schema.

    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  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. Feedback on the new console

    Why have you hidden the Skill ID away onto the dashboard. When I'm updating to a new Lambda version and pasting in the endpoints, I then need to skill to set at lambda, which means I need to go to the dashboard page. Please make it available like it was on the old console.

    Also, please please please, lets have some simple debugging logs and testing of execution for the Lambda.

    Just a little test button next to the endpoint where it fires off something (discovery?) (SmartHome Skill) just to make sure it can execute the Lambda, between the permissions…

    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. Printing Skill code within JSON editor

    Which I'm in the JSON editor (or any part of ASK) can I print the code associated with my skill?
    Thanks,
    Frank M

    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 →
  13. Allow Flash Briefings to connect to any port

    There's no reason Flash Briefings should be confined to ports 80 and 443, as webservices can (and do) run on any almost any port. This restriction causes serious limitations for (among others) people trying to run multiple services on the same EC2 node.

    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  ·  Flash Briefing  ·  Flag idea as inappropriate…  ·  Admin →
  14. Sample Utterance Issue

    Unfortunately Alexa didn't react anymore to my sample utterances. I had to delete all of them and add them again manually

    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  ·  Interaction Model  ·  Flag idea as inappropriate…  ·  Admin →
    Received  ·  Alexa Admin responded

    Thanks for pointing this out! We’ll get this routed over to the appropriate internal team for review.

  15. Missing UI flow in the new beta Alexa Console

    If you select 'Measure' for a live skill from the skill list, then go to the Launch tab, you can't edit anything unless you go back to the Measure tab, switch to Development stage and go to Launch again. A stage selection drop-down in the Launch tab would be more intuitive.

    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 →
  16. One-click return to console

    Should be easier to return to the console from the details of a specific skill. Rather than (or in addition to) "Your Alexa Consoles", add a "Current Console" link that provides a one-click return to the current console.

    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  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. UI Fixes

    The "Save Model" and "Build Model" SHOULD allow you to click it without losing your intent position on the page. Same goes for the "Interaction Model" side menus.

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

    New i/f is neat. Thanks.
    It would be good if you could add the link to CREATE a Lambda endpoint again (it was on the old console).

    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  ·  AWS/Alexa Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Include supported interface approval status in certification process

    Currently, it is difficult to determine between a non-display device, and a skill that simply isn't approved for display interface.

    Per Paul Cutsinger: "For speed, certification will publish your skill for voice only then come back and enable the display once that's tested. So, spot will send this.event.context.System.device.supportedInterfaces.Display once the skill has been certified for that device."

    Would be good to be able to check the status of this process somewhere.

    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  ·  Skill Certification  ·  Flag idea as inappropriate…  ·  Admin →
  20. Measure data is not matching in new and old console.

    Measure data is not matching in new and old console.

    In old console, unique customers are less but Sessions & utterances are more compared to new console.

    I don't think it's not possible to have less users and more utterances.

    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  ·  Skill Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base