If you have an email account and use it for it for work there are two absolute certainties you will face: 1) There are lots of great deals for v1agra and c1alis for the discriminating email shopper and 2) The ambiguous email request for help or support with a problem will blow a good chunk out of your otherwise productive afternoon (and perhaps evening if they time it right). The Productivity 501 blog has the quintessential example of the ambiguous request:

My computer doesn’t work. Help!!!!!
– Jane

An email like this will guarantee three things: 1) Frustrated tech support 2) Multiple back and forth emails to clarify and remedy the problem and 3) an ultimately frustrated user. Emails requesting an action of someone should be as concrete yet as concise as possible to clarify the problem and work towards a quick resolution. Productivity 501 has some great tips for crafting more efficient emails that will reduce confusion and result in a remedy to the request.

• Write from the reader’s standpoint - Make sure you pay attention to the knowledge and experience level of your reader. Define unfamiliar acronyms and use their language.
• Include necessary background information - I will often write a short email asking a question and then at the bottom add additional background or clarifying information. For example, if I’m writing to someone who is new in their position, I may include a bit of background history explaining the current state of affairs. By putting it after my signature, they can continue reading if they have questions, but it does not make my message overly long for people who are already familiar with everything that is going on.
• Anticipate questions - As you compose your email, keep asking yourself “what questions will this statement likely prompt from the reader?” Sometimes this may lead you to add another sentence that will clarify your meaning. Sometimes it may prompt you to add an attachment of related information. In some situations, it might even make sense to put a FAQ (frequently asked questions) at the end of your message.
• Keep messages short - Long messages tend to get ignored. Try to keep your message short. If it needs to be longer, be sure the first paragraph gives a good summary. I’ve found that writing a one or two paragraph message, my signature, and then the bulk of supporting data (after my signature) helps increase the chance that they will read the first part of my message.

Take a look at Productivity 501 or the rest of this great article and some other suggestions for better use of e-communications.