<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for bode</title><link>http://disqus.com/by/bode/</link><description></description><atom:link href="http://disqus.com/bode/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 16 Jul 2009 06:24:04 -0000</lastBuildDate><item><title>Re: What is your Anti-Churn Strategy?</title><link>http://www.ubigen.org/?p=200#comment-12735826</link><description>&lt;p&gt;Interesting topic and one I did some academic work on recently so it's fresh in my mind.&lt;br&gt;Though an Anti-churn strategy may be required, I would agree with other comments that the companies strategy should be focused on winning and retaining customers. As  you mentioned, if a customer has left after a series of bad experiences, it would be much harder to win them back than to win a new customer. &lt;br&gt;Feed back from clients is something a lot of companies (especially in emerging markets) underestimate. You hear it a lot, but i cannot stress how important it is to *regularly* listen to customers. Companies must consistently ask them the right questions, collate their answers, measure their "happiness" or otherwise with the product/service and have strategies for analysing this data and most importantly acting on it. Companies must make sure the customers know why they are carrying out this activity and communicate their findings with them along with what they intend to do it. This may seem like a lot of work, but there is a lot of research out there that shows that the companies that do this will not only retain their clients, they will bring in more business (word of mouth etc). I would argue that adding a robust customer retention programme as part of the company strategy is more important than an anti-churn programme.&lt;/p&gt;&lt;p&gt;cheers,&lt;br&gt;Bode&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bode</dc:creator><pubDate>Thu, 16 Jul 2009 06:24:04 -0000</pubDate></item></channel></rss>