<?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 To Reduce The Number of Customer Service Emails You Get	</title>
	<atom:link href="https://www.groovehq.com/blog/reduce-customer-service-emails/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/reduce-customer-service-emails</link>
	<description></description>
	<lastBuildDate>Mon, 01 Oct 2018 09:26:33 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>
		By: SnapEngage		</title>
		<link>https://www.groovehq.com/blog/reduce-customer-service-emails#comment-4955</link>

		<dc:creator><![CDATA[SnapEngage]]></dc:creator>
		<pubDate>Thu, 13 Aug 2015 16:00:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3491#comment-4955</guid>

					<description><![CDATA[Thanks for the mention Len! We&#039;re all about cutting down on inbox clutter. One helpful tool in the live chat arsenal that may address some of the concerns that Brady mentioned is a pre-chat form that displays FAQ&#039;s to visitors prior to starting a chat with an agent. This can help address commonly asked questions without increasing agent load. However, we also agree with Yakov that in order for a business to be successful, customer experience must trump energy drain, and focusing on qualified website traffic will naturally help reduce unnecessary chat load.]]></description>
			<content:encoded><![CDATA[<p>Thanks for the mention Len! We&#8217;re all about cutting down on inbox clutter. One helpful tool in the live chat arsenal that may address some of the concerns that Brady mentioned is a pre-chat form that displays FAQ&#8217;s to visitors prior to starting a chat with an agent. This can help address commonly asked questions without increasing agent load. However, we also agree with Yakov that in order for a business to be successful, customer experience must trump energy drain, and focusing on qualified website traffic will naturally help reduce unnecessary chat load.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brady Dowling		</title>
		<link>https://www.groovehq.com/blog/reduce-customer-service-emails#comment-4977</link>

		<dc:creator><![CDATA[Brady Dowling]]></dc:creator>
		<pubDate>Tue, 11 Aug 2015 16:03:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3491#comment-4977</guid>

					<description><![CDATA[I can&#039;t exactly agree on the chat side. While it may be effective and valuable for users and the company overall, it certainly doesn&#039;t reduce load.


Technically, yes, it reduces &quot;emails&quot; but you&#039;re going to get 4x as many requests via chat than you would via email. Many of them will be people saying &quot;Sup, is this a human or a bot?&quot; We&#039;ve all said this at one point or another but we forget that people even do this until you see it 20 times in a row in your inbox :)


Aside from that, good points. I think simple audits/reviews of the requests that come in is a very effective way of combatting future requests. You can take a step back and say, &quot;Why did this person reach out? What can I do to prevent this next time?&quot;]]></description>
			<content:encoded><![CDATA[<p>I can&#8217;t exactly agree on the chat side. While it may be effective and valuable for users and the company overall, it certainly doesn&#8217;t reduce load.</p>
<p>Technically, yes, it reduces &#8220;emails&#8221; but you&#8217;re going to get 4x as many requests via chat than you would via email. Many of them will be people saying &#8220;Sup, is this a human or a bot?&#8221; We&#8217;ve all said this at one point or another but we forget that people even do this until you see it 20 times in a row in your inbox 🙂</p>
<p>Aside from that, good points. I think simple audits/reviews of the requests that come in is a very effective way of combatting future requests. You can take a step back and say, &#8220;Why did this person reach out? What can I do to prevent this next time?&#8221;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Chris Dunne		</title>
		<link>https://www.groovehq.com/blog/reduce-customer-service-emails#comment-4978</link>

		<dc:creator><![CDATA[Chris Dunne]]></dc:creator>
		<pubDate>Tue, 11 Aug 2015 15:46:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3491#comment-4978</guid>

					<description><![CDATA[Nice blog Len.
Chris, RepricerExpress]]></description>
			<content:encoded><![CDATA[<p>Nice blog Len.<br />
Chris, RepricerExpress</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bill Dettering		</title>
		<link>https://www.groovehq.com/blog/reduce-customer-service-emails#comment-4980</link>

		<dc:creator><![CDATA[Bill Dettering]]></dc:creator>
		<pubDate>Tue, 11 Aug 2015 15:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3491#comment-4980</guid>

					<description><![CDATA[Great article. Adding... for our (Applian&#039;s) technical products that need troubleshooters, we&#039;re using Zingtree interactive decision trees to help customers self-solve. They are easy for the customers to use, and can break down multiple steps into bite-sized chunks thaat are easier for customers to follow.]]></description>
			<content:encoded><![CDATA[<p>Great article. Adding&#8230; for our (Applian&#8217;s) technical products that need troubleshooters, we&#8217;re using Zingtree interactive decision trees to help customers self-solve. They are easy for the customers to use, and can break down multiple steps into bite-sized chunks thaat are easier for customers to follow.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
