Field Report: The "Personalised" Email That Had The Wrong Name
a field report on personalisation token failures in automated email campaigns, from [FIRST_NAME] left unsubstituted to emails addressed to the previous owner of the address
Severity Score
8.1 / 10
Cringe Half-Life
The failure is immediate; the screenshot is permanent
Recurrence Probability
Every list with dirty data
Era
2026
👁️ What Everyone Noticed
The thing nobody had a name for until now
The ambition of personalised email marketing — creating a one-to-one communication experience at million-recipient scale — collided repeatedly with the practical reality of unclean data, incorrect field mapping, and automation platform edge cases. The result was emails that warmly greeted recipients as "Hi [FIRST_NAME]," or correctly addressed the company name but incorrectly addressed the individual, or warmly referred to a recent purchase the recipient had not made.
🦠 Why It Spread
The Bureau's best guess (officially filed)
Personalisation tokens are now standard practice. Standard practice scales faster than QA processes. Every additional field added to a personalisation template added an additional potential failure mode. The emails sent to millions. The errors reached thousands. The screenshots reached everyone.
💀 Peak Cultural Damage
The version that made the Bureau file a formal complaint
An email from a mental health app beginning "Hi [FIRST_NAME], we noticed you haven't completed your wellbeing check-in this week." The wellbeing app had not resolved its template variables.
🔄 Relapse Risk
The Bureau's honest forecast (not good)
Permanent. More personalisation variables mean more failure modes.
🧟 Survivors
Sites still doing this. Unironically.
"Hi [FIRST_NAME]," (still being sent in 2026)
emails addressed to the previous employer listed in an old LinkedIn profile
"We missed you, [COMPANY_NAME]" addressed to an individual person
🔗 Related Phenomena
Other things the Bureau blames
2026 • Ranking
Email Subject Lines That Still Get Opened
a ranking of email subject line strategies so transparent, manipulative, or bizarre that their continued efficacy is the most damning evidence about human attention available
2026 • Field Report
Fake Social Proof Counters In The Wild
a field report on live counters, active-now widgets, and quietly theatrical metrics with no disclosed origin
2025 • Top 10
Ways AI Made The Internet Worse
a ranked audit of the specific, documented, and entirely preventable ways AI deployment degraded ordinary internet use across 2025
2026 • Field Report
Founders Using Terminal Fonts For Everything
an on-the-ground report from the startup web where monospaced authority escaped containment
🦕 Historical Predecessor
What it was before anyone named it
📅 2026 Archive
Other things the internet did that year
2026 • Top 10
Worst AI Website Trends of 2026
a ranked archive of the most cursed AI landing-page habits, from model-logo rows to fake agent claims and terminal-font overconfidence
2026 • Trend
All Model Logos In One Row
the sudden trend of AI product pages lining up every possible model brand as a trust ceremony
2026 • Trend
Terminal Fonts For Everything
the trend of applying terminal fonts and command-line styling to products that do not benefit from either
2026 • Trend
Chat Widgets Blocking Close Buttons
the increasingly universal habit of support widgets blocking the very buttons users came to press
❓ FAQ
Questions the Bureau has been asked too many times
What is Personalised Email With Wrong Name?
Personalised Email With Wrong Name is a documented field report in the NCCB archive for 2026, best known for a field report on personalisation token failures in automated email campaigns, from [first_name] left unsubstituted to emails addressed to the previous owner of the address.
Why did Personalised Email With Wrong Name spread?
Personalisation tokens are now standard practice. Standard practice scales faster than QA processes. Every additional field added to a personalisation template added an additional potential failure mode. The emails sent to millions. The errors reached thousands. The screenshots reached everyone.
Will Personalised Email With Wrong Name come back?
Permanent. More personalisation variables mean more failure modes.
When was Personalised Email With Wrong Name first documented?
Personalised Email With Wrong Name is indexed in the NCCB archive with a first documented sighting of The first mail merge. Approximately 1980..
⚖️ Bureau Tribunal
Think you're immune to this? Submit for evaluation.
The Tribunal offers comprehensive life audits: Soul Value Index, Attention Span Certification, Hypocrisy Polygraph, and the Normie Certification. Results are binding. No appeals. No refunds.
🖼️ Visual Evidence
What this looks like when shared without context (Bureau approved)
forensic exhibit of personalisation token failures, each mounted as specimen with field mapping diagram and deadpan annotation, museum of automation mishaps