<?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 We Grew Our Business by Picking Up Scraps (And Stopped Leaving Customers on the Table)	</title>
	<atom:link href="https://www.groovehq.com/blog/stop-leaving-customers-on-the-table/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/stop-leaving-customers-on-the-table</link>
	<description></description>
	<lastBuildDate>Sat, 16 Feb 2019 11:42:03 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>
		By: Rodion Telpizov		</title>
		<link>https://www.groovehq.com/blog/stop-leaving-customers-on-the-table#comment-1311</link>

		<dc:creator><![CDATA[Rodion Telpizov]]></dc:creator>
		<pubDate>Sun, 23 Oct 2016 17:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2259#comment-1311</guid>

					<description><![CDATA[Wow Alex, that&#039;s really cool ideas and insights. We&#039;ll certainly try the winback emails you suggested. 
Thanks a million!
A quick question. On which emails did you tried these &quot;Second chance subject lines&quot;? 
On your onboarding emails? Or on notifications about new blog post?]]></description>
			<content:encoded><![CDATA[<p>Wow Alex, that&#8217;s really cool ideas and insights. We&#8217;ll certainly try the winback emails you suggested.<br />
Thanks a million!<br />
A quick question. On which emails did you tried these &#8220;Second chance subject lines&#8221;?<br />
On your onboarding emails? Or on notifications about new blog post?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Shawn Blanc		</title>
		<link>https://www.groovehq.com/blog/stop-leaving-customers-on-the-table#comment-1315</link>

		<dc:creator><![CDATA[Shawn Blanc]]></dc:creator>
		<pubDate>Thu, 20 Oct 2016 20:31:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2259#comment-1315</guid>

					<description><![CDATA[Loved this article! 

It hits home for me quite a bit as we are literally in the middle of gutting and re-building our own email sales funnels, and a big part of that is  re-considering what to do with subscribers who don’t convert to customers right away.

Something you mentioned in your post was #5 and collecting insights by asking for new customers to reply to your email.

If you dive into those replies from your customers, you could probably easily identify the top 3-4 “buckets” that people fall into in terms of why it is they are buying Groove. 

Then, if you wanted, you could ask your customers to elect which bucket they fall into as part of the sign-up process.

Then, once you know why it is that they signed up, you could send them a custom onboarding sequence that positions Groove as the solution around that specific bucket they chose when they were signing up. 

The assumed value of all that work would be that your customers would see Groove as a more personal and specific solution for them, and, thus, hopefully would be more likely to stick around longer.

A fantastic resource for this whole “bucket&quot; idea is the book by Ryan Levesque: Ask.

http://www.amazon.com/dp/1939447720/]]></description>
			<content:encoded><![CDATA[<p>Loved this article! </p>
<p>It hits home for me quite a bit as we are literally in the middle of gutting and re-building our own email sales funnels, and a big part of that is  re-considering what to do with subscribers who don’t convert to customers right away.</p>
<p>Something you mentioned in your post was #5 and collecting insights by asking for new customers to reply to your email.</p>
<p>If you dive into those replies from your customers, you could probably easily identify the top 3-4 “buckets” that people fall into in terms of why it is they are buying Groove. </p>
<p>Then, if you wanted, you could ask your customers to elect which bucket they fall into as part of the sign-up process.</p>
<p>Then, once you know why it is that they signed up, you could send them a custom onboarding sequence that positions Groove as the solution around that specific bucket they chose when they were signing up. </p>
<p>The assumed value of all that work would be that your customers would see Groove as a more personal and specific solution for them, and, thus, hopefully would be more likely to stick around longer.</p>
<p>A fantastic resource for this whole “bucket&#8221; idea is the book by Ryan Levesque: Ask.</p>
<p><a href="http://www.amazon.com/dp/1939447720/" rel="nofollow ugc">http://www.amazon.com/dp/1939447720/</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Grow		</title>
		<link>https://www.groovehq.com/blog/stop-leaving-customers-on-the-table#comment-1316</link>

		<dc:creator><![CDATA[Grow]]></dc:creator>
		<pubDate>Thu, 20 Oct 2016 20:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=2259#comment-1316</guid>

					<description><![CDATA[Great examples of how seemingly marginal activities can have big results.]]></description>
			<content:encoded><![CDATA[<p>Great examples of how seemingly marginal activities can have big results.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
