<?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: Conversion tip: Don&#8217;t let bad error messages cost you sales</title>
	<atom:link href="http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html</link>
	<description>Kevin Ertell serves up a cocktail of e-retail and cross-channel strategies, tactics, observations, and ideas.</description>
	<lastBuildDate>Thu, 22 Jul 2010 15:18:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Booking engine update January 2010 &#171; Hurtigruten Web team Blog</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/comment-page-1#comment-2265</link>
		<dc:creator>Booking engine update January 2010 &#171; Hurtigruten Web team Blog</dc:creator>
		<pubDate>Fri, 22 Jan 2010 14:38:49 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.180/~kevinert/retail-shaken-not-stirred/?p=10#comment-2265</guid>
		<description>[...] date. Several error messages have been improved. Learn more about error messages in web solutions here and here (in [...]</description>
		<content:encoded><![CDATA[<p>[...] date. Several error messages have been improved. Learn more about error messages in web solutions here and here (in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don&#8217;t Spook The Customers: Halloween&#8217;s a good time for a user interface review : Segment Target Personalize</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/comment-page-1#comment-1003</link>
		<dc:creator>Don&#8217;t Spook The Customers: Halloween&#8217;s a good time for a user interface review : Segment Target Personalize</dc:creator>
		<pubDate>Fri, 08 Jan 2010 18:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.180/~kevinert/retail-shaken-not-stirred/?p=10#comment-1003</guid>
		<description>[...] I borrowed the above example of a nasty input error message from this excellent article by Kevin Ertell; be sure to read it before reviewing your store&#8217;s user interface. Another article to check [...]</description>
		<content:encoded><![CDATA[<p>[...] I borrowed the above example of a nasty input error message from this excellent article by Kevin Ertell; be sure to read it before reviewing your store&#8217;s user interface. Another article to check [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My Favorite Sites of the Year &#124; Retail: Shaken Not Stirred</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/comment-page-1#comment-831</link>
		<dc:creator>My Favorite Sites of the Year &#124; Retail: Shaken Not Stirred</dc:creator>
		<pubDate>Thu, 07 Jan 2010 01:03:30 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.180/~kevinert/retail-shaken-not-stirred/?p=10#comment-831</guid>
		<description>[...] written error messages are the bane of the web and a shameful way to lose sales, as I&#8217;ve previously discussed. But even well written error messages can be annoying because they come after the fact. [...]</description>
		<content:encoded><![CDATA[<p>[...] written error messages are the bane of the web and a shameful way to lose sales, as I&#8217;ve previously discussed. But even well written error messages can be annoying because they come after the fact. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Stewart</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/comment-page-1#comment-53</link>
		<dc:creator>Jason Stewart</dc:creator>
		<pubDate>Fri, 23 Oct 2009 20:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.180/~kevinert/retail-shaken-not-stirred/?p=10#comment-53</guid>
		<description>Completely agree with your clarifying point Kevin!
</description>
		<content:encoded><![CDATA[<p>Completely agree with your clarifying point Kevin!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Ertell</title>
		<link>http://www.retailshakennotstirred.com/retail-shaken-not-stirred/2009/10/conversion-tip-dont-let-bad-error-messages-cost-you-sales.html/comment-page-1#comment-52</link>
		<dc:creator>Kevin Ertell</dc:creator>
		<pubDate>Thu, 22 Oct 2009 22:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://66.147.244.180/~kevinert/retail-shaken-not-stirred/?p=10#comment-52</guid>
		<description>Thanks for your comment, Eoin, and excellent point about accented characters. I&#039;m really glad the accent on your name showed up correctly on my blog! :-)
I appreciate you bringing the point up, because we Americans can sometimes forget it&#039;s the WORLD WIDE web and languages and character sets other than those from traditional American English are perfectly valid.
</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Eoin, and excellent point about accented characters. I&#8217;m really glad the accent on your name showed up correctly on my blog! <img src='http://www.retailshakennotstirred.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /><br />
I appreciate you bringing the point up, because we Americans can sometimes forget it&#8217;s the WORLD WIDE web and languages and character sets other than those from traditional American English are perfectly valid.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
