<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Tips to improve your email communication skills  | Beyond The Box</title>
		<link>http://blog.beyondthebox.co.uk/2007/10/12/tips-to-improve-your-email-communication-skills/#comment-64</link>
		<author>Christine Knott</author>
		<pubDate>Wed, 20 Feb 2008 18:55:48 +0000</pubDate>
		<guid>http://blog.beyondthebox.co.uk/2007/10/12/tips-to-improve-your-email-communication-skills/#comment-64</guid>
		<description>I ran the communication course yesterday at Oldham and as you have mentioned in your post the email section was well received. One delegate raised an interesting point about how it can be used negatively. He asked how someone should deal with a situation when senders maliciously copy in a third party if the content is focussed on highlighting mistakes that the recipent has made. I suggested that the companys email policy is referred to or the sender is approached to discuss the situation. It all boils down to personal values I suppose but it is a tricky one. Has anyone had any similar situations? Does anyone have any ideas for handling an instance like this? We'd love to hear from you.</description>
		<content:encoded><![CDATA[<p>I ran the communication course yesterday at Oldham and as you have mentioned in your post the email section was well received. One delegate raised an interesting point about how it can be used negatively. He asked how someone should deal with a situation when senders maliciously copy in a third party if the content is focussed on highlighting mistakes that the recipent has made. I suggested that the companys email policy is referred to or the sender is approached to discuss the situation. It all boils down to personal values I suppose but it is a tricky one. Has anyone had any similar situations? Does anyone have any ideas for handling an instance like this? We&#8217;d love to hear from you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
