Question: Alexa just doesn't understand the word 'postpaid' and I've tried it a million times in my skill. I also tried "Alexa, Simon says postpaid" but it repeats something else other than postpaid, I don't know why. My sample utterance is like this "what is the {type} sales" and the type has custom slot values "postpaid",etc.

I've looked at AMAZON.LITERAL but didn't quite understand it if it will help me in my case. So any workaround will be helpful and thanks in advance.

Answer: 
As a general rule, Windows x64 requires *all* functions to provide unwind information. The only exception is for leaf functions which do not modify `rsp` and do not modify any nonvolatile registers.
Judging by the context of your question, what you really want to know is the practical consequences of not providing unwind information for your non-leaf assembly functions on x64 Windows. Since C++ exceptions are implemented based on SEH exceptions, when I talk about exceptions below, I mean both all "native" (access violation, something thrown using `RaiseException`, etc.) and C++ exceptions. Here's a list off the top of my head:

* Exceptions won't be able to pass through your function

It's important to note that this point is not about throwing an exception, or an access violation happening *directly* in your function. Let's say your assembly code calls into a C++ function, which throws an exception. Even if the caller of your assembly function has a matching `catch` block, it will never be able to catch the exception, as unwinding will stop at your function without the unwind data.

* When walking the stack, the stack walk will stop at the function without unwind data (or go astray; the point is, you will get an invalid call stack)

Basicaly, anything that walks the stack is screwed if your function is present on the call stack (debuggers when displaying the call stack, profilers, etc.)

* Registered [`Unhandled Exception Filters`](https://msdn.microsoft.com/en-us/library/windows/desktop/ms680634(v=vs.85).aspx "Unhandled Exception FIlters") will not be called back if an exception gets thrown, and your assembly function is on the call stack

This interferes with anything that relies on UEFs. Custom crash handlers, for instance. Or something potentially more relevant: `std::terminate` won't be called back in this case, if your program throws a C++ exception, that is unhandled (as it's dictated by the C++ standard). The MSVC runtime uses a UEF to implement this, so this won't work as well.

---

Are you developing a 3rd party library? If that's the case, the importance of the above points will depend on the use case of your clients.