<?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: How do you deliver world-class service when your support traffic doubles but your staffing doesn&#8217;t?</title>
	<atom:link href="http://blog.parature.com/index.php/customerserviceexperience/how-do-you-deliver-world-class-service-when-your-support-traffic-doubles/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.parature.com/customerserviceexperience/how-do-you-deliver-world-class-service-when-your-support-traffic-doubles/</link>
	<description>The Parature Blog</description>
	<lastBuildDate>Sat, 13 Mar 2010 15:16:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jennifer Henning</title>
		<link>http://blog.parature.com/customerserviceexperience/how-do-you-deliver-world-class-service-when-your-support-traffic-doubles/comment-page-1/#comment-218</link>
		<dc:creator>Jennifer Henning</dc:creator>
		<pubDate>Wed, 17 Jun 2009 18:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=146#comment-218</guid>
		<description>Having Parature has helped with support traffic spikes immensely. When there is an issue affecting multiple customers, we are quickly able to update our support portal, mass email our customers, and mass action any support tickets for the issue. Previously, we would have to wait for the tickets to start rolling in, and handle each one individually- you can imagine the amount of time wasted there and the aggravation our customers faced when not being notified promptly.</description>
		<content:encoded><![CDATA[<p>Having Parature has helped with support traffic spikes immensely. When there is an issue affecting multiple customers, we are quickly able to update our support portal, mass email our customers, and mass action any support tickets for the issue. Previously, we would have to wait for the tickets to start rolling in, and handle each one individually- you can imagine the amount of time wasted there and the aggravation our customers faced when not being notified promptly.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
