<?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>berbs.us &#187; Customer Service</title>
	<atom:link href="http://berbs.us/category/customer-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://berbs.us</link>
	<description>a blog by jason berberich</description>
	<lastBuildDate>Fri, 30 Jul 2010 20:00:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Finally — Resolution with Symantec</title>
		<link>http://berbs.us/2007/02/finally-resolution-with-symantec/</link>
		<comments>http://berbs.us/2007/02/finally-resolution-with-symantec/#comments</comments>
		<pubDate>Tue, 06 Feb 2007 21:50:32 +0000</pubDate>
		<dc:creator>Jason Berberich</dc:creator>
				<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[Business]]></category>

		<guid isPermaLink="false">http://labs.berbs.us/2007/02/finally-resolution-with-symantec/</guid>
		<description><![CDATA[I'm happy to say that my two month saga with Symantec customer service is finally over. I heard back from Ben this morning, who assured me people were looking into my issue. In the mean time though, I took my concern up a few notches by emailing a few Symantec executives. Within the last 30 [...]


Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/symantec-mysupport-follow-up/' rel='bookmark' title='Permanent Link: Symantec MySupport Follow-up'>Symantec MySupport Follow-up</a></li>
<li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>I’m happy to say that my <a href="http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/" >two month saga</a> with Symantec customer service is finally over. I heard back from Ben this morning, who assured me people were looking into my issue. In the mean time though, I took my concern up a few notches by emailing a few Symantec executives.</p>

<p>Within the last 30 minutes, I received a call from a Symantec employee named Andrew who was really helpful. He had spent over an hour researching my problem, to discover that my issue was a very weird circumstance that was somehow was being created internally in their software.</p>

<p>In any case, while Andrew wasn’t able to fix the original problem, he did offer a temporary fix that will let me download what I need. I want to thank both him and Ben for all of the help they’ve given me.</p>

<p>My last word on this topic is just this: It never had to be this way. Throughout this ordeal, I had no way of knowing if my case had dropped off the face of the Earth, or if a Symantec employee was working on it. Good communication is <em>everything</em> in these types of situations. If I don’t hear anything, I’m left to assume nothing is happening, if that’s the intent or not.</p>

<p><strong>Postscript:</strong> In case anyone is wondering, Symantec employees were aware that I was blogging about this situation since my <a href="http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/" >first post</a> about it on January 12th. They never once asked that I add to or remove my comments in any way.</p>


<p>Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/symantec-mysupport-follow-up/' rel='bookmark' title='Permanent Link: Symantec MySupport Follow-up'>Symantec MySupport Follow-up</a></li>
<li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://berbs.us/2007/02/finally-resolution-with-symantec/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Current Score with Symantec Customer Support</title>
		<link>http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/</link>
		<comments>http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/#comments</comments>
		<pubDate>Wed, 31 Jan 2007 18:54:44 +0000</pubDate>
		<dc:creator>Jason Berberich</dc:creator>
				<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://labs.berbs.us/2007/01/the-current-score-with-symantec-customer-support/</guid>
		<description><![CDATA[I've written about my terrible customer service experience(s) with Symantec a couple of times already. I was hoping my previous post on the subject would be the last, but this thing is still unresolved. Here's a time line for you: 11/28/2006 - I received a "Version Upgrade Notification" email from Symantec, including a PDF document [...]


Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/' rel='bookmark' title='Permanent Link: Here’s an Idea: Customer Service Callbacks'>Here’s an Idea: Customer Service Callbacks</a></li>
<li><a href='http://berbs.us/2007/02/finally-resolution-with-symantec/' rel='bookmark' title='Permanent Link: Finally — Resolution with Symantec'>Finally — Resolution with Symantec</a></li>
<li><a href='http://berbs.us/2007/01/symantec-mysupport-follow-up/' rel='bookmark' title='Permanent Link: Symantec MySupport Follow-up'>Symantec MySupport Follow-up</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
<li><a href='http://berbs.us/2007/10/amazons-customer-culture/' rel='bookmark' title='Permanent Link: Amazon’s Customer Culture'>Amazon’s Customer Culture</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>I’ve written about my <strong>terrible</strong> customer service experience(s) with Symantec a <a href="http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/" >couple</a> of <a href="http://berbs.us/2007/01/symantec-mysupport-follow-up/" >times</a> already. I was hoping my previous post on the subject would be the last, but this thing is <em>still</em> unresolved. Here’s a time line for you:</p>

<ul>
<li>11/28/2006 — I received a “Version Upgrade Notification” email from Symantec, including a PDF document a URL and Notification ID to be used to retrieve the new release of Backup Exec 11d Windows. I log into their licensing portal and input my information, only to get an error message saying <em>“Your request cannot be processed. Please contact Symantec Customer Care”</em>.</li>
<li>Mid-December, 2006 — Chalking the previous experience up to a temporary glitch, I try logging in again to download the software update. No luck — I get the same error message.</li>
<li>12/22/2006 — I try logging in again and inputting my information, but get the same problem. I eventually find and call the Symantec “Customer Care” phone number (800.721.3934). The message says that hold times are in excess of 45 minutes due to high call volume regarding the “newly introduced Symantec Licensing portal”. I wait on hold for about 15 minutes before hanging up and going to Symantec MySupport to log an issue through the company’s online support system. This is where I have the experience I partially documented on a <a href="http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/" >previous post</a>.</li>
<li>01/12/2007 — Fed up with Symantec MySupport, I decide to wait on hold with “Customer Care” (800.721.3934). After waiting <strong>1 1/2 hours</strong> to speak with a real person, I talk to a rep named Cordella. She takes a look at the account and says a new notification number needs to be issued to me, which will be sent out within the next week.</li>
<li>01/16/2007 — I receive an email from a Symantec employee named Ben regarding my blog post about the MySupport site. We talk on the phone for a few minutes regarding that experience, and he says to keep him in the loop regarding my support issue.</li>
<li>01/19/2007 — One week after speaking to Cordella, I still haven’t received my new notification number. I email Ben back, and he submits my issue into Symantec’s internal customer escalation system.</li>
<li>01/25/2007 — No word from Symantec support yet. I email Ben to check in again, and he quickly checks on the status of my request. Several minutes later, I receive a phone call from a Symantec employee named Mark, who is in charge of the internal customer escalation system. He says he’s forwarding my information to a manager in the licensing department and that I should expect a call from them shortly after he does so.</li>
<li>1/30/2007 — Still no word from Mark or the licensing department manager. I bug Ben again, and he forwards my email to one of the people involved with the customer escalation program.</li>
</ul>

<p>So, that’s where the situation sits right now. Even Symantec’s internal problem escalation system isn’t bringing this thing to a resolution. If that’s the case, someone going through the normal support channels has practically no chance of getting their problem fixed.</p>

<p>I have to say that I really like Ben and think he’s genuinely interested in helping me and others out. He’s been extremely accessible and prompt whenever I send him an email. It’s the Symantec <em>system</em> that’s a problem. It squashes any chance of guys like him making a real difference. <strong>That’s</strong> what’s wrong with big businesses.</p>


<p>Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/' rel='bookmark' title='Permanent Link: Here’s an Idea: Customer Service Callbacks'>Here’s an Idea: Customer Service Callbacks</a></li>
<li><a href='http://berbs.us/2007/02/finally-resolution-with-symantec/' rel='bookmark' title='Permanent Link: Finally — Resolution with Symantec'>Finally — Resolution with Symantec</a></li>
<li><a href='http://berbs.us/2007/01/symantec-mysupport-follow-up/' rel='bookmark' title='Permanent Link: Symantec MySupport Follow-up'>Symantec MySupport Follow-up</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
<li><a href='http://berbs.us/2007/10/amazons-customer-culture/' rel='bookmark' title='Permanent Link: Amazon’s Customer Culture'>Amazon’s Customer Culture</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Symantec MySupport Follow-up</title>
		<link>http://berbs.us/2007/01/symantec-mysupport-follow-up/</link>
		<comments>http://berbs.us/2007/01/symantec-mysupport-follow-up/#comments</comments>
		<pubDate>Wed, 17 Jan 2007 05:38:09 +0000</pubDate>
		<dc:creator>Jason Berberich</dc:creator>
				<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Usability]]></category>
		<category><![CDATA[Web Apps]]></category>
		<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://labs.berbs.us/2007/01/symantec-mysupport-follow-up/</guid>
		<description><![CDATA[When I wrote about my frustration with the Symantec MySupport site last Friday, it was mainly a way for me to vent. I wasn't expecting anything to come of it, which was why I was extremely surprised to find an email in my inbox this afternoon from a Symantec employee named Ben. Ben said someone [...]


Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
<li><a href='http://berbs.us/2007/02/finally-resolution-with-symantec/' rel='bookmark' title='Permanent Link: Finally — Resolution with Symantec'>Finally — Resolution with Symantec</a></li>
<li><a href='http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/' rel='bookmark' title='Permanent Link: Here’s an Idea: Customer Service Callbacks'>Here’s an Idea: Customer Service Callbacks</a></li>
<li><a href='http://berbs.us/2007/05/facebook-loves-developers-and-i-love-facebook/' rel='bookmark' title='Permanent Link: Facebook Loves Developers, and I Love Facebook'>Facebook Loves Developers, and I Love Facebook</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>When I wrote about <a href="http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/" >my frustration with the Symantec MySupport</a> site last Friday, it was mainly a way for me to vent. I wasn’t expecting anything to come of it, which was why I was extremely surprised to find an email in my inbox this afternoon from a Symantec employee named Ben.</p>

<p>Ben said someone had forwarded him a link to my critique of MySupport and asked if I’d be willing to talk about my experience. Several hours later, he called me up and we chatted for a while about it. I learned about some 3rd party software integration they’re going through along with a few other things. More than anything else though, I found out that Ben was genuinely interested in hearing my opinion and making the MySupport experience better.</p>

<p>Ben also reminded me that there are still some good people who care working in huge corporations. It’s too bad the systems of this companies usually keep them on so tight a leash they can’t make a difference.</p>

<p>So, thanks for contacting me Ben. You gave me a little more hope in corporations. It’s good to know someone is actually listening.</p>


<p>Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/' rel='bookmark' title='Permanent Link: Bad Web Design #1: Symantec MySupport'>Bad Web Design #1: Symantec MySupport</a></li>
<li><a href='http://berbs.us/2007/02/finally-resolution-with-symantec/' rel='bookmark' title='Permanent Link: Finally — Resolution with Symantec'>Finally — Resolution with Symantec</a></li>
<li><a href='http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/' rel='bookmark' title='Permanent Link: Here’s an Idea: Customer Service Callbacks'>Here’s an Idea: Customer Service Callbacks</a></li>
<li><a href='http://berbs.us/2007/05/facebook-loves-developers-and-i-love-facebook/' rel='bookmark' title='Permanent Link: Facebook Loves Developers, and I Love Facebook'>Facebook Loves Developers, and I Love Facebook</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://berbs.us/2007/01/symantec-mysupport-follow-up/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Here’s an Idea: Customer Service Callbacks</title>
		<link>http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/</link>
		<comments>http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/#comments</comments>
		<pubDate>Fri, 12 Jan 2007 20:21:47 +0000</pubDate>
		<dc:creator>Jason Berberich</dc:creator>
				<category><![CDATA[Customer Service]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Ideas]]></category>
		<category><![CDATA[Insights]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://labs.berbs.us/2007/01/heres-an-idea-customer-service-callbacks/</guid>
		<description><![CDATA[An idea popped into my head after my Symantec "customer service" phone ordeal earlier today. Instead of making customers wait in a call queue for minutes (or hours) on end, why not let them wait for a short time - maybe five minutes. If they still haven't been passed to a real human being by [...]


Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2005/03/great-customer-service/' rel='bookmark' title='Permanent Link: Great Customer Service'>Great Customer Service</a></li>
<li><a href='http://berbs.us/2006/10/the-waiting-game/' rel='bookmark' title='Permanent Link: The Waiting Game'>The Waiting Game</a></li>
<li><a href='http://berbs.us/2007/10/amazons-customer-culture/' rel='bookmark' title='Permanent Link: Amazon’s Customer Culture'>Amazon’s Customer Culture</a></li>
<li><a href='http://berbs.us/2007/09/something-id-like-to-see-a-rest-web-service-for-my-phone/' rel='bookmark' title='Permanent Link: Something I’d Like to See: A REST Web Service for My Phone'>Something I’d Like to See: A REST Web Service for My Phone</a></li>
</ol>]]></description>
			<content:encoded><![CDATA[<p>An idea popped into my head after my <a href="http://berbs.us/2007/01/bad-web-design-1-symantec-mysupport/" >Symantec “customer service” phone ordeal</a> earlier today. Instead of making customers wait in a call queue for minutes (or hours) on end, why not let them wait for a short time — maybe five minutes. If they still haven’t been passed to a real human being by that point, just have them punch in their phone number on the keypad. Then, when a support rep is finally available, have their system automatically dial up the customer’s number.</p>

<p>I think this would do a couple of things. First, it would remove the frustration that grows with every minute you’re on hold. That in itself would make the support calls more productive for both parties. Second, it shows a lot of respect for the customer. Instead of treating them like cattle by keeping them on hold, they get to go back to their regular job until they get the call.</p>

<p>This idea can’t be unique — some company out there <em>has to be</em> doing something like this already. The question to ask then, is <em>why aren’t most companies doing it?</em></p>

<p>Sadly, I believe the answer is that most big companies just don’t care about their customers. Their “customers” are a mass of faceless and nameless people that are interchangeable and replaceable. Usually, you get lots of attention from sales while they “court” you, but if you ever decide to sign an agreement with them, you’re screwed. Support is an afterthought, and you’re looked at as an expense instead of being treated the way a customer really should. That’s why phone support is so often outsourced to call centers in India with employees who have no investment in a company, but read from a script instead.</p>

<p>That’s why I feel small businesses can really exploit this current state. They’re filled with people who still care, and there’s a very good chance the support person is also the sales person and the person providing the product or service. They’re also a thousand times faster than corporations, and can change their sales pitch or the product itself the day they learn of an issue from a customer, instead of having to go through layer after layer of bureaucracy.</p>

<p>Like I’ve said before, doing the right thing usually isn’t any harder than doing the “easy” thing. It means thinking a little differently and focusing your energy in a different place. But it also means <em>caring</em> — something a corporation is incapable of doing.</p>


<p>Possibly related posts:<ol><li><a href='http://berbs.us/2007/01/the-current-score-with-symantec-customer-support/' rel='bookmark' title='Permanent Link: The Current Score with Symantec Customer Support'>The Current Score with Symantec Customer Support</a></li>
<li><a href='http://berbs.us/2005/03/great-customer-service/' rel='bookmark' title='Permanent Link: Great Customer Service'>Great Customer Service</a></li>
<li><a href='http://berbs.us/2006/10/the-waiting-game/' rel='bookmark' title='Permanent Link: The Waiting Game'>The Waiting Game</a></li>
<li><a href='http://berbs.us/2007/10/amazons-customer-culture/' rel='bookmark' title='Permanent Link: Amazon’s Customer Culture'>Amazon’s Customer Culture</a></li>
<li><a href='http://berbs.us/2007/09/something-id-like-to-see-a-rest-web-service-for-my-phone/' rel='bookmark' title='Permanent Link: Something I’d Like to See: A REST Web Service for My Phone'>Something I’d Like to See: A REST Web Service for My Phone</a></li>
</ol></p>]]></content:encoded>
			<wfw:commentRss>http://berbs.us/2007/01/heres-an-idea-customer-service-callbacks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
