<?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: Questions about this email? Too bad!</title>
	<atom:link href="http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/</link>
	<description>Learn beneficial marketing and business principles from everyday experiences</description>
	<lastBuildDate>Mon, 06 Feb 2012 17:52:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Joe Rawlinson</title>
		<link>http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/#comment-229</link>
		<dc:creator>Joe Rawlinson</dc:creator>
		<pubDate>Sun, 03 Dec 2006 19:37:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/#comment-229</guid>
		<description>TJ: I like your solution of the web form. Getting the details of the customer issue before you even see the incoming email is definitely a boost to your productivity. 

I&#039;m sure it cuts down on the back and forth that is so common with email support. Cutting down on the number of email iterations with customers helps them get their answer quicker and saves you time and money on support.</description>
		<content:encoded><![CDATA[<p>TJ: I like your solution of the web form. Getting the details of the customer issue before you even see the incoming email is definitely a boost to your productivity. </p>
<p>I&#8217;m sure it cuts down on the back and forth that is so common with email support. Cutting down on the number of email iterations with customers helps them get their answer quicker and saves you time and money on support.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TJ</title>
		<link>http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/#comment-228</link>
		<dc:creator>TJ</dc:creator>
		<pubDate>Fri, 01 Dec 2006 19:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.returncustomer.com/2006/12/01/questions-about-this-email-too-bad/#comment-228</guid>
		<description>At my company, all of the support requests either went through our 800 number or through our support e-mail address.  About 6 months ago, we switched to a online contact form and the resilts have been nothing short of phenomenal.

With a web contact form, you can get definitive statistics on the types of problems people are having.  By asking for basic information ahead of time, we can troubleshoot much faster and people are more likely to describe their issue.  At least once a day we would receive emails saying only &quot;it does not work help!!!1&quot;.  Since implementing the contact form, we get these sort of requests once a week at the most.

Obviously, this move by MBNA is unacceptable.  While I believe that a no-reply e-mail address is perfectly acceptable, access to support still needs to be clearly labeled and easy to access.</description>
		<content:encoded><![CDATA[<p>At my company, all of the support requests either went through our 800 number or through our support e-mail address.  About 6 months ago, we switched to a online contact form and the resilts have been nothing short of phenomenal.</p>
<p>With a web contact form, you can get definitive statistics on the types of problems people are having.  By asking for basic information ahead of time, we can troubleshoot much faster and people are more likely to describe their issue.  At least once a day we would receive emails saying only &#8220;it does not work help!!!1&#8243;.  Since implementing the contact form, we get these sort of requests once a week at the most.</p>
<p>Obviously, this move by MBNA is unacceptable.  While I believe that a no-reply e-mail address is perfectly acceptable, access to support still needs to be clearly labeled and easy to access.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

