<?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 Support</title>
	<atom:link href="http://www.mailchimp.com/blog/transactional-email-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mailchimp.com/blog/transactional-email-support/</link>
	<description>MailChimp, email marketing, and monkeys!</description>
	<lastBuildDate>Fri, 20 Nov 2009 22:25:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Transactional and Marketing email options &#171; Spudaroo.com: Blog</title>
		<link>http://www.mailchimp.com/blog/transactional-email-support/comment-page-1/#comment-4925</link>
		<dc:creator>Transactional and Marketing email options &#171; Spudaroo.com: Blog</dc:creator>
		<pubDate>Sun, 30 Aug 2009 20:06:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1365#comment-4925</guid>
		<description>[...] in love all over again. Its so easy you can&#8217;t help but feel warm and fuzzy. They have limited transactional email support which will in short let you handle welcome emails and forgot your password emails. Pricing of [...]</description>
		<content:encoded><![CDATA[<p>[...] in love all over again. Its so easy you can&#8217;t help but feel warm and fuzzy. They have limited transactional email support which will in short let you handle welcome emails and forgot your password emails. Pricing of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kate</title>
		<link>http://www.mailchimp.com/blog/transactional-email-support/comment-page-1/#comment-4924</link>
		<dc:creator>Kate</dc:creator>
		<pubDate>Sun, 30 Aug 2009 18:49:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1365#comment-4924</guid>
		<description>I would love to see this expanded. I am in the process of launching a new site that has 50+ transactional emails to handle a variety of things. I would LOVE to run all of this through MailChimp and would happily pay to do so but right now, this isn&#039;t possible while you only support one off transactional email.

This is a feature that is so, so desperately needed by small and medium sized business alike. Its archaic to have to keep going back to the dev team in order to amend the content or template for an email. 

Please add this soon - you will be swamped with customers!</description>
		<content:encoded><![CDATA[<p>I would love to see this expanded. I am in the process of launching a new site that has 50+ transactional emails to handle a variety of things. I would LOVE to run all of this through MailChimp and would happily pay to do so but right now, this isn&#8217;t possible while you only support one off transactional email.</p>
<p>This is a feature that is so, so desperately needed by small and medium sized business alike. Its archaic to have to keep going back to the dev team in order to amend the content or template for an email. </p>
<p>Please add this soon &#8211; you will be swamped with customers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://www.mailchimp.com/blog/transactional-email-support/comment-page-1/#comment-4034</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Fri, 05 Jun 2009 19:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1365#comment-4034</guid>
		<description>I love the transactional support however I&#039;m wondering if it supports our use case. We have a number of transactional emails; new users, password resets, etc. We would like people outside the development group to manage the content of these emails. I figured, create an email template for each transaction type. The problem though is that the API requires you to specify the content array which overrides the values in those templates. The API does the same thing for values like Subject, From, etc.

Is there anyway to allow the template default values, and the list default values to be used?

Please feel free to email if you have any clarifying questions.</description>
		<content:encoded><![CDATA[<p>I love the transactional support however I&#8217;m wondering if it supports our use case. We have a number of transactional emails; new users, password resets, etc. We would like people outside the development group to manage the content of these emails. I figured, create an email template for each transaction type. The problem though is that the API requires you to specify the content array which overrides the values in those templates. The API does the same thing for values like Subject, From, etc.</p>
<p>Is there anyway to allow the template default values, and the list default values to be used?</p>
<p>Please feel free to email if you have any clarifying questions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://www.mailchimp.com/blog/transactional-email-support/comment-page-1/#comment-1950</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 13 Nov 2008 18:16:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1365#comment-1950</guid>
		<description>This is really great! I love when you add new features to the API.</description>
		<content:encoded><![CDATA[<p>This is really great! I love when you add new features to the API.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shafqat</title>
		<link>http://www.mailchimp.com/blog/transactional-email-support/comment-page-1/#comment-1862</link>
		<dc:creator>Shafqat</dc:creator>
		<pubDate>Thu, 30 Oct 2008 18:47:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mailchimp.com/blog/?p=1365#comment-1862</guid>
		<description>Simply awesome. We can now replace our ugly/boring welcome e-mails with some monkey sexiness. Well done! Look forward to trying it out.</description>
		<content:encoded><![CDATA[<p>Simply awesome. We can now replace our ugly/boring welcome e-mails with some monkey sexiness. Well done! Look forward to trying it out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
