<?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: Dealing with an unexpected rush.</title>
	<atom:link href="http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/</link>
	<description>The blog about customer service and the customer service experience.</description>
	<lastBuildDate>Fri, 10 Feb 2012 08:35:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Service Untitled</title>
		<link>http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/comment-page-1/#comment-133202</link>
		<dc:creator>Service Untitled</dc:creator>
		<pubDate>Thu, 02 Aug 2007 22:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/#comment-133202</guid>
		<description>Ben,

Well it is definitely a good idea. I can see how it would certainly increase efficiency.</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>Well it is definitely a good idea. I can see how it would certainly increase efficiency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hubbard</title>
		<link>http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/comment-page-1/#comment-133103</link>
		<dc:creator>Ben Hubbard</dc:creator>
		<pubDate>Thu, 02 Aug 2007 21:18:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/#comment-133103</guid>
		<description>Hello Doug,

Webmail.us has one… it&#039;s relatively new and evolved.  We basically realized that a point of contact was the right way to go, but someone has to inform account managers, the technical support team, and of course others of interest in the company.  

Besides streamlining communication, another big reason was to help the engineers.  No matter how understanding team members are, being asked once every ten minutes for an update by ten different people is basically an interruption every sixty seconds… and that adds negative pressure.  During an issue, &quot;I think I found the issue&quot; can be misunderstood by someone and three generations down the line that message becomes &quot;it&#039;s fixed&quot; even when it might not be.  To prevent this, one contact who knows the vital information to get and what, if any, confirmation questions to ask.

