Think about it from the client's perspective - using Github issues might be your preferred way of tracking the changes he requests, but it is unlikely his prefe

Think about it from the client's perspective - using Github issues might be your preferred way of tracking the changes he requests, but it is unlikely his preferred tool. He just wants to email you the changes he wants and have them made - the implementation is not his concern. As soon as the client feels like he doesn't understand what you are saying, you stop becoming a problem-solver and start becoming a problem. In addition to whatever responsibilities he has on his end, now he needs to try to figure out what you are saying. The key to a happy client is removing problems from their plate. Here's a different way to communicate the same things as your original email: $CLIENT, you mentioned that you wanted a few changes to the content of the site. If the changes are easy to describe, you can just email them to me and I will take care of it. Otherwise let's sit down/have a phone call about the changes. I've also done some research into the digital signage that we discussed. I found an option that will cost $30-$40 per sign, is that within your budget? I can present all the options I've found at our next meeting. Notice that I tried to avoid any deep technical details (e.g. after you email me the changes, I will add an item to the bug tracker and do feature-branching to implement the changes then deploy to the staging server). My version is not perfect either, but I think it would be better received.