<?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: Your Customers Aren’t Telling You Everything. Here’s What To Do About It.	</title>
	<atom:link href="https://www.groovehq.com/blog/outbound-customer-service/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/outbound-customer-service</link>
	<description></description>
	<lastBuildDate>Thu, 27 Sep 2018 17:41:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.1</generator>
	<item>
		<title>
		By: Jeff Toister		</title>
		<link>https://www.groovehq.com/blog/outbound-customer-service#comment-2626</link>

		<dc:creator><![CDATA[Jeff Toister]]></dc:creator>
		<pubDate>Fri, 27 Feb 2015 00:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3418#comment-2626</guid>

					<description><![CDATA[I enjoyed your post, particularly the coining of the phrase, &quot;customer issues in the wild.&quot; I&#039;d also suggest many of these issues aren&#039;t all that wild. They just don&#039;t make it to management.

Your restaurant story is a great example. Many of the issues you experienced that night were well-known to your server. I bet your server didn&#039;t do anything with that information. 

Why? They may not have resonated as an official complaint. Or, they feared being implicated in poor service. Perhaps they were just too focused on a busy night to care.

I also like your suggestions on monitoring social media. My own research indicates that Twitter is generally a second channel for complaints.

http://www.toistersolutions.com/blog/2014/10/7/what-angry-customers-tweet-about]]></description>
			<content:encoded><![CDATA[<p>I enjoyed your post, particularly the coining of the phrase, &#8220;customer issues in the wild.&#8221; I&#8217;d also suggest many of these issues aren&#8217;t all that wild. They just don&#8217;t make it to management.</p>
<p>Your restaurant story is a great example. Many of the issues you experienced that night were well-known to your server. I bet your server didn&#8217;t do anything with that information. </p>
<p>Why? They may not have resonated as an official complaint. Or, they feared being implicated in poor service. Perhaps they were just too focused on a busy night to care.</p>
<p>I also like your suggestions on monitoring social media. My own research indicates that Twitter is generally a second channel for complaints.</p>
<p><a href="http://www.toistersolutions.com/blog/2014/10/7/what-angry-customers-tweet-about" rel="nofollow ugc">http://www.toistersolutions.com/blog/2014/10/7/what-angry-customers-tweet-about</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Theresa Ferries		</title>
		<link>https://www.groovehq.com/blog/outbound-customer-service#comment-2651</link>

		<dc:creator><![CDATA[Theresa Ferries]]></dc:creator>
		<pubDate>Tue, 24 Feb 2015 17:08:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3418#comment-2651</guid>

					<description><![CDATA[At my job, we focus on asking &quot;Discovery Questions.&quot; These are open ended questions that help both my customer and myself find the best solution for their current need. 


However, I find those very same &quot;Discovery Questions&quot; work even better when the customer has a concern or problem with an order. It tells the customer that I (and the company) am listening to them, that I WANT to find a solution, and that I want to prevent the problem from happening to them (or any other customer) ever again. Of course the most important is for them to know that I am actively listening to their concern. 


And of course when there is a problem, it is ever so important that I accept the responsibility on behalf of the company, since at that time I am the face/voice of the company. That sincere apology makes it so much easier to get the needed information with those &quot;Discovery Questions.&quot;]]></description>
			<content:encoded><![CDATA[<p>At my job, we focus on asking &#8220;Discovery Questions.&#8221; These are open ended questions that help both my customer and myself find the best solution for their current need. </p>
<p>However, I find those very same &#8220;Discovery Questions&#8221; work even better when the customer has a concern or problem with an order. It tells the customer that I (and the company) am listening to them, that I WANT to find a solution, and that I want to prevent the problem from happening to them (or any other customer) ever again. Of course the most important is for them to know that I am actively listening to their concern. </p>
<p>And of course when there is a problem, it is ever so important that I accept the responsibility on behalf of the company, since at that time I am the face/voice of the company. That sincere apology makes it so much easier to get the needed information with those &#8220;Discovery Questions.&#8221;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dan		</title>
		<link>https://www.groovehq.com/blog/outbound-customer-service#comment-2653</link>

		<dc:creator><![CDATA[Dan]]></dc:creator>
		<pubDate>Tue, 24 Feb 2015 17:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3418#comment-2653</guid>

					<description><![CDATA[It&#039;s a bit orthogonal to your point, but one thing we&#039;ve done at Improvely is add a feedback form to the bottom of every single page of the app. It&#039;s at least 10X&#039;d the number of messages we get, including from people who are frustrated/upset about something and want to vent. They&#039;ve got the contact form right there and do it, which also means they vent on our site instead of somewhere else, and we can get them helped right away. 

E.g.: http://demo.improvely.com/reports/mywebshop/person?id=nlt%40fnzpfpplf.nft



i do monitor the brand on other sites too of course, and my tool of choice for that is Mention.com.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s a bit orthogonal to your point, but one thing we&#8217;ve done at Improvely is add a feedback form to the bottom of every single page of the app. It&#8217;s at least 10X&#8217;d the number of messages we get, including from people who are frustrated/upset about something and want to vent. They&#8217;ve got the contact form right there and do it, which also means they vent on our site instead of somewhere else, and we can get them helped right away. </p>
<p>E.g.: <a href="http://demo.improvely.com/reports/mywebshop/person?id=nlt%40fnzpfpplf.nft" rel="nofollow ugc">http://demo.improvely.com/reports/mywebshop/person?id=nlt%40fnzpfpplf.nft</a></p>
<p>i do monitor the brand on other sites too of course, and my tool of choice for that is Mention.com.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dale Harrison		</title>
		<link>https://www.groovehq.com/blog/outbound-customer-service#comment-2654</link>

		<dc:creator><![CDATA[Dale Harrison]]></dc:creator>
		<pubDate>Tue, 24 Feb 2015 16:02:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3418#comment-2654</guid>

					<description><![CDATA[A number of years ago I did a restructuring and turnaround on a company with a terrible service history and a significant rate of account loss.


To try and get a handle on things, I pulled several hundred lost accounts and we contacted them directly to learn why they left. I then cross-correlated this with the historical customer complaint records.


Result: 1:50 


For every 50 customers who quit us for a competitor...only one ever lodged a recorded complaint with our customer service group.


Most complaints ultimately point to systemic issues in the organization...and are always just the tip of the iceberg waiting to sink you...]]></description>
			<content:encoded><![CDATA[<p>A number of years ago I did a restructuring and turnaround on a company with a terrible service history and a significant rate of account loss.</p>
<p>To try and get a handle on things, I pulled several hundred lost accounts and we contacted them directly to learn why they left. I then cross-correlated this with the historical customer complaint records.</p>
<p>Result: 1:50 </p>
<p>For every 50 customers who quit us for a competitor&#8230;only one ever lodged a recorded complaint with our customer service group.</p>
<p>Most complaints ultimately point to systemic issues in the organization&#8230;and are always just the tip of the iceberg waiting to sink you&#8230;</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: levberlin		</title>
		<link>https://www.groovehq.com/blog/outbound-customer-service#comment-2655</link>

		<dc:creator><![CDATA[levberlin]]></dc:creator>
		<pubDate>Tue, 24 Feb 2015 15:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3418#comment-2655</guid>

					<description><![CDATA[Another approach is to proactively ask users how they feel about the product while they&#039;re using it. Kind of like the net promoter score with feedback. Basically a popup with -1, 0, +1, and comment field to explain why they felt this way. Much more likely to get feedback that way (positive or negative) and bug reports than the user going out of their way to email/call/chat you.]]></description>
			<content:encoded><![CDATA[<p>Another approach is to proactively ask users how they feel about the product while they&#8217;re using it. Kind of like the net promoter score with feedback. Basically a popup with -1, 0, +1, and comment field to explain why they felt this way. Much more likely to get feedback that way (positive or negative) and bug reports than the user going out of their way to email/call/chat you.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
