Name the token, the relevance, and the fix — so the email earns the reply, not the creepy.
Audit the personalization on our last 20 cold emails.
The audit found 8 of 20 emails used the company name only — no relevance — and the best emails used a signal + pain. The fix rewrote the 8 emails to add the signal + pain, and the next 20 emails averaged 8% reply rate, up from 4%. The template earned the reply because it named the relevance, not just the token.
A personalization audit template is the audit that decides whether the personalization earns or creeps. It fixes the token, the relevance, and the fix — so the audit reads as a checklist, not a score. An email that names the company without the relevance earns the creepy; a personalization audit template that names the token and the relevance earns the reply and the meeting.
A reusable audit shape for the personalization — the token, the relevance, the fix — that earns the reply and the meeting. The template fixes the shape so the audit reads as a checklist, not a score.
The one data point the email uses — the name, the company, the signal — that earns the read. The token is the part that earns the read, because an email without the token earns the blast; an email with the token earns the read.
The one reason the token earns the reply — the signal, the pain, the angle — that earns the reply. The relevance is the part that earns the reply, because a token without the relevance earns the creepy; a token with the relevance earns the reply.
The rewrite that earns the relevance — the clearer signal, the sharper pain, the stronger angle — per email. The fix is the part that earns the reply, because a token without the fix earns the creepy; a token with the fix earns the reply and the meeting.
The agent reads your emails and the reply data, drafts the token, the relevance, and the fix, and names the rewrite per email. It pairs with the persona specific messaging pack and the contact enrichment brief templates.
The last 20 emails.
Reply rate per email.
Agent names the one data point.
One rewrite per email.
Names the token, does not blast
Names the relevance, not just the token
Re-runs monthly, not once
Pairs with the persona messaging and contact enrichment templates
Name the one token, the one relevance, and the one fix. The audit reads as a checklist, not a score, which is why the email earns the reply, not the creepy.
The token that earns the read and the relevance that earns the reply. An email that names the company without the relevance earns the creepy; an email that names the token and the relevance earns the reply.
Name the relevance — the reason the token earns the reply. A token without the relevance earns the creepy; a token with the relevance earns the reply, because the relevance is what earns the trust.
A token that earns the read, a relevance that earns the reply, and a fix that earns the meeting. The email that names the company without the relevance earns the creepy; the email that names the relevance earns the reply.