-
Incorporate handlers into Alexa console for more accurate NLP
Alexa should only have to decide between the intents available inside of a handler. By integrating handler groupings into the Alexa Console the build process and NLP can take into account these more specific situations and will become more accurate deciding between the 3 intents in a specific handler as opposed to the 18 intents that are available.
3 votes -
Extend of option to entend session duration
I work 8 hours a day like most developers, so I have to login 3 to 4 times a day because amazon developers log you off automatically every 2 hours? I understand its a security issue but I would like the option to maintain the session a little longer, or at the very least, extend the session duration if the developer is using the console.
3 votes -
Build model upon saving endpoint
Change behaviour when saving endpoint.
When saving a new endpoint, e.g. to a new lambda version a green pop-up appears. This most likely represents success for most users. But the text says, that the skill has to be build before the change becomes effective. This might easily be forgotten. For example, before I submit a skill for certification I always publish a new version of my lambda endpoint. If I forget to build the skill after adding that endpoint to the skill it might point to $LATEST. That means changes to the lambda would affect the skill in certification or…3 votes -
Feedback on the new console
Why have you hidden the Skill ID away onto the dashboard. When I'm updating to a new Lambda version and pasting in the endpoints, I then need to skill to set at lambda, which means I need to go to the dashboard page. Please make it available like it was on the old console.
Also, please please please, lets have some simple debugging logs and testing of execution for the Lambda.
Just a little test button next to the endpoint where it fires off something (discovery?) (SmartHome Skill) just to make sure it can execute the Lambda, between the permissions…
3 votes -
Have analytic scores show which Alexa device customers are using
When seeing your analytics for skill, put in a way to see if customers are using it on a screen or not. To see if there's more engagement with your skill if they see graphics or not (from the APL)
2 votes -
a built-in slot for special characters
Need a built-in slot that accepts special characters such as .,/@#%&$*()!"':;<>? , as Alexa couldn't read them as characters but reads them as words like (dot, at, comma, etc.)
Please Help!2 votes -
Code error check before deploy
It would greatly help if the Deploy button, under the Code tab, could check and warn if there were any code errors before deploying the lambda code. Right now I can deploy code with error or even an empty js file. Ideally, the Deploy operation should fail or stop with a good message.
2 votes -
Allow BETA testing once a skill has been submitted or has passed certification but not been released
Allow users to continue to BETA test once a skill is submitted for certification or in a certified but not released state.
2 votes -
Skills Delete Bug
Deleted skills from the Alexa Skills dashboard should stay deleted. It is frustrating and confusing when those skills re-appear after deleting them.
2 votes -
Make it obvious you're on dev / live skill
When on the dev console it is hard to tell if the project you have open is the dev or live version of a skill without going to specific pages and seeing if the save button is disabled or not.
This could be solved by putting this status somewhere on the page. I think this could be done by putting this info (dev vs live) on the dev console's top bar (so you can see it everywhere), and maybe even color-coding the info to draw the eye.
2 votes -
Can we please add a drag and drop control ability in APL designer
APL needs a drag and drop designer.
2 votes -
Alexa Hosted: Enable Code Version History/Restore
Since Alexa Hosted is based on git repository for code storage (AWS CodeCommit as described in doc), let user view and restore a previous version of code.
It would be veeery useful for people like me who accidentally dropped code, or in general to restore previous version for any reason.
2 votes -
2 votes
-
Enhanced console analytics
Add an all time button to the time interval, the interface is a bit awkward to be able access the data.
As an aid to tracking promotions a since first release stats a first 30 day from release would also be good.
Finally and api to access the analytics would good2 votes -
Customize Dashboard
Custom Dashboard and Status Filter
2 votes -
Intent filter for to skip the match
It is nice to have, inside the Intent editor, a filter that allow the Intent Match to match the intent only if the previous intent was into a list of intents
2 votes -
Post alerts when there are issues affecting large number of users
Post an alert here when you have outage or other issues affecting a large number of users.
2 votes -
deleting an intent should remove required slots from dialogModel
deleted intent with required slots still has required slots in dialogModel
2 votes -
Endpoints per intent
It would be VERY helpful if each intent within a skill can have its own endpoint.
If you have a company that wants several intents under the one skill, but each intent is really quite seperate functionality, you want to be able to call a different endpoint for each intent so that you can have some sanity over your code organisation.
Either an web hook per intent, or a lambda per intent.
Currently you have to but a stack of unrelated code (different intents) into the same lambda.2 votes -
Test 'no response' from user.
It would be very helpful to have a way to mimic 'no response' from the user. If you can do that, it's not obvious how.
2 votes
- Don't see your idea?