The setup
An account manager had a thoughtful idea for his own two-week honeymoon: when his email set an out-of-office reply, a matching CRM automation would flip on too, and — his favorite touch — auto-mark any contact who emailed him during that window as "Do Not Contact," so marketing wouldn't nag people who were mid-conversation with him while he was unreachable. Considerate, in theory. He built it himself, quietly, as a personal quality-of-life hack, and rolled it out to just his own account list without mentioning it to anyone, because it felt like a personal setting, not a company one.
The only field available to flag "don't contact this person right now" was the org-wide Contact Status field — the same one marketing, finance, and renewals all read from to decide who gets emailed at all. There was no per-rep, temporary, or scoped version. He used the field that existed.
The collapse
He left for his honeymoon. Over two weeks, a good chunk of his roughly 400 active accounts emailed him with logistics questions, support requests, and renewal paperwork — completely normal customer behavior. Every one of them got auto-flagged "Do Not Contact" at the contact level, org-wide, not just "don't email while he's out." That flag silently suppressed them from renewal reminders, the quarterly newsletter, and — critically — the automated renewal invoice sequence that finance relied on completely.
Nobody noticed for six weeks, until finance asked why renewal invoice open rates had quietly cratered. By then, 118 customers had been globally suppressed from all communication. Several missed their renewal window entirely and briefly lapsed, which produced a wave of "wait, are we cancelled?" phone calls timed almost perfectly with his first week back from the honeymoon.
The autopsy
Root causes on record
- A personal automation used a company-wide field. "Do Not Contact" at the account level is not the same thing as "don't email this specific person right now," and the system had no way to express the difference.
- Nobody reviewed it because nobody knew it existed. A one-person automation, built and deployed without any change process, had no second set of eyes to catch the scope problem.
- Suppression and renewal billing shared a single flag. A courtesy gesture toward inbox fatigue ended up silently blocking invoices — two very different concerns, tied to the same switch.
- No monitoring on Do Not Contact volume. A sudden spike of 118 new suppressions in two weeks should have tripped an alert well before finance stumbled onto it by accident.
Recommendation pending
Editor's note: this slot will point to a data-governance tool that can alert on unusual bulk field changes — exactly the kind of spike that sat unnoticed here for six weeks.
What the post-mortem actually changed
Marketing suppression and billing suppression are now two separate fields, and any automation touching either requires sign-off from a second person before it goes live — no more solo personal hacks running on shared data. A weekly report now flags any Do Not Contact spike above a small threshold. He still thinks his original idea was a good one. He is not wrong. It just needed a field that didn't exist yet.