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

51 results found

  1. we need a type for money. so if i say, "i want to pay 4 dollars and 12 cents" the slot returns 4.12. currently i'm using two slots and a lot of utterances which is painful.

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

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

  2. We would like to use this, but can't because the rules are too restrictive.If a user is asked about what they want info about, they should not be forced to say "tell me about Point Defiance Zoo". They should be able to say "Point Defiance Zoo" with no leading phrase. Instead of forcing us to use a leading or trailing phrase, please allow the use of just {query} (without 'search for...' or other text around it as in the example below:
    {

        "name": "SearchIntent",
    
        "samples": [
    
          "search for {Query}",
    
          "find out {Query}",
    
          "search for {Query} near me"
    
        ],
    
        "slots": [
    70 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)
  3. Get the probability a slot was selected.

    This would help an experienced developer implement a dialog to confirm with the user or to execute indent directly.

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

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

  4. Create an AMAZON.ALPHANUMERIC slot type (although with a better, shorter name!) This would extend the current AMAZON.NUMBER slot type and hopefully improve the recognition model. Discussed in https://forums.developer.amazon.com/questions/4821/how-would-you-design-slots-for-letter-and-number-c.html

    21 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. Would be great to be able to record & handle audio files with Alexa.

    For example: "Alexa, start recording", recording.... "Alexa, stop recording" & then we developers would get an audio file of that. That would be a great feature & would give a lot of opportunities for new apps.

    Keep voting this up :)

    20 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. Need a "number" that supports leading zero's. So when a user enters "012" it reads back "zero one two". The current number type reads back "twelve".

    14 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)
  7. I make use of AMAZON.Time slot in my skill. I received feedback from the certification team that I should confirm if a user meant AM or PM when specifying a twelve-hour time. There is one edge case that poses an annoying problem with this feedback.

    Since all times are parsed as 24-hour format by the AMAZON.Time slot type, I have no way to know whether a user said, for example "five" or "five a.m." because both get parsed as "05:00". In other words, I lose information about whether the user already explicitly said "five a.m." or if they just said…

    13 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)
  8. For custom slot types, regular expression should also be allowed. This can help with lot of complications when it comes to custom slot types

    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)
  9. Our skill uses SearchQuery in order to accept a "free-form" and unstructured response from the user. However, the SearchQuery intent is still restricted to the 8 second response limit. This can be confusing for users, as the user has no way of knowing that the 8 second limit exists or how long they have been talking for. To make things worse, Alexa will actually let you talk for longer than 8 seconds but will reject the response if it was longer than the limit. If no reprompt is set, the skill is terminated and the user is left with no…

    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)
  10. Please provide a UK postcode slot for Alexa

    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)
  11. Immagine you need to shut down the bedroom light AND THEN turn on the TV AND THEN rise up the volume ETC...

    Right now you have to say:
    Alexa... shut down the bedroom light... wait... OK....
    Alexa... turn on the TV ... wait... OK....
    Alexa... rise up the volume on the TV ... wait... OK...

    It would be wonderful to be able to concatenate Alexa actions, using some custom words like: COMMAND0 ['AND THEN' COMMAND1] ...['AND THEN' COMMAND_N]

    The word should be unique and it's higly suggested to be considered a RESERVED key which developer might not use…

    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)
  12. Since AMAZON.LITERAL is discontinued and developers are encouraged to use AMAZON.SearchQuery or Slot values to handle the data.

    We have a requirement for building skill with parsing the entire spoken text as token to the API for further business processing.

    Tried with Amazon.SearchQuery (fails when no matching utterance found) and Fallback intent (only failed mapping from Slots are returned) with no luck.

    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)
  13. People think differently how to describe what they want, and so they have many different ways to verbalize slots. Currently, to account for those different words, the developer would have to manually come up with those variations. Either though their imagination or by manually asking people to interact with the skill. These are great methods, but they are slow and very localized.

    It would be great to have some tool, like a built-in mass user testing tool or even a built in synonym recommendation tool.

    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)
  14. Have AMAZON.Number accept decimal points in user verbal input. Right now, it handles 'minus' or negative numbers, but not when there is a decimal point.

    6 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. ISP requires a "purchase"-intent to be available in the interaction model, currently every developer implements his own "purchase"-intent with his own utterances. This is not user friendly, as a user cannot rely on being able to use learned utterances from "skill A" in "skill B". So my idea is a new standard built-in "PurchaseIntent".

    6 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. I constantly come across the need for JOIN Slot Type: a Type that includes other Type(s) and some new values.

    In my case, I have few thousands of VALUE in two Slot Types that should be included in several other Types as well; so, keep repeating these in my model json file is really annoying.

    I think one solution would be simply a feature to define a Slot Type as a subset of another Type rather than repeating Values...

    6 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)
  17. Hi,
    is there a way to set devault slot values?
    I work with money value slots and in german there is the problem with "one".
    We count one (1), two (2), three (3)...
    in german eins, zwei, drei ...
    but we don't say "eins Euro" we say "einen Euro" or "ein Euro". Same for one cent or size value.

    I know I can fix it with a secound intent like:
    1. Intent
    {euro} Euro
    2. Intent
    ein Euro
    einen Euro

    If there a better way to do it? something like fix slot values depending on the utterances?

    greatings
    Marc

    6 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. Unfortunaly the AMAZON.Date slot is auto completed by the model with the year, even if the year is not specified by the user. e.g. "give me my trips from 15. August" returns in the slot something like 15.8.2018, but of cause the user did not specifiy the year, but the skill developer does simply not know that the year was not provided!

    This could be solved, via some enhancement and would not break existing skils.

    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

    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 submitting this request. Your request has been received.

  19. Why not letting the user directly submit feature requests, leave feedbacks and report bugs?
    We know that the most important thing that allows a developer to build a high-quality product is the feedback from the end-user.
    Receiving them during the beta-testing phase or submitted through email from the user may not be enough and its not simple, fast and fun.
    For every custom skill, i would like to use Built-In Intents, example:

    AMAZON.FeatureRequestIntent:

    • User: "Alexa, tell {skill_name} that i would like to leave a feedback"
    • Alexa: "Please tell me more"
    • User: "I would really appreciate if i could {action...}"
    • Alexa:…
    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)
  20. Improve dynamic entities increasing the 100 value limit and the 30 minutes caching

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