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

993 results found

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. In the Launch tab of the new skills console, when you are working on language-specific metadata, there is a dialog that pops up if you haven't saved all of the information before navigating away. This flow does two things that it shouldn't do:

    1. The dialog will trigger if all you've done is click into a text box, even if you've made no change to that box.
    2. After resolving the dialog (discard or save), the page redirects you to the "privacy and compliance" sub-page, even if that's not the thing you clicked on to trigger the dialog in the first 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)
  10. Love it! So clean and consistant. One feedback on the left hand navigation. Make it scrollable so when we have lots of intents open we are able to see the right side of the page. Or better yet keep the right side of the page fixed and we can scroll the left hand navigation freely and open / collapse intents etc. Keep up the good work team! :-)

    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. The interaction model has two view - the old preview one and the new Beta preview one. They support different features and switching in between, deletes the changes made. The only reason why my team is still using the old preview, is because we can easily upload new and edit the old training. Would be great if this is also possible in the Beta preview, as to use the other new features available, like synonyms, dialogues, etc.

    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)
    Received  ·  Alexa Admin responded

    Thanks a lot for posting this request. Your request has been received

  12. Amazon.DATE supports values such as previous/next month, week, day or year. It doesn't support date input such as next two months. Need support to specify the duration of previous/next request for Amazon.DATE.

    0 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. Hi Alexians,

    I am facing an issue with my use case. In my use case, it's sending some recommendation to users based on the query. The recommendations response takes sometime more time than expected and ends up with sessionEndedRequest Timeout. can it be possible for Alexa to send the same request as (like re-prompt customer ) rempromt alexa Skill which will invoke our webhook again and will send my response quickly this time because recommendations will be already in memory. It would be a great use case to handle session Ended Request. You may put a limit of reprompt alexa…

    0 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
1 2 46 47 48 50 Next →
  • Don't see your idea?