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. Making a CatchAll slot

    At the moment there isn't the possibility to use a CatchAll slot.

    We can use SearchQuery but only if there isn't any custom slot in the utterance.

    It would be great if there is the possibility to use a slot that can catch everything

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  2. Slot for IPV4 address

    IP address slot

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  3. Deactivate intents directive depending on context

    Depending on the state of the user discussion, It could be useful to be able to deactivate on the fly some intents, by sending an appropriate directive, to restrict the intents matching possibilities and make the intent selection more efficient.

    For instance, if I have a skill with the following intents:
    - ListPossibleGames
    - StartAGame
    - ProvideGameAnswer
    If my game have two states: ChooseGame and Playing.
    It could be useful, to deactivate the ProvideGameAnswer intent when being in ChooseGame state, and to disable the two others when being in Playing state. This way, Alexa will never retrieve by accident an…

    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  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow longer responses for AMAZON.SearchQuery

    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…

    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

    Received  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  5. AMAZON.US_FIRST_NAME doesn't handle multi-word names

    The built-in slot type AMAZON.USFIRSTNAME has a very large list of names, and it matches those names fairly consistently. One weakness it has, however, is that it does not handle double names (https://en.wikipedia.org/wiki/Double_name), such as "*********", properly.

    Steps to reproduce:
    1. Open the developer console
    2. Create a skill with an intent that has a slot for USFIRSTNAME
    3. Open the test console
    4. Launch the skill
    5. Attempt to the invoke the intent using the name "Billie Jean"

    Expected:
    -Slot value sent to skill is "Billie Jean"

    Actual:
    -Slot value sent to skill…

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  6. fallback

    I would like to know the utterances that triggered Fallback intent so that I can improve my skill over time.

    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  ·  1 comment  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  7. Replacement for AMAZON.LITERAL

    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.

    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

    Received  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  8. Include 12/24 time interpretation in SSML

    I am currently building an Alexa skill that uses an external API (LibCal). The API returns the availability of study rooms in military time (13:00, etc). This is not an issue because the AMAZON.TIME slot changes a user given time to military automatically (from "one pm" to "13:00") so I can search for a given time without converting. However, I would like Alexa to speak out times in Standard rather than Military. As of now, Alexa speaks times like "13:00" as "thirteen hundred hours". It would be great if Alexa can recognize military times (the same way it does when…

    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  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add AMAZON.Number support in AMAZON.SelectIntent

    Right now SelectIntent supports AMAZON.Ordinal for options (fifth option). But it doesn't support AMAZON.Number Slot type (option five). We are getting user responses like "option five" instead of "fifth option". We cannot expect the user to say "select fifth option" instead user might say option five. Adding Number slot type to SelectIntent would fulfill the intent purpose.

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  10. Recognize tenths of an hour with AMAZON.DURATION

    The built-in intent does not correctly interpret durations like "point one hours" or "point two hours". Instead, it interprets them as on hour (PT1H) and two hours (PT2H), respectively. It would be great to see the built-in intent extended with this capability.

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  11. Fallbackintent

    It would be very useful to have some way to retrieve in the endpoint which user input activated Fallback intent so the endpoint could add it's own mechanisms for managing it

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  12. slot type for currency

    Have slot types for currency as with AMAZON.numbers you wont get far (in my case I build a pocket money tracker and now my son things he has 102 euro instead of 2.50€ 😫)

    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

    Received  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  13. Specify duration for Amazon.DATE

    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

    Received  ·  0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  14. Post Code slot type

    Include PostCode slot type

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  15. Capture if AM/PM was specified in AMAZON.Time slot

    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…

    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

    Received  ·  3 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support AMAZON.JP_CITY and AMAZON.JP_REGION

    We wanna create some skills about Japanese to the Skill store in the US.
    But in the US there are no built-in list slot types about Japan.

    We want to use list slots for Japanese City and Region slots like an AMAZON.ATCITY and AMAZON.ATREGION.

    Thanks,

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  17. Second Address Line beyond AMAZON.PostalAddress

    AMAZON.PostalAddress in the US Alexa Skill builder is the equivalent of a first line of a physical address - house number and street name. Is there a plan to accomodate a second line that could have an apartment/suite/room identifier and an apartment number, etc.? Currently, in order to include apartment identifiers they have to be combined on the same line as the Street name/house number.

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  18. Don't auto-complete AMAZON.DATE because it returns wrong results.

    When a user says just a month for AMAZON.DATE slot the slot value is returned with next year's year.

    For example - "whatever utterance in July?" returns 2019-07-01 for July.

    As a skill developer how can I tell if the user just said "July" (which would much more likely be July this year, i.e. 2018-07) or if they really said "July next year"?

    Also there is no distinction between dates with days and just months. If the user says "whatever in July" returns the same as "whatever on July 1st" - how can I tell if they are talking about…

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  19. Using original version of the built in slot after extending

    In an alexa skill, after extending the built in Amazon intents like AMAZON.person for a particular intent, we can't use the original version of AMAZON.Person for other intents. It would be better if the original version will be available even after extending.

    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  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  20. Regular expression for custom slot types

    For custom slot types, regular expression should also be allowed. This can help with lot of complications when it comes to custom slot types

    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

    Received  ·  2 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base