<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Nils Vinje &#8211; Groove Blog</title>
	<atom:link href="https://www.groovehq.com/blog/author/nils/feed" rel="self" type="application/rss+xml" />
	<link>https://www.groovehq.com/blog</link>
	<description></description>
	<lastBuildDate>Tue, 19 Feb 2019 11:10:43 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.5.14</generator>
	<item>
		<title>How to Say “No” to Your Customers (And Why You Should)</title>
		<link>https://www.groovehq.com/blog/how-to-say-no-to-customers</link>
					<comments>https://www.groovehq.com/blog/how-to-say-no-to-customers#comments</comments>
		
		<dc:creator><![CDATA[Nils Vinje]]></dc:creator>
		<pubDate>Tue, 29 Mar 2016 08:26:51 +0000</pubDate>
				<category><![CDATA[Customer Support]]></category>
		<guid isPermaLink="false">http://www.groovehq.com/blog/?p=3327</guid>

					<description><![CDATA[<p>It can be hard to say no to your customers. But it doesn’t need to be. Here’s how. Note from Len: this is a guest post from Nils Vinje, partner at Glide Consulting, a SaaS customer success consulting company whose customers include Oracle, Intuit, Customer.io, ToutApp and more. Nils has a tremendous amount of experience [&#8230;]</p>
<p>The post <a rel="nofollow" href="https://www.groovehq.com/blog/how-to-say-no-to-customers">How to Say “No” to Your Customers (And Why You Should)</a> appeared first on <a rel="nofollow" href="https://www.groovehq.com/blog">Groove Blog</a>.</p>
]]></description>
		
					<wfw:commentRss>https://www.groovehq.com/blog/how-to-say-no-to-customers/feed</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
