In the test simulator, it would be great if "8" would be understood as a spoken word "eight" so I don't have to type a number every time. This took me about 3 hours to figure out / debug a bug in my code that wasn't there.

Allow an al time selection in the analytics section

In the Alexa Developer Console Test panel, add a button next to each bubble in the transcript pane that reloads that phrase and submits with 1 click.

In testing it's common to use the same value over and over and over, currently I do the very tedious: select the transcript text, copy, paste into the input field, hit enter. Should be an easy feature upgrade to give a button next to all inputs in the transcript so they can be reloaded quickly.

Hi,

Your dropdown for selecting months in the Earnings tab is not displaying all months depending on the number of rows in the table below it. I, for instance, can only select up to June.

Cheers,
Lennert

Bad user interface. Also, no step-by-step instruction how to convert a skills created in 2017 to the new format.

When a build fails or save fails, the error prompt is not descriptive:

Operation Failed
The attempted operation has returned an unspecified error. This may be due to an expired session, or a model that exceeds 1MB in size.

Think more descriptive and precises error messages are needed, algo between every save or build I usually make several changes, it would be nice so the difference between actual json and the one from the previous successful save.

Ability to send back a variable, in the SSML response, which will convert to the user's first name. This allows for the identity to remain hidden to the skill's developer, however, enables the developer to personalize the skill. This can be done for a specific voice profile. If the first name is not available, then it is gracefully ignored. For example:

<speak>@fname, here is your quote of the day.</speak>
would either convert to
"Sebastien, here is your quote of the day"
Or
"here is your quote of the day"

The tutorial screenshots do not match the current builder.

For example https://developer.amazon.com/alexa-skills-kit/tutorials/fact-skill-1 looks like https://www.dropbox.com/s/bp4p4xru11iama5/Screenshot%202018-05-03%2014.23.31.png?dl=0

Yet the actual Skill builder looks like https://www.dropbox.com/s/e4kk4eo1o9lv50g/Screenshot%202018-05-03%2014.23.42.png?dl=0

This makes following the tutorial a little confusing and difficult.

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.

Click to View a skill that has a status of "Live." Buttons such as Save Model, Build Model, Save Interfaces, Save Endpoints appear disabled, but when you click on one, they still trigger an event.

Responses include:

Save Failed
Provided eTag does not match with the resource's current eTag. Please apply your changes on the latest version of the resource. Error code: InvalidEtag - Tuesday, Apr 3, 2018, 3:48 PM

Interaction Model Saved Successfully
The interaction model has been saved without errors. The Model must be successfully built for changes to take effect. - Tuesday, Apr 3, 2018, 3:49 PM

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.

Currently ASK doesn't provide original user utterances in its request body. But it would be a great enhancement if it does so. It enables the Alexa Skills Developers to help improve the end user experience by collecting different sorts of original user utterances and update the intent invocations of our custom skills

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.