<?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: How NOT to Title Your Email Newsletter Subject Line</title>
	<atom:link href="http://www.mjswebsolutions.com/blog/index.php/2007/11/19/how-not-to-title-your-email-newsletter-subject-line/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mjswebsolutions.com/blog/index.php/2007/11/19/how-not-to-title-your-email-newsletter-subject-line/</link>
	<description>The MJS blog was created to share with others our successes, mistakes and experiences while on the internet. I hope we&#039;re able to provide some useful and meaningful advice in the process.</description>
	<lastBuildDate>Fri, 02 Jul 2010 15:27:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Michael Swartz</title>
		<link>http://www.mjswebsolutions.com/blog/index.php/2007/11/19/how-not-to-title-your-email-newsletter-subject-line/comment-page-1/#comment-15698</link>
		<dc:creator>Michael Swartz</dc:creator>
		<pubDate>Tue, 20 Nov 2007 21:47:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjswebsolutions.com/blog/?p=197#comment-15698</guid>
		<description>Hello Janine.

Thank you for your response.

I went back to the email and Vertical Response did deliver. 

I didn&#039;t mean to come down hard on VR, I just wish the headline in the email read &quot;Be Ready for Too Much Business&quot; instead of &quot;Keep Your Customers Happy &amp; Manage Service Levels&quot;. I would have been more likely to click through.

I agree, the subject line was strong. That&#039;s why I opened the email and was ready to comment on the story.</description>
		<content:encoded><![CDATA[<p>Hello Janine.</p>
<p>Thank you for your response.</p>
<p>I went back to the email and Vertical Response did deliver. </p>
<p>I didn&#8217;t mean to come down hard on VR, I just wish the headline in the email read &#8220;Be Ready for Too Much Business&#8221; instead of &#8220;Keep Your Customers Happy &amp; Manage Service Levels&#8221;. I would have been more likely to click through.</p>
<p>I agree, the subject line was strong. That&#8217;s why I opened the email and was ready to comment on the story.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janine Popick</title>
		<link>http://www.mjswebsolutions.com/blog/index.php/2007/11/19/how-not-to-title-your-email-newsletter-subject-line/comment-page-1/#comment-15697</link>
		<dc:creator>Janine Popick</dc:creator>
		<pubDate>Tue, 20 Nov 2007 21:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mjswebsolutions.com/blog/?p=197#comment-15697</guid>
		<description>Hi Michael

We actually did deliver, if you click on the story you are taken to a subhead that reads:

BE READY FOR TOO MUCH BUSINESS

You&#039;ve only got about 35-40 characters in your subject line to get a message across, we felt this was the strongest. 

There actually was no trickery involved. We try to give our small businesses as much beneficial information in a newsletter that we can to help them. We don&#039;t get &quot;paid advertising&quot; to do this. 

BTW, great site.

Janine Popick</description>
		<content:encoded><![CDATA[<p>Hi Michael</p>
<p>We actually did deliver, if you click on the story you are taken to a subhead that reads:</p>
<p>BE READY FOR TOO MUCH BUSINESS</p>
<p>You&#8217;ve only got about 35-40 characters in your subject line to get a message across, we felt this was the strongest. </p>
<p>There actually was no trickery involved. We try to give our small businesses as much beneficial information in a newsletter that we can to help them. We don&#8217;t get &#8220;paid advertising&#8221; to do this. </p>
<p>BTW, great site.</p>
<p>Janine Popick</p>
]]></content:encoded>
	</item>
</channel>
</rss>
