<?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 Salesforce.com is Mangling Their Email Marketing Efforts &amp; What You Can Learn from Their Mistakes</title>
	<atom:link href="http://www.emailbroadcast.com/blog/2010/01/how-salesforce-com-is-mangling-their-email-marketing-efforts-what-you-can-learn-from-their-mistakes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.emailbroadcast.com/blog/2010/01/how-salesforce-com-is-mangling-their-email-marketing-efforts-what-you-can-learn-from-their-mistakes/</link>
	<description>Email Marketing That Rocks.</description>
	<lastBuildDate>Fri, 09 Jul 2010 18:49:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jamie Grenney</title>
		<link>http://www.emailbroadcast.com/blog/2010/01/how-salesforce-com-is-mangling-their-email-marketing-efforts-what-you-can-learn-from-their-mistakes/comment-page-1/#comment-47</link>
		<dc:creator>Jamie Grenney</dc:creator>
		<pubDate>Tue, 02 Feb 2010 18:12:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.emailbroadcast.com/blog/?p=256#comment-47</guid>
		<description>Ken to follow up on our phone call this morning we want to apologize for the email and explain what happened. 

As you mentioned, you were no longer a Salesforce customer so you should have not received these system notification emails. It should have been caught in the list suppression but there was a process breakdown. We have since corrected the problem and appreciate you bringing it to our attention.  

A couple of the points in your post seem to be misunderstandings. While it is true that our emails are sent from a  “no-reply” address, all replies go to valid and monitored email accounts. Also, we do include an opt-out link in all of our marketing emails. However, the email you received was regarding changes to the Salesforce service. We consider these communications operational in nature. In fact, we are obliged to inform all of our users of any upcoming maintenance or changes that may impact their ability to use Salesforce. 

Once again, we apologize for the frustration it has caused and hopefully this clears up some of the confusion.</description>
		<content:encoded><![CDATA[<p>Ken to follow up on our phone call this morning we want to apologize for the email and explain what happened. </p>
<p>As you mentioned, you were no longer a Salesforce customer so you should have not received these system notification emails. It should have been caught in the list suppression but there was a process breakdown. We have since corrected the problem and appreciate you bringing it to our attention.  </p>
<p>A couple of the points in your post seem to be misunderstandings. While it is true that our emails are sent from a  “no-reply” address, all replies go to valid and monitored email accounts. Also, we do include an opt-out link in all of our marketing emails. However, the email you received was regarding changes to the Salesforce service. We consider these communications operational in nature. In fact, we are obliged to inform all of our users of any upcoming maintenance or changes that may impact their ability to use Salesforce. </p>
<p>Once again, we apologize for the frustration it has caused and hopefully this clears up some of the confusion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Mahar</title>
		<link>http://www.emailbroadcast.com/blog/2010/01/how-salesforce-com-is-mangling-their-email-marketing-efforts-what-you-can-learn-from-their-mistakes/comment-page-1/#comment-46</link>
		<dc:creator>Ken Mahar</dc:creator>
		<pubDate>Thu, 21 Jan 2010 02:30:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.emailbroadcast.com/blog/?p=256#comment-46</guid>
		<description>Author Update: Incredible but true!

 After forwarding this morning&#039;s email to my contact at Salesforce that is supposed to be handling my removal (apparently a monumental task), and having a live phone conversation with that contact about my plans to blog about their ineptitude - I received this message 20 minutes ago:

From: &quot;Salesforce.com Support&quot; 
Date: January 20, 2010 6:01:24 PM PST
To: (address removed)@gmail.com
Subject: Changes to Custom Object Permissions Coming with Spring &#039;10 - CORRECTION
Reply-To: &quot;Salesforce.com Support&quot; 


 
Dear Administrator,

On Tuesday, January 19th, 2010, we sent you an email introducing new custom object permission behavior in Spring &#039;10. This new behavior only impacts Enterprise and Unlimited Edition organizations.
It has no impact on Professional or Group Edition organizations.

Professional and Group Edition organizations can continue to create custom objects and all users will have full access to the new objects. 

It is our policy to ensure that these communications are targeted to relevant audiences only. We apologize for any confusion our original email may have caused. Should you have further questions, please contact Customer Support.

Best regards,
-salesforce.com Customer Support

 

Copyright 2000-2010 salesforce.com - All rights reserved - Various trademarks held by their respective owners
Salesforce.com, One Market Street, Suite 300, San Francisco, CA 94105</description>
		<content:encoded><![CDATA[<p>Author Update: Incredible but true!</p>
<p> After forwarding this morning&#8217;s email to my contact at Salesforce that is supposed to be handling my removal (apparently a monumental task), and having a live phone conversation with that contact about my plans to blog about their ineptitude &#8211; I received this message 20 minutes ago:</p>
<p>From: &#8220;Salesforce.com Support&#8221;<br />
Date: January 20, 2010 6:01:24 PM PST<br />
To: (address removed)@gmail.com<br />
Subject: Changes to Custom Object Permissions Coming with Spring &#8216;10 &#8211; CORRECTION<br />
Reply-To: &#8220;Salesforce.com Support&#8221; </p>
<p>Dear Administrator,</p>
<p>On Tuesday, January 19th, 2010, we sent you an email introducing new custom object permission behavior in Spring &#8216;10. This new behavior only impacts Enterprise and Unlimited Edition organizations.<br />
It has no impact on Professional or Group Edition organizations.</p>
<p>Professional and Group Edition organizations can continue to create custom objects and all users will have full access to the new objects. </p>
<p>It is our policy to ensure that these communications are targeted to relevant audiences only. We apologize for any confusion our original email may have caused. Should you have further questions, please contact Customer Support.</p>
<p>Best regards,<br />
-salesforce.com Customer Support</p>
<p>Copyright 2000-2010 salesforce.com &#8211; All rights reserved &#8211; Various trademarks held by their respective owners<br />
Salesforce.com, One Market Street, Suite 300, San Francisco, CA 94105</p>
]]></content:encoded>
	</item>
</channel>
</rss>
