<?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: Transactional email</title>
	<atom:link href="http://blog.wordtothewise.com/2009/06/transactional-email/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2009/06/transactional-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: Thoughts on transactional mail at Word to the Wise</title>
		<link>http://blog.wordtothewise.com/2009/06/transactional-email/comment-page-1/#comment-2255</link>
		<dc:creator>Thoughts on transactional mail at Word to the Wise</dc:creator>
		<pubDate>Tue, 07 Jul 2009 00:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=449#comment-2255</guid>
		<description>[...] had at MAAWG about transactional email and opened up the conversation to readers here. Mike proposed a definition. [Transactional mail is] an automated message, sent on a per-user basis, usually as [...]</description>
		<content:encoded><![CDATA[<p>[...] had at MAAWG about transactional email and opened up the conversation to readers here. Mike proposed a definition. [Transactional mail is] an automated message, sent on a per-user basis, usually as [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven</title>
		<link>http://blog.wordtothewise.com/2009/06/transactional-email/comment-page-1/#comment-2254</link>
		<dc:creator>Steven</dc:creator>
		<pubDate>Thu, 18 Jun 2009 21:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=449#comment-2254</guid>
		<description>I think transactional email is anything which serves a functional purpose which is useful to the receiver. Shipping information is the classic example, invitations to buy are not.</description>
		<content:encoded><![CDATA[<p>I think transactional email is anything which serves a functional purpose which is useful to the receiver. Shipping information is the classic example, invitations to buy are not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Margaret Farmakis</title>
		<link>http://blog.wordtothewise.com/2009/06/transactional-email/comment-page-1/#comment-2258</link>
		<dc:creator>Margaret Farmakis</dc:creator>
		<pubDate>Fri, 12 Jun 2009 15:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=449#comment-2258</guid>
		<description>I agree with Mike and Kelly on their definitions, however I would disagree that these messages are always (or should only be) messages that users can&#039;t unsubscribe from. We recommend that marketers include opt-out links as part of certain transactional messages, like welcome messages, which are triggered as the result of a user action (signing up).

Welcome messages, while essential as part of any optimized email marketing program, can often receive a higher level of complaints, so to protect your sender reputation and maintain high inbox deliverability, it&#039;s always a best practice to make it easier for subscribers to opt-out than complain and click the &quot;This is spam&quot; button.

I would also agree that it&#039;s a great idea to test the use of promotions in your transactional messages. The more targeted and relevant those promotions are (for example, if the customer bought a set of sheets, include a promotion for other bedding items like pillows, blankets and throws), the better. The more relevant your messaging (whether it&#039;s content or promotions), regardless of the type of messaging you&#039;re sending, the more active and engaged your subscribers will be.</description>
		<content:encoded><![CDATA[<p>I agree with Mike and Kelly on their definitions, however I would disagree that these messages are always (or should only be) messages that users can&#8217;t unsubscribe from. We recommend that marketers include opt-out links as part of certain transactional messages, like welcome messages, which are triggered as the result of a user action (signing up).</p>
<p>Welcome messages, while essential as part of any optimized email marketing program, can often receive a higher level of complaints, so to protect your sender reputation and maintain high inbox deliverability, it&#8217;s always a best practice to make it easier for subscribers to opt-out than complain and click the &#8220;This is spam&#8221; button.</p>
<p>I would also agree that it&#8217;s a great idea to test the use of promotions in your transactional messages. The more targeted and relevant those promotions are (for example, if the customer bought a set of sheets, include a promotion for other bedding items like pillows, blankets and throws), the better. The more relevant your messaging (whether it&#8217;s content or promotions), regardless of the type of messaging you&#8217;re sending, the more active and engaged your subscribers will be.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Lorenz</title>
		<link>http://blog.wordtothewise.com/2009/06/transactional-email/comment-page-1/#comment-2257</link>
		<dc:creator>Kelly Lorenz</dc:creator>
		<pubDate>Thu, 11 Jun 2009 18:13:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=449#comment-2257</guid>
		<description>I agree with Mike on all but the opt-in message. My definition of transactional is basically the same as CAN-SPAM&#039;s: anything that people can&#039;t unsubscribe from. This would include administrative messages like shipping confirmations and receipts, anything where the marketer is providing information based on the recipient&#039;s actions. That doesn&#039;t mean, however, that transactional messages can not also include a marketing element, but the focus should be on the marketer responding to an action taken by the recipient. I&#039;m on the fence on whether actions taken toward a recipient (ie, someone is now following you) count as you can unsubscribe from these alerts and to quote the dictionary, the strict definition of a &quot;transaction&quot; is an instance of buying or selling a good.

It will probably change over time, but that is my definition of transactional emails today.

-Kelly Lorenz</description>
		<content:encoded><![CDATA[<p>I agree with Mike on all but the opt-in message. My definition of transactional is basically the same as CAN-SPAM&#8217;s: anything that people can&#8217;t unsubscribe from. This would include administrative messages like shipping confirmations and receipts, anything where the marketer is providing information based on the recipient&#8217;s actions. That doesn&#8217;t mean, however, that transactional messages can not also include a marketing element, but the focus should be on the marketer responding to an action taken by the recipient. I&#8217;m on the fence on whether actions taken toward a recipient (ie, someone is now following you) count as you can unsubscribe from these alerts and to quote the dictionary, the strict definition of a &#8220;transaction&#8221; is an instance of buying or selling a good.</p>
<p>It will probably change over time, but that is my definition of transactional emails today.</p>
<p>-Kelly Lorenz</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Hillyer</title>
		<link>http://blog.wordtothewise.com/2009/06/transactional-email/comment-page-1/#comment-2256</link>
		<dc:creator>Mike Hillyer</dc:creator>
		<pubDate>Thu, 11 Jun 2009 14:17:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=449#comment-2256</guid>
		<description>I&#039;d call it mail that is generated as a result of a user action, in direct relation to that user action. Ideally this is an action on the part of the recipient but I can see situations where it could be another user.

I&#039;d go with examples such as opt-in messages, purchase confirmations, notices of the actions of a fellow user (xx posted on your wall).

This could also extend into automated messages such as shipping notifications and alerts from a registrar that your domain is about to expire (assuming of course that the registrar in question is the one who you registered the domain with).

If I had to make it a short explanation I&#039;d say it&#039;s an automated message, sent on a per-user basis, usually as the result of a direct action by the user or strongly associated with the user.</description>
		<content:encoded><![CDATA[<p>I&#8217;d call it mail that is generated as a result of a user action, in direct relation to that user action. Ideally this is an action on the part of the recipient but I can see situations where it could be another user.</p>
<p>I&#8217;d go with examples such as opt-in messages, purchase confirmations, notices of the actions of a fellow user (xx posted on your wall).</p>
<p>This could also extend into automated messages such as shipping notifications and alerts from a registrar that your domain is about to expire (assuming of course that the registrar in question is the one who you registered the domain with).</p>
<p>If I had to make it a short explanation I&#8217;d say it&#8217;s an automated message, sent on a per-user basis, usually as the result of a direct action by the user or strongly associated with the user.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

