<?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: Critique of a Random Sales Email</title>
	<atom:link href="http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/</link>
	<description>Ecommerce consulting &#38; solutions for online store retailers</description>
	<lastBuildDate>Wed, 08 Feb 2012 13:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Josh Colter</title>
		<link>http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/#comment-619</link>
		<dc:creator>Josh Colter</dc:creator>
		<pubDate>Thu, 14 Jan 2010 14:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.eliasinteractive.com/?p=997#comment-619</guid>
		<description>@Toni &amp; Jerome The sales guy did send me a quick note. Here was his reply:

&quot;Thanks for the response. I wanted to assure you this was not part of some mass email job sent out randomly to agencies. I simply came across your website, thought it was nice and sent you an email as a kind of introduction. The info@ was the only address on your site so that’s what I used.

Again sorry for the inconvenience.

PS.

Thanks for the advice on how to craft an email, but honestly this was kind of off the cuff, hence the spelling error.&quot;

My critique probably caught him off guard, so I can understand some defensiveness. Anyone who has tried to sell something has experienced writing a bad sales email (I&#039;ve written a lot fo bad sales copy). I&#039;ve been called out in the past from prospects and it was not fun (helpful, but not fun).

It&#039;s interesting that he went with the info@ address for contacting us when each Elias partner&#039;s personal twitter &amp; Linkedin accounts are on our team page.</description>
		<content:encoded><![CDATA[<p>@Toni &#038; Jerome The sales guy did send me a quick note. Here was his reply:</p>
<p>&#8220;Thanks for the response. I wanted to assure you this was not part of some mass email job sent out randomly to agencies. I simply came across your website, thought it was nice and sent you an email as a kind of introduction. The info@ was the only address on your site so that’s what I used.</p>
<p>Again sorry for the inconvenience.</p>
<p>PS.</p>
<p>Thanks for the advice on how to craft an email, but honestly this was kind of off the cuff, hence the spelling error.&#8221;</p>
<p>My critique probably caught him off guard, so I can understand some defensiveness. Anyone who has tried to sell something has experienced writing a bad sales email (I&#8217;ve written a lot fo bad sales copy). I&#8217;ve been called out in the past from prospects and it was not fun (helpful, but not fun).</p>
<p>It&#8217;s interesting that he went with the info@ address for contacting us when each Elias partner&#8217;s personal twitter &#038; Linkedin accounts are on our team page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerome</title>
		<link>http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/#comment-618</link>
		<dc:creator>Jerome</dc:creator>
		<pubDate>Thu, 14 Jan 2010 12:57:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.eliasinteractive.com/?p=997#comment-618</guid>
		<description>you&#039;re totally right, the &quot;corrected&quot; version is much better, especially with the call to action, enhanced by its position in the text: at the end. That&#039;s what you&#039;re gonna remember from the email.

The Sales reply should also be informative. Did he get back to you ?</description>
		<content:encoded><![CDATA[<p>you&#8217;re totally right, the &#8220;corrected&#8221; version is much better, especially with the call to action, enhanced by its position in the text: at the end. That&#8217;s what you&#8217;re gonna remember from the email.</p>
<p>The Sales reply should also be informative. Did he get back to you ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Toni Anicic</title>
		<link>http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/#comment-617</link>
		<dc:creator>Toni Anicic</dc:creator>
		<pubDate>Thu, 14 Jan 2010 12:27:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.eliasinteractive.com/?p=997#comment-617</guid>
		<description>Yea, your reviewed version looks much better. Did you get a reply from the sales guy? :)</description>
		<content:encoded><![CDATA[<p>Yea, your reviewed version looks much better. Did you get a reply from the sales guy? <img src='http://www.eliasinteractive.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Critique d&#8217;un email de vente pris au hasard &#124; Simple Entrepreneur</title>
		<link>http://www.eliasinteractive.com/blog/critique-of-a-random-sales-email/#comment-616</link>
		<dc:creator>Critique d&#8217;un email de vente pris au hasard &#124; Simple Entrepreneur</dc:creator>
		<pubDate>Thu, 14 Jan 2010 06:37:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.eliasinteractive.com/?p=997#comment-616</guid>
		<description>[...] Lire l&#8217;article original [...]</description>
		<content:encoded><![CDATA[<p>[...] Lire l&#8217;article original [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

