<?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: Timeliness of email</title>
	<atom:link href="http://blog.wordtothewise.com/2010/02/timeliness-of-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2010/02/timeliness-of-email/</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:06:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Maayan</title>
		<link>http://blog.wordtothewise.com/2010/02/timeliness-of-email/comment-page-1/#comment-3811</link>
		<dc:creator>Maayan</dc:creator>
		<pubDate>Thu, 04 Feb 2010 03:00:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1212#comment-3811</guid>
		<description>In the first case I&#039;d have to agree with you. I think the immediacy of text messaging makes it an appropriate addition to corporate messaging to users - the smaller, nimbler brother of email if you will. Companies should focus on where each type of communication works best and communicate to their subscribers the reason for obtaining email address vs. phone number for texting.

On the other point, such issues can&#039;t be completely avoided but they can be greatly reduced in the following ways: 
1) when announcing events, the creative should strive to call-out the timing of the event, if possible associating the date/time with something easy for users to remember (e.g. &quot;Our day-after-Valentine&#039;s-day sale&quot;) 
2) where events occur frequently like the one you described, marketers should strive for consistency in the amount of time b/w event notifications and event starts - utilizing follow-up messaging reminders where applicable
3) add-to-calendar button links can be added to campaigns to make it easy for users to add events to digital calendars and get reminders in a way that works best for them. This isn&#039;t very difficult to employ, and from my research can be done with Google, Yahoo, and MSN/Live web calendars as well as iCal and Outlook Calendar.

I&#039;m actually in process of writing about the third point for http://www.emailresponsibly.com/ and would love to explore the idea further. Thanks for the post - it&#039;s helping me get the gears moving.</description>
		<content:encoded><![CDATA[<p>In the first case I&#8217;d have to agree with you. I think the immediacy of text messaging makes it an appropriate addition to corporate messaging to users &#8211; the smaller, nimbler brother of email if you will. Companies should focus on where each type of communication works best and communicate to their subscribers the reason for obtaining email address vs. phone number for texting.</p>
<p>On the other point, such issues can&#8217;t be completely avoided but they can be greatly reduced in the following ways:<br />
1) when announcing events, the creative should strive to call-out the timing of the event, if possible associating the date/time with something easy for users to remember (e.g. &#8220;Our day-after-Valentine&#8217;s-day sale&#8221;)<br />
2) where events occur frequently like the one you described, marketers should strive for consistency in the amount of time b/w event notifications and event starts &#8211; utilizing follow-up messaging reminders where applicable<br />
3) add-to-calendar button links can be added to campaigns to make it easy for users to add events to digital calendars and get reminders in a way that works best for them. This isn&#8217;t very difficult to employ, and from my research can be done with Google, Yahoo, and MSN/Live web calendars as well as iCal and Outlook Calendar.</p>
<p>I&#8217;m actually in process of writing about the third point for <a href="http://www.emailresponsibly.com/" rel="nofollow">http://www.emailresponsibly.com/</a> and would love to explore the idea further. Thanks for the post &#8211; it&#8217;s helping me get the gears moving.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

