<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Business Writing Today &#187; business email guidelines</title>
	<atom:link href="http://www.businesswritingtoday.net/tag/business-email-guidelines/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.businesswritingtoday.net</link>
	<description>Clear writing brings success.</description>
	<lastBuildDate>Mon, 14 Jun 2010 17:52:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Business Email: 20 Guidelines</title>
		<link>http://www.businesswritingtoday.net/business-email-20-guidelines/</link>
		<comments>http://www.businesswritingtoday.net/business-email-20-guidelines/#comments</comments>
		<pubDate>Thu, 23 Apr 2009 19:06:40 +0000</pubDate>
		<dc:creator>Charles</dc:creator>
				<category><![CDATA[Email]]></category>
		<category><![CDATA[business email guidelines]]></category>

		<guid isPermaLink="false">http://www.businesswritingtoday.net/?p=243</guid>
		<description><![CDATA[Every business should understand that it&#8217;s responsible for the content of emails that go out under its name.  Here are some &#8220;do and don&#8217;t&#8221; reminders that we should all keep in mind.
Do:

Be clear and concise.  Help your reader by providing context when necessary.
Answer questions thoroughly.
Always use correct spelling, grammar, and punctuation.  Proofread and revise before [...]]]></description>
			<content:encoded><![CDATA[<p>Every business should understand that it&#8217;s responsible for the content of emails that go out under its name.  Here are some &#8220;do and don&#8217;t&#8221; reminders that <img style=' float: right; padding: 4px; margin: 0 0 2px 7px;'  class="alignright size-medium wp-image-244" title="email-symbol" src="http://www.businesswritingtoday.net/blog/wp-content/uploads/2009/04/email-symbol-300x198.jpg" alt="email-symbol" width="300" height="198" />we should all keep in mind.</p>
<p><strong>Do:</strong></p>
<ol>
<li>Be clear and concise.  Help your reader by providing context when necessary.</li>
<li>Answer questions thoroughly.</li>
<li>Always use correct spelling, grammar, and punctuation.  Proofread and revise before sending.</li>
<li>Indicate content and purpose in the subject line.  Be specific.</li>
<li>Use &#8220;reply&#8221; and keep to the message thread.</li>
<li>Adopt a legal disclaimer and use it in every email.</li>
<li>Have a formal email policy.</li>
<li>Write with gender neutrality in mind.</li>
<li>Remember that company email isn&#8217;t private.  It&#8217;s company property.</li>
<li>Include complete contact information in your signature.</li>
</ol>
<p><strong>Don&#8217;t:</strong></p>
<ol>
<li>Use too much industry jargon.</li>
<li>Capitalize every word in your subject line.  This can be interpreted as spam.</li>
<li>Use &#8220;reply all&#8221; indiscriminately.  If it&#8217;s appropriate, go ahead.</li>
<li>Use a high-priority flag or &#8220;urgent&#8221; in your subject line unless it&#8217;s warranted.</li>
<li>Use language that could be interpreted as libelous, defamatory, sexist, or racist.</li>
<li>Treat company email as your own.</li>
<li>Send irate emails.  Cool off.  Use the phone.</li>
<li>Send emails to a large number of recipients.  This can expose email addresses to unauthorized persons.  Use &#8220;bcc&#8221; instead.</li>
<li>Write long paragraphs.  Readers hate to see &#8220;walls of words&#8221; and will resist reading such emails.  Instead, break up the text, use bullets.</li>
<li>Be redundant.  Say it once.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.businesswritingtoday.net/business-email-20-guidelines/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
