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 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 -
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 voteThanks for pointing this out! We’ll get this routed over to the appropriate internal team for review.
-
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 -
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.Displayonce the skill has been certified for that device."Would be good to be able to check the status of this process somewhere.
1 vote -
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 -
"Unsaved data" flow doesn't work properly
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:
- 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.
- 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 -
Scrollable Left Navigation and Fixed right portion
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 -
Bulk upload of training for the new Beta Builder
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 voteThanks a lot for posting this request. Your request has been received
-
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 -
Reprompt Webhook in case of SessionEnded Request due to ENDPOINT_TIME_OUT
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
- Don't see your idea?