<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
	<channel>
		<title>gdp's Comments</title>
		<language>en-us</language>
		<link>https://www.intensedebate.com/users/1276777</link>
		<description>Comments by rhappe</description>
<item>
<title>Social Media Monitoring and Engagement - Salesforce Marketing Cloud : Digital Love: Understanding How to Respond &amp; Build Relationships</title>
<link>http://radian6.mmdevreview.com/blog/2011/07/digital-love-understanding-how-to-respond-build-relationships/#IDComment175882069</link>
<description>Thank you -  You bring up a great point. If you don&amp;#039;t know someone and have not interacted in the past, it is very hard to figure out why they may not be responding. It could be many things - they don&amp;#039;t respond to unsolicited communication, they don&amp;#039;t prioritize it, its not their preferred communications channel, it didn&amp;#039;t speak to their interests, they are flooded with other work, etc.  In that case I think you should reach out to them a few times in different channels, with some time in between, but if they then do not then respond you should assume they are not interested.  Also, one mistake I see all the time is formal pitches from people I don&amp;#039;t know. A much more effective strategy would be to establish some kind of casual relationship with me first by commenting on my blog, reaching out on Twitter, etc. I am *much* more likely to pay attention to something sent to me by someone I&amp;#039;ve already had some contact with - and I think that is universally true. So, proceed with reaching out but if over time you are not getting a response, it&amp;#039;s time to move on in my opinion. There is no hard and fast rule but the more one sided communications you send out without a response, the higher the likelihood you are pestering someone </description>
<pubDate>Thu, 21 Jul 2011 12:56:46 +0000</pubDate>
<guid>http://radian6.mmdevreview.com/blog/2011/07/digital-love-understanding-how-to-respond-build-relationships/#IDComment175882069</guid>
</item>	</channel>
</rss>