<?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: Chipotle Wraps Up a Catastrophic Rewards Program, and Dishes Out a Lesson in What NOT to Do…</title>
	<atom:link href="https://synced.io/blog/catastrophic-rewards-program/feed/" rel="self" type="application/rss+xml" />
	<link>https://synced.io/blog/catastrophic-rewards-program/</link>
	<description></description>
	<lastBuildDate>Wed, 02 Nov 2016 12:50:41 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.2</generator>
	<item>
		<title>By: 5 Loyalty Programme Trends to Watch &#124; Synced.io</title>
		<link>https://synced.io/blog/catastrophic-rewards-program/#comment-469</link>
		<dc:creator><![CDATA[5 Loyalty Programme Trends to Watch &#124; Synced.io]]></dc:creator>
		<pubDate>Wed, 02 Nov 2016 12:50:41 +0000</pubDate>
		<guid isPermaLink="false">https://synced.io/blog/?p=180#comment-469</guid>
		<description><![CDATA[[&#8230;] The loyalty programme landscape is continually changing, with trends coming and going as quickly as Chipotle’s catastrophic ‘Chiptopia’ scheme. For brands and businesses, the secret is to gain insight on what’s got staying power, and what’s simply destined to crash and burn, Chipotle style [to read more about where Chipotle went wrong - check our post here] [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] The loyalty programme landscape is continually changing, with trends coming and going as quickly as Chipotle’s catastrophic ‘Chiptopia’ scheme. For brands and businesses, the secret is to gain insight on what’s got staying power, and what’s simply destined to crash and burn, Chipotle style [to read more about where Chipotle went wrong - check our post here] [&#8230;]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
