<?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>LeadSift</title>
	<atom:link href="http://leadsift.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://leadsift.com</link>
	<description>Turn Social Feeds into Local Leeds</description>
	<lastBuildDate>Fri, 17 May 2013 18:37:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>LeadSift selected for 48 hours in the Valley!</title>
		<link>http://leadsift.com/leadsift-selected-for-c10048-hours-in-the-valley/</link>
		<comments>http://leadsift.com/leadsift-selected-for-c10048-hours-in-the-valley/#comments</comments>
		<pubDate>Thu, 16 May 2013 14:41:28 +0000</pubDate>
		<dc:creator>Hatem Nassrat</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://leadsift.com/?p=1396</guid>
		<description><![CDATA[We&#8217;re proud to announce that we have been selected to take part in 48 hours in the valley on June 10-12. 48hrs in the Valley is a mentorship program hosted by the C100 in conjunction with the Canadian Consulate of San Francisco and Palo Alto. This event happens twice a year and invites 20 of [...]]]></description>
		<wfw:commentRss>http://leadsift.com/leadsift-selected-for-c10048-hours-in-the-valley/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>3 Twitter Mistakes That Could Cost You Sales and Leads</title>
		<link>http://leadsift.com/twitter-mistakes/</link>
		<comments>http://leadsift.com/twitter-mistakes/#comments</comments>
		<pubDate>Mon, 13 May 2013 16:58:15 +0000</pubDate>
		<dc:creator>LeadSift</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Lead Generation]]></category>
		<category><![CDATA[Sales Mistakes]]></category>
		<category><![CDATA[Sales Social Media]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[Social Media Leads]]></category>
		<category><![CDATA[Social Selling Mistakes]]></category>
		<category><![CDATA[Twitter Mistakes]]></category>

		<guid isPermaLink="false">http://leadsift.com/?p=1350</guid>
		<description><![CDATA[Social media has undoubtedly changed the way businesses identify potential sales leads and interact with customers. If businesses have learned anything over the last few years, it’s that social media cannot be ignored. Twitter, specifically, is an effective tool for lead discovery, relationship nurturing and driving sales. In fact, last year 82 per cent of [...]]]></description>
		<wfw:commentRss>http://leadsift.com/twitter-mistakes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why Telecom Providers Should Be Paying Attention To Social Media [INFOGRAPHIC]</title>
		<link>http://leadsift.com/telecom-providers-social-media-infographic/</link>
		<comments>http://leadsift.com/telecom-providers-social-media-infographic/#comments</comments>
		<pubDate>Mon, 06 May 2013 15:14:03 +0000</pubDate>
		<dc:creator>LeadSift</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://leadsift.com/?p=1367</guid>
		<description><![CDATA[In an earlier post, we talked about the Love/Hate relationship between telecom and social media. Specifically, we talked about the significant amount of churn in Telecom and how it was being communicated through social media. We also discussed how social media presents both an opportunity and threat to the telecom industry as it relates to [...]]]></description>
		<wfw:commentRss>http://leadsift.com/telecom-providers-social-media-infographic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
