<?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: Friday Q&#038;A: A Quick Tip for Reducing SaaS Churn	</title>
	<atom:link href="https://www.groovehq.com/blog/friday-qa-july-22-2016/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog/friday-qa-july-22-2016</link>
	<description></description>
	<lastBuildDate>Sat, 16 Feb 2019 11:42:53 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.1</generator>
	<item>
		<title>
		By: Wei Zheng		</title>
		<link>https://www.groovehq.com/blog/friday-qa-july-22-2016#comment-1548</link>

		<dc:creator><![CDATA[Wei Zheng]]></dc:creator>
		<pubDate>Fri, 22 Jul 2016 16:29:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=710#comment-1548</guid>

					<description><![CDATA[The blog is helpful. Thanks!
My question is what level of churn is acceptable? Churn is always there, it is just to which level it starts worrying you. Are there any related metrics you use? Or it could be as simple as driving down the churn at all time, and once it starts creeping up, you do something about it in order to keep it down?]]></description>
			<content:encoded><![CDATA[<p>The blog is helpful. Thanks!<br />
My question is what level of churn is acceptable? Churn is always there, it is just to which level it starts worrying you. Are there any related metrics you use? Or it could be as simple as driving down the churn at all time, and once it starts creeping up, you do something about it in order to keep it down?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kate H		</title>
		<link>https://www.groovehq.com/blog/friday-qa-july-22-2016#comment-1549</link>

		<dc:creator><![CDATA[Kate H]]></dc:creator>
		<pubDate>Fri, 22 Jul 2016 16:01:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=710#comment-1549</guid>

					<description><![CDATA[Thanks for taking time to answer my question, Alex :) And great insights, as always.]]></description>
			<content:encoded><![CDATA[<p>Thanks for taking time to answer my question, Alex 🙂 And great insights, as always.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James McBryan		</title>
		<link>https://www.groovehq.com/blog/friday-qa-july-22-2016#comment-1550</link>

		<dc:creator><![CDATA[James McBryan]]></dc:creator>
		<pubDate>Fri, 22 Jul 2016 15:45:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=710#comment-1550</guid>

					<description><![CDATA[I notice you guys use intercom for that.  I was thinking about doing something similar but using Groove to kick off the message through the API just so I can consolidate everything to one system.  Is there a reason you wouldn&#039;t recommend using Groove to send out that type of message?]]></description>
			<content:encoded><![CDATA[<p>I notice you guys use intercom for that.  I was thinking about doing something similar but using Groove to kick off the message through the API just so I can consolidate everything to one system.  Is there a reason you wouldn&#8217;t recommend using Groove to send out that type of message?</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
