<?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"
	>
<channel>
	<title>Comments on: Email non-viable for acquisition</title>
	<atom:link href="http://blog.wordtothewise.com/2008/05/email-non-viable-for-acquisition/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2008/05/email-non-viable-for-acquisition/</link>
	<description>Spam, delivery, email and more</description>
	<pubDate>Thu, 08 Jan 2009 18:38:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Word to the Wise &#187; Recent comments</title>
		<link>http://blog.wordtothewise.com/2008/05/email-non-viable-for-acquisition/#comment-14348</link>
		<dc:creator>Word to the Wise &#187; Recent comments</dc:creator>
		<pubDate>Tue, 27 May 2008 05:00:24 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=143#comment-14348</guid>
		<description>[...] my Email non-viable for acquisition post, Josh disagreed. He says I think saying that “email is not viable for customer acquisition” might be too broad [...]</description>
		<content:encoded><![CDATA[<p>[...] my Email non-viable for acquisition post, Josh disagreed. He says I think saying that “email is not viable for customer acquisition” might be too broad [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua Baer</title>
		<link>http://blog.wordtothewise.com/2008/05/email-non-viable-for-acquisition/#comment-13760</link>
		<dc:creator>Joshua Baer</dc:creator>
		<pubDate>Wed, 14 May 2008 14:08:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=143#comment-13760</guid>
		<description>I agree that purchased lists are a bad idea and extremely difficult, if not impossible, to maintain acceptable complaint rates with.

But I think saying that "email is not viable for customer acquisition" might be too broad of a statement. I wouldn't have any problem with "Purchasing lists is not viable for customer acquisition"

There are lots of ways to do customer acquisition through email without purchasing a list. Services like CoolSavings can provide customer acquisition through email messages that have a lot of similarity to the direct mail model. People love to sign up for email lists that send them coupons, travel specials, new gadgets and sweepstakes.

When users receive a message from one of these lists, it looks a lot like direct mail. The body of the email is primarily an advertisement. Better lists have strong branding that the user recognizes. But I know lots of examples of companies that are able to provide a list "rental" instead of actually selling the list without going over the complaint thresholds and while maintaining whitelists at all the ISPs.</description>
		<content:encoded><![CDATA[<p>I agree that purchased lists are a bad idea and extremely difficult, if not impossible, to maintain acceptable complaint rates with.</p>
<p>But I think saying that &#8220;email is not viable for customer acquisition&#8221; might be too broad of a statement. I wouldn&#8217;t have any problem with &#8220;Purchasing lists is not viable for customer acquisition&#8221;</p>
<p>There are lots of ways to do customer acquisition through email without purchasing a list. Services like CoolSavings can provide customer acquisition through email messages that have a lot of similarity to the direct mail model. People love to sign up for email lists that send them coupons, travel specials, new gadgets and sweepstakes.</p>
<p>When users receive a message from one of these lists, it looks a lot like direct mail. The body of the email is primarily an advertisement. Better lists have strong branding that the user recognizes. But I know lots of examples of companies that are able to provide a list &#8220;rental&#8221; instead of actually selling the list without going over the complaint thresholds and while maintaining whitelists at all the ISPs.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