Ben</description>
		<content:encoded><![CDATA[<p>Hello Doug,</p>
<p>Webmail.us has one… it&#8217;s relatively new and evolved.  We basically realized that a point of contact was the right way to go, but someone has to inform account managers, the technical support team, and of course others of interest in the company.  </p>
<p>Besides streamlining communication, another big reason was to help the engineers.  No matter how understanding team members are, being asked once every ten minutes for an update by ten different people is basically an interruption every sixty seconds… and that adds negative pressure.  During an issue, &#8220;I think I found the issue&#8221; can be misunderstood by someone and three generations down the line that message becomes &#8220;it&#8217;s fixed&#8221; even when it might not be.  To prevent this, one contact who knows the vital information to get and what, if any, confirmation questions to ask.</p>
<p>Ben</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Service Untitled</title>
		<link>http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/comment-page-1/#comment-131325</link>
		<dc:creator>Service Untitled</dc:creator>
		<pubDate>Wed, 01 Aug 2007 22:34:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/#comment-131325</guid>
		<description>Ben,

Thanks for your (detailed) comment! Great points.

You only want to put inexperienced (in the customer service sense) on the frontlines when it is your last resort. If you do put them on the frontlines, then you want to have them do simple tasks or tasks that can be done with a process. That way, a lack of customer service experience won&#039;t make as big as a difference . 

I like your idea of cross training employees during quieter times that way they can help out during the busier times if needed. This is a great idea and one that I generally suggest anyways. That way, a bookkeeper could answer a customer question about how to login or a technical support representative could answer the question about how much is due on their most recent invoice. 

I like the idea of a crisis manager. I have never heard of such a role. Do you know of any companies that have a person like that? It would be an interesting subject to talk about. I bet that must be a stressful job as well.

Definitely! Basically every aspect can always be improved upon. It is just knowing how and then actually doing it. Thanks again for your comment.</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>Thanks for your (detailed) comment! Great points.</p>
<p>You only want to put inexperienced (in the customer service sense) on the frontlines when it is your last resort. If you do put them on the frontlines, then you want to have them do simple tasks or tasks that can be done with a process. That way, a lack of customer service experience won&#8217;t make as big as a difference . </p>
<p>I like your idea of cross training employees during quieter times that way they can help out during the busier times if needed. This is a great idea and one that I generally suggest anyways. That way, a bookkeeper could answer a customer question about how to login or a technical support representative could answer the question about how much is due on their most recent invoice. </p>
<p>I like the idea of a crisis manager. I have never heard of such a role. Do you know of any companies that have a person like that? It would be an interesting subject to talk about. I bet that must be a stressful job as well.</p>
<p>Definitely! Basically every aspect can always be improved upon. It is just knowing how and then actually doing it. Thanks again for your comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Hubbard</title>
		<link>http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/comment-page-1/#comment-131303</link>
		<dc:creator>Ben Hubbard</dc:creator>
		<pubDate>Wed, 01 Aug 2007 22:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/dealing-with-an-unexpected-rush/2007/08/01/#comment-131303</guid>
		<description>This is a great post in my opinion, and of all the points, the most prudent I feel is #1, to have formal procedures.  It may be common for many small companies to have a five-alarm type issue before they realize how important such procedures are.

The normal Customer Service reps likely can handle the procedure changes fine, but if you use non-frontline employees like bookkeepers to help, doing things like sorting tickets (if you have a ticketing system that supports that) or helping to just let customers know that you are on it can make a HUGE difference.  I am against putting them in the front line, as they are likely don&#039;t know how to handle angry customers, but there are many other areas they can help.

My suggestion is that people that will be called upon to lend such aid in a rush be exposed to the tool during quieter times.  If you have a ticketing system, show them how to take and sort a ticket, so that when an issue does happen these team members won&#039;t be seeing the ticketing system interface or using the tools for the very first time.

As a support team or company manager, giving the team a pep talk during such issues is huge I think.  Let them know it&#039;s their time to shine.  Like Doug mentioned, a bonus is helpful, but if it&#039;s so busy that they can&#039;t take a lunch break, spring for a pizza delivery for the guys and gals facing the front line.  High moral is vital, and really not that hard to maintain.

Also, especially if you are in the technical field, having a crisis manager is a good move I think.  This person would be responsible for distributing information.  Sometimes the technicians working to solve the problem are the best ones for information.  The last thing they need is to be interrupted every 30 seconds by people asking the same question.  In times of a major issue, the CEO could be clamoring for information, the sales reps getting calls from their customers, account managers, and support managers all ask the same questions.  Having one person responsible for getting frequent updates and making sure they&#039;re given to the right people could make sure the information is consistent, accurate, and that the issue gets resolved sooner.

Great post Doug… and one that I think many readers may benefit from more discussions or posts on.  After all, so many smaller companies use customer service and technical support as a key differentiator between themselves and their customers, and when there is a rush (or service outage) is when customers are most likely to get peeved and forget the previous fast response times and help you were able to offer.  It&#039;s a huge area I think can always be improved upon!</description>
		<content:encoded><![CDATA[<p>This is a great post in my opinion, and of all the points, the most prudent I feel is #1, to have formal procedures.  It may be common for many small companies to have a five-alarm type issue before they realize how important such procedures are.</p>
<p>The normal Customer Service reps likely can handle the procedure changes fine, but if you use non-frontline employees like bookkeepers to help, doing things like sorting tickets (if you have a ticketing system that supports that) or helping to just let customers know that you are on it can make a HUGE difference.  I am against putting them in the front line, as they are likely don&#8217;t know how to handle angry customers, but there are many other areas they can help.</p>
<p>My suggestion is that people that will be called upon to lend such aid in a rush be exposed to the tool during quieter times.  If you have a ticketing system, show them how to take and sort a ticket, so that when an issue does happen these team members won&#8217;t be seeing the ticketing system interface or using the tools for the very first time.</p>
<p>As a support team or company manager, giving the team a pep talk during such issues is huge I think.  Let them know it&#8217;s their time to shine.  Like Doug mentioned, a bonus is helpful, but if it&#8217;s so busy that they can&#8217;t take a lunch break, spring for a pizza delivery for the guys and gals facing the front line.  High moral is vital, and really not that hard to maintain.</p>
<p>Also, especially if you are in the technical field, having a crisis manager is a good move I think.  This person would be responsible for distributing information.  Sometimes the technicians working to solve the problem are the best ones for information.  The last thing they need is to be interrupted every 30 seconds by people asking the same question.  In times of a major issue, the CEO could be clamoring for information, the sales reps getting calls from their customers, account managers, and support managers all ask the same questions.  Having one person responsible for getting frequent updates and making sure they&#8217;re given to the right people could make sure the information is consistent, accurate, and that the issue gets resolved sooner.</p>
<p>Great post Doug… and one that I think many readers may benefit from more discussions or posts on.  After all, so many smaller companies use customer service and technical support as a key differentiator between themselves and their customers, and when there is a rush (or service outage) is when customers are most likely to get peeved and forget the previous fast response times and help you were able to offer.  It&#8217;s a huge area I think can always be improved upon!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

