How do we handle verbally submitted change requests?

What I usually would do is to document it down and parked it in the product backlog. We will discuss this in our next project meeting on the list of the product backlog items together with whatever change requests documented. In this way, it is making the change requests documented and discussed in a project meeting with the clients. Also, this helped me to answer to my development team on the insertion of new change requests and its rationale. Many times when these new verbal change requests were being discussed, it tends to be prioritised lowly against the other items and not being worked on at all.

H.J., how do you handle emergency change requests that cannot wait for the next project meeting?