WEBVTT

1
00:00:00.000 --> 00:00:03.880
Ruth asked Cedar Valley Hospice for
exactly one fundraising

2
00:00:03.880 --> 00:00:06.100
email between November and January.

3
00:00:06.900 --> 00:00:10.000
On the 18th of November, Dan sends an
approved proposal.

4
00:00:10.780 --> 00:00:12.580
That fulfills her single email quota.

5
00:00:13.740 --> 00:00:17.780
But a weekly contact import into the
events platform fails to carry over

6
00:00:17.780 --> 00:00:18.960
her suppression status.

7
00:00:19.840 --> 00:00:23.420
On the 3rd of December, the events team
successfully delivers a concert

8
00:00:23.420 --> 00:00:24.060
ticket reminder.

9
00:00:24.880 --> 00:00:25.840
That is a breach.

10
00:00:26.220 --> 00:00:30.040
A ticket request still counts as an
ask, no matter which team sends it.

11
00:00:30.940 --> 00:00:35.120
Keisha, the operations manager, audits
the actual delivery logs on the

12
00:00:35.120 --> 00:00:37.260
7th of December and catches the error.

13
00:00:37.860 --> 00:00:41.880
She immediately fixes the import flaw
and checks the database to find 11

14
00:00:41.880 --> 00:00:43.040
other donors affected.

15
00:00:43.960 --> 00:00:48.020
For the 11 donors whose latest
preferences still allow email, Keisha

16
00:00:48.020 --> 00:00:49.920
executes a strict recovery protocol.

17
00:00:49.920 --> 00:00:54.060
Each gets a short, plain apology email
containing absolutely

18
00:00:54.060 --> 00:00:56.280
no new invitations or asks.

19
00:00:57.120 --> 00:01:00.060
But there is an absolute exception for
the 12th donor.

20
00:01:00.600 --> 00:01:04.520
Because this person recently requested
no email at all, Keisha merely

21
00:01:04.520 --> 00:01:07.560
records the breach and sends absolutely
nothing.

22
00:01:08.080 --> 00:01:12.020
Count actual deliveries across every
system and verify suppression lists

23
00:01:12.020 --> 00:01:13.880
after every single database import.