How to Include an Unsubscribe Link

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.

131206-f-it851-005

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.

For goodness sake, please try this in your sandbox or a Trailhead playground first!  Continue reading →

When to Include an Unsubscribe Link

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.

woman using white smartphone on front of table

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.

Continue reading →

Building a Custom, Responsive, Client Intake Form in Salesforce NPSP

I loved seeing DaizyLogik‘s demo of this tool for the Bellingham Food Bank at the Seattle Non-Profit User Group last year. And hurray! You can now find it on the App Exchange. Below I am reblogging from their blog – did I do this right?

DaizyLogik

For many years, Bellingham Food Bank used a legacy Access database called “The Food Bank Intake Database” to track client intake information for the 300-600 households who use their services each day they’re open. This software allowed them to collect data for analysis of the services they provided to their clients, and to produce the monthly statistical reports required by various funders.

As time passed, and as the organization upgraded their various systems, the Access database did not upgrade along with it. The staff at Bellingham Food Bank recognized the mission critical nature of the database, and began to make plans to replace the aging system once it started to crash regularly. In order to process a household every 30-60 seconds, the team needed a system they could depend on.

The Bellingham Food Bank engaged DaizyLogik to design and develop a client intake application that leverages the features of Salesforce…

View original post 20 more words