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.

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.

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)

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!

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.

Allow users to continue to BETA test once a skill is submitted for certification or in a certified but not released state.

Deleted skills from the Alexa Skills dashboard should stay deleted. It is frustrating and confusing when those skills re-appear after deleting them.

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.

APL needs a drag and drop designer.

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.

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 good

Custom Dashboard and Status Filter

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

Post an alert here when you have outage or other issues affecting a large number of users.

deleted intent with required slots still has required slots in dialogModel

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.

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.