<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Describe Behavior, Not Feelings, in Your Mystery Shop Reports</title>
	<atom:link href="http://www.mysteryshoppersmanual.com/describe-behavior-not-feelings-in-your-mystery-shop-reports/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mysteryshoppersmanual.com/describe-behavior-not-feelings-in-your-mystery-shop-reports</link>
	<description>Tips for being a successful professional shopper</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:50:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Cathy Stucker</title>
		<link>http://www.mysteryshoppersmanual.com/describe-behavior-not-feelings-in-your-mystery-shop-reports/comment-page-1#comment-2210</link>
		<dc:creator>Cathy Stucker</dc:creator>
		<pubDate>Tue, 09 Nov 2010 20:35:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysteryshoppersmanual.com/?p=786#comment-2210</guid>
		<description>That can be frustrating; however, it appears that the client does not want long comment and lots of details. It may be acceptable to use symbols such as &#039;&amp;&#039; in these reports to save space--it all depends on the company and the client.

Watch out for any unnecessary words, such as very, really, so, etc. Just keep your writing as tight as possible.

If there are things you believe they need to know that simply will not fit in the space allowed, send an email with the information to your scheduler.</description>
		<content:encoded><![CDATA[<p>That can be frustrating; however, it appears that the client does not want long comment and lots of details. It may be acceptable to use symbols such as &#8216;&#038;&#8217; in these reports to save space&#8211;it all depends on the company and the client.</p>
<p>Watch out for any unnecessary words, such as very, really, so, etc. Just keep your writing as tight as possible.</p>
<p>If there are things you believe they need to know that simply will not fit in the space allowed, send an email with the information to your scheduler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kara smith</title>
		<link>http://www.mysteryshoppersmanual.com/describe-behavior-not-feelings-in-your-mystery-shop-reports/comment-page-1#comment-2209</link>
		<dc:creator>kara smith</dc:creator>
		<pubDate>Tue, 09 Nov 2010 17:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysteryshoppersmanual.com/?p=786#comment-2209</guid>
		<description>I am struggling with writing reports that have a strict &#039;character count&#039; in their comments sections.  I find that I am trying to give good descriptions &amp; then I run out of space!  This means I have to rework or delete details in order to fit the answer in the space provided.  Do you have any suggestions I can use in these situations?  Is it appropriate to use shorthand or symbols (like &amp; or w/) in the comments in my online reports?</description>
		<content:encoded><![CDATA[<p>I am struggling with writing reports that have a strict &#8216;character count&#8217; in their comments sections.  I find that I am trying to give good descriptions &amp; then I run out of space!  This means I have to rework or delete details in order to fit the answer in the space provided.  Do you have any suggestions I can use in these situations?  Is it appropriate to use shorthand or symbols (like &amp; or w/) in the comments in my online reports?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

