<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Customer retention: update 3</title>
	<atom:link href="http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/</link>
	<description></description>
	<lastBuildDate>Tue, 08 Dec 2009 17:33:59 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mulqueeny</title>
		<link>http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/#comment-80</link>
		<dc:creator>Mulqueeny</dc:creator>
		<pubDate>Thu, 13 Mar 2008 10:40:52 +0000</pubDate>
		<guid isPermaLink="false">http://mulqueeny.wordpress.com/?p=24#comment-80</guid>
		<description>Down boy :) and I thank you</description>
		<content:encoded><![CDATA[<p>Down boy <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  and I thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/#comment-79</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Thu, 13 Mar 2008 10:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://mulqueeny.wordpress.com/?p=24#comment-79</guid>
		<description>In which case, I bow to your wisdom, beauty, charm, and firmness of fetlock. A lot of palaver, though, for something that really ought to have been issue number one for the team changing the cms. Hey, let&#039;s rebuild the website in a way that completely breaks it! Top plan! Trebles all round!</description>
		<content:encoded><![CDATA[<p>In which case, I bow to your wisdom, beauty, charm, and firmness of fetlock. A lot of palaver, though, for something that really ought to have been issue number one for the team changing the cms. Hey, let&#8217;s rebuild the website in a way that completely breaks it! Top plan! Trebles all round!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mulqueeny</title>
		<link>http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/#comment-77</link>
		<dc:creator>Mulqueeny</dc:creator>
		<pubDate>Thu, 13 Mar 2008 09:46:31 +0000</pubDate>
		<guid isPermaLink="false">http://mulqueeny.wordpress.com/?p=24#comment-77</guid>
		<description>Yes indeed it will - the comms would be more about reassurance - i.e. don&#039;t panic, we have changed loads of stuff but we are still looking after you - you will still get to the information you need. 

With the reprinting, there are going to be url changes - therefore printed matter will need to reflect this, but yes, old urls will work.</description>
		<content:encoded><![CDATA[<p>Yes indeed it will &#8211; the comms would be more about reassurance &#8211; i.e. don&#8217;t panic, we have changed loads of stuff but we are still looking after you &#8211; you will still get to the information you need. </p>
<p>With the reprinting, there are going to be url changes &#8211; therefore printed matter will need to reflect this, but yes, old urls will work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://mulqueeny.wordpress.com/2008/03/13/customer-retention-update-3/#comment-76</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Thu, 13 Mar 2008 08:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://mulqueeny.wordpress.com/?p=24#comment-76</guid>
		<description>If you&#039;re redirecting things anyway, why does there need to be any comms? I mean, it&#039;ll just work: why does anyone need to know that you&#039;re redirecting links?

The same with reprinting things. You don&#039;t need to. The redirects take care of everything. And the success rate is easy too. It&#039;s just how many 404 errors you get. And you can fix those as you go, too, so after a month or so you&#039;ll have 100% coverage.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re redirecting things anyway, why does there need to be any comms? I mean, it&#8217;ll just work: why does anyone need to know that you&#8217;re redirecting links?</p>
<p>The same with reprinting things. You don&#8217;t need to. The redirects take care of everything. And the success rate is easy too. It&#8217;s just how many 404 errors you get. And you can fix those as you go, too, so after a month or so you&#8217;ll have 100% coverage.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
