One Email Means Every Team

The finding in its setting

Damgaard and Gravert (2018) emailed about 43,500 people on DanChurchAid’s list. One version added a postscript promising a single email in the next three months, where the usual pattern was monthly. Over the first three days, 0.30% of that group unsubscribed against 0.49% for the usual email: 0.19 percentage points lower, or about 39% fewer in relative terms. Giving didn’t differ significantly. Donors who gave monthly by automatic payment weren’t included.

The tested promise covered email in general. A promise about fundraising email only, like the one below, is narrower and wasn’t what the study tested. The study doesn’t show that quarterly contact suits everyone or that fewer emails raise more money.

One promise, many senders

A development team can send one appeal and still break the promise, because the events team sends a ticket invitation, a relationship manager sends a personal ask and the platform sends an automated reminder. Each team sent one email. The donor received four.

Classify every message by its purpose, whatever the sending team calls it. Then check each donor’s delivery history across every system that can send. A combined contact history tells you whether the promise held; a count of templates per team doesn’t.

Writing the promise

Use exact dates, name the kind of email covered and list what will still arrive. If the donor’s own words were broader, such as “just one email please,” either honor that for all email or ask what they meant before applying a narrower promise.

Keep each preference with its source and date, apply the latest one and keep the history. A preference outranks anything staff have said they’ll send. If a relationship manager offered to send a proposal and the donor has since chosen fewer fundraising emails, the proposal becomes the one email or waits until the period ends.

Ruth’s preference, and what was already scheduled

Cedar Valley Hospice’s preference page lets donors choose “One fundraising email between November 1 and January 31.” Ruth Adair, who has given every December for six years, chooses it on October 20 and receives the confirmation below. Ruth’s record also shows a September conversation in which Dan, a relationship manager, offered to send details of the family room renovation in November, and Ruth said that would be fine.

On October 23, Keisha, the operations manager, pulls every message scheduled to reach Ruth between November 1 and January 31 from every system that can send email.

How Keisha resolved it

Dan’s proposal becomes the one fundraising email. Ruth had agreed to receive it, it’s the most specific of the six fundraising messages scheduled, and it comes from someone Ruth knows. Keisha asks Dan to keep it to one message. If Ruth replies with questions, Dan answers them, but there’s no follow-up nudge unless Ruth asks for one.

Lin’s platform can’t remove the appeal section for individual readers, so Lin sets up a news-only edition, with no appeal and no donate button, for donors with this preference. In December, when the appeal leads the newsletter, the edition is suppressed for them.

Keisha adds Ruth to the suppression list in every system that sends: the email platform, the events platform and the automation rules. Each queue owner confirms in writing that it’s applied. Dan’s calendar entry now reads “Ruth: one fundraising email agreed, November 18.”

The audit

Keisha reads delivery events every Monday during the period, and again on February 2. Drafts and scheduled sends don’t count. Keisha reads delivery logs from the email platform, the events platform and the CRM’s record of staff email, and asks relationship managers to confirm anything sent outside those systems.

The December 3 reminder came from a weekly contact import into the events platform, and the import didn’t carry suppressions. Keisha finds it on the December 7 check. Ruth received two fundraising emails instead of one. Keisha fixes the import, checks the other donors with the same preference and finds eleven more who received the reminder, and tells Paul and Dan that day.

Ruth’s preferences still allow email, so Keisha sends a short apology with no mention of the concert or the appeal and no request of any kind. For the one affected donor who had since asked for no email at all, Keisha fixes the cause and records the breach without writing.

Ruth’s December gift doesn’t restart anything. The receipt went out as usual and the promise ran to January 31. The February 2 audit found no further breaches.

Who owns it

One person owns the register and the audit, usually in operations. Each queue owner confirms suppression in their own system, and confirms again after any import or list rebuild. Relationship managers log personal emails in the CRM or tell the register owner, because personal email often bypasses the systems the audit reads.