<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Micro Biz Journal &#187; Customer Support</title>
	<atom:link href="http://www.microbizjournal.com/category/operations/customer-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.microbizjournal.com</link>
	<description>Lessons Learned in My Journey with a Micro Business</description>
	<lastBuildDate>Fri, 01 Apr 2011 16:47:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>It Pays to Bare All</title>
		<link>http://www.microbizjournal.com/it-pays-to-bare-all/</link>
		<comments>http://www.microbizjournal.com/it-pays-to-bare-all/#comments</comments>
		<pubDate>Tue, 23 Sep 2008 12:13:09 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Customer Support]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://www.microbizjournal.com/?p=216</guid>
		<description><![CDATA[I had a frustrating week on the technology front. We use a product that automates many of our marketing activities. For example, it automatically sends out a series of sales tips to customers and at the end offers them a membership in a on-going sales coaching program. For the last couple of weeks, we couldn&#8217;t [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-thumbnail wp-image-217" title="Transparency" src="http://www.microbizjournal.com/wp-content/uploads/2008/09/transparency-135x150.jpg" alt="" width="135" height="150" hspace="10" vspace="10"/>I had a frustrating week on the technology front. We use a product that automates many of our marketing activities. For example, it automatically sends out a series of sales tips to customers and at the end offers them a membership in a on-going sales coaching program.</p>
<p>For the last couple of weeks, we couldn&#8217;t figure out why no one was opting to join the coaching program. After all, it&#8217;s a tremedous value that delivers a host of resources to make an immediate and lasting impact to your sales. Just click here to&#8230; Sorry &#8211; I got carried away&#8230;</p>
<p>We were confronted with the ugly prospect that we are marketing losers, unable to do a basic upsell. Faced with this, I took the next logical step: find someone else to blame. Luckily I did!</p>
<p>As it turns out, our marketing software had broken. They had released a new version and done a crappy job of testing. So for two weeks, when our prospects finished their run of sales tips, they were not getting their upsell pitch. They weren&#8217;t getting as much as a <em>Thank you and come again</em>&#8230;</p>
<p>So I called my friends at Infusion (the software company) and asked <em>Wat Up?!?!?</em>  The response: <em>Yeah, we know about that</em>. I was dumb-founded. I was losing money and they didn&#8217;t let me know? The excuse: <em>We weren&#8217;t sure how many users were impacted</em>.</p>
<p>I can forgive software bugs. I have been around the industry long enough to know that s**t happens. What I can&#8217;t forgive is not being notified. If I had been notified I could have done manual follow. I would have been grumpy but I would still have business continuity.</p>
<p>When companies hold back this information, it is because they are being huge wimps. They don&#8217;t want to get beat up and deal with complaints. It&#8217;s tough &#8211; I&#8217;ve been there. I&#8217;ve been physically threatened by customers not happy with the fact there is a bug and the resolution time frame. But that is life in software. Deal with it.</p>
<p>You want to make customers really mad &#8211; hide the truth from them. Then when they find out (they always do) and realize the damage done, it is medieval time.</p>
<p>Here was my response to Infusion:</p>
<blockquote><p><em>&#8230;You have to remember that most of us rely on this for our livelihood. I can tell you first hand when there is a bug in Infusion where a marketing campaign doesn&#8217;t run or a credit card doesn&#8217;t get processed, my pay goes down. Nothing ignites passions like one&#8217;s wallet.</em></p>
<p><em>And to be frank, most business-to-business software companies do a far better job at transparency with known issues. I cannot count the number of times that I&#8217;ve called Infusion support with an critical issue and been told that, &#8220;oh yeah &#8211; we know about that.&#8221; Yet at the same time on this forum, there is no mention of the bug under &#8220;known issues.&#8221;</em></p>
<p><em>Top this up with the frustration of a new application that has broken many, many things. While I question the prioritization of a new interface versus stability and features, regardless the new app appears to have been released prematurely.</em></p>
<p><em>What I expect from Infusion is a table, updated daily, with the following:</em></p>
<ol type="1">
<li><em>A list of every open Pri 1 and 2 issue. No filtering just because the number of users impacted isn&#8217;t known.<br />
</em></li>
<li><em>A statement about who is impacted by situation. For example: &#8220;users who perform this type of operation&#8230;&#8221;<br />
</em></li>
<li><em>Any known workaround. Even if all that can be done is check that one has the problem and do some painfully manual workaround.</em></li>
</ol>
<p><em>I have been around the software business for a long time. Let me assure you, you will lose more customers by hiding serious issues than by coming clean.</em></p>
<p><em>Chris Voice</em></p></blockquote>
<p>How about you? Are you honest with your customers? Even when you look bad?</p>
<p>C.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.microbizjournal.com/it-pays-to-bare-all/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

