I have revised this one to submit for security review with the AppExchange. With security improvements to Sites in Winter ’20, I’ll need to add additional improvements very soon.
Now includes Leads as well as Contacts. Includes Custom Metadata instead of hardcoding emails in the Flow.
Allow Recipients to Unsubscribe from All Emails
Follow this tutorial to include an unsubscribe link in promotional emails sent from Salesforce. This post gives you some reasons for considering this feature.
When the recipient clicks to unsubscribe, a flow will look for all contacts and leads who have this as their preferred email address (if you’re in NPSP) or in the Email field. All contacts or leads who meet that requirement will be marked “Email Opt Out.” The email address owner will receive one confirmation email immediately.
Follow this tutorial to include an unsubscribe link in promotional emails sent from Salesforce. My last post gives you some reasons for considering this feature.
So…you did that directly in production. I see…
When the recipient clicks to unsubscribe, a flow will look for ALL CONTACTS (not leads) who have this as their preferred email address (if you’re in NPSP) or in the Email field. All contacts who meet that requirement will be marked “Email Opt Out.” The email address owner will receive one confirmation email immediately.
The benefits of sending email directly from Salesforce are that you can automate when they go out, you can send up to 5,000 emails per day, and email templates are really simple to set up.
Dear Asses and Donkeys Trust, I no longer want to receive your email. XOXO, Belinda
But any time you’re emailing groups of people, you should be mindful of the requirements of the CAN-SPAM law (which I just learned isn’t called the “Canned Spam” law). CAN-SPAM requires that emails, in certain scenarios, provide an option for the recipient to unsubscribe.
I am writing to you on my personal blog as a puzzle-solving Salesforce admin, not a Salesforce employee. Your decisions around unsubscribe options can have legal implications for your organization so please do not take anything from this post as legal guidance or means to make your communications legally compliant. That decision is between you and your lawyers.
…And building a trigger that creates a new task when an email was sent!
In 2018, I’m focusing on building my “dev cred,” as Leah McGowen-Hare put it at Forcelandia a few years ago.
Next week is the final week of my RAD Women coding course and I am thrilled with how far I have come.
I am also building more connections in the Salesforce digital communities of Trailblazer, Power of Us Hub and Twitter.
So I was checking out the unanswered questions on the Trailblazer Community to see if I could help out and I ran into this one:
Is it possible to use Process Builder or Workflow in auto creating a task after an email is sent related to a record? The email (with a specific Subject filter) will be sent from (A) within Salesforce or (B) Gmail/Outlook but will be recorded in the Activity History. I tried to create a WR but it didn’t run after I sent an email.