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

Alexa Skills - Developer Voice And Vote

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. The recently introduced AMAZON.FallbackIntent, which allows utterances which do not match any of the utterances associated with other intents to be picked up by a skill, is extremely useful. However, this can only be used in English (US) skills and not any any other languages, such as English (UK). This makes development harder than it should be and discourages developers from creating their skills in multiple languages.

    88 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

    16 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. I have a skill that looks up property management information for apartment buildings. We have over 150 properties which are defined as values for a slot. 4 digit property numbers for values and string property names as synonyms.

    I would like to be able to query a database for the slot values and synonyms dynamically at runtime.

    85 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

    9 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. It would be nice if AMAZON.NUMBER handled ordinals... I give the user a list and ask which he wants more information on. The user says "the first" and it should resolve to 1.

    11 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

    1 comment  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  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. Currently AMAZON.FallbackIntent is only available for english and german. Please make it possible for French.

    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

    0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Launched  ·  Alexa Admin responded

    Hello,

    Thank you for submitting an Alexa Skills Feature Request. We are happy to inform you that the feature you have requested has launched! Please refer to the following pages for more information:

    https://developer.amazon.com/en-US/blogs/alexa/alexa-skills-kit/2019/11/handle-unexpected-user-requests-with-FallbackIntent-phonenumber-ordinal-built-in-slots-expanded

    https://developer.amazon.com/en-US/docs/alexa/custom-skills/standard-built-in-intents.html#fallback

  5. I discovered a weird bug in German:

    • Slot with name "forWhom"
    • Slot Value: "me"
    • Synonym for "me": "mich"

    When you elicit the slot and answer "mich", I am getting this:

    "forWhom": {
    "name": "forWhom",
    "value": "Mitch",
    "resolutions": {
    "resolutionsPerAuthority": [
    {
    "authority": "...",
    "status": {
    "code": "ERSUCCESSMATCH"
    },
    "values": [
    {
    "value": {
    "name": "me",
    "id": "me"
    }
    }
    ]
    },
    {
    "authority": "...",
    "status": {
    "code": "ERSUCCESSNO_MATCH"
    }
    }
    ]
    },
    "confirmationStatus": "NONE"
    },

    Where does "Mitch" come from?

    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

    0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  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. For the AMAZON.Date Slot, Alexa does not seem to understand numbers like 28 or 25 as the day. It just does not resolve to anything, no mattter how clearly I speak out "Achtundzwanzig" (28 in German). It works with 11, 15 and the like, but with many others it doesn't - 28 in particular.

    example where it does not work:
    "Achtundzwanziger August 2018".

    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

    1 comment  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Launched  ·  Alexa Admin responded

    Hello,

    Thank you for submitting an Alexa Skills Feature Request. We are happy to inform you that the feature you have requested has launched!

    We can confirm that the most recent version of the AMAZON.DATE built-in slot resolves dates containing numbers like “acht und zwanzigste/r” and “fünf und zwanzigste/r” correctly to either “28” or “25”.
    Please note that the date is provided to your service in ISO-8601 date format, which means the utterance “acht und zwanzigster august zwei tausend achtzehn” returns the value “2018-08-28”, for example*:
    ‘slots’: {
    ‘date’: {
    ‘confirmation_status’: ‘NONE’,
    ‘name’: ‘date’,
    ‘resolutions’: None,
    ‘value’: ‘2018-08-28’}
    }

  7. I'm trying to get Alexa to understand the German "zehnter august neunzehn hundert zwei und achtzig" as date, but it always recognizes this as {"value": "2018-08-10"}. It seems it's impossible to pass past dates to Alexa. I think it would be valuable to have that feature.

    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

    0 comments  ·  Built-in Intent / Slots  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Launched  ·  Alexa Admin responded

    Hello,

    Thank you for submitting an Alexa Skills Feature Request. We are happy to inform you that the feature you have requested has launched!

    We can confirm that the most recent version of the AMAZON.DATE built-in slot also resolves past dates into the correct output value.
    Please note that the date is provided to your service in ISO-8601 date format, which means the utterance “zehnter august neunzehn hundert zwei und achtzig” returns the value “1982-08-10”, for example*:
    ‘slots’: {
    ‘date’: {
    ‘confirmation_status’: ‘NONE’,
    ‘name’: ‘date’,
    ‘resolutions’: None,
    ‘value’: ‘1982-08-10’}
    }

  • Don't see your idea?