This free detector tells you if your compliment sounds copy-pasted.
We flag openers that could be sent to anyone — and that everyone recognises.
- Generic flatterymedium
I loved your recent post
→ Replace the compliment with one concrete, verifiable detail — or remove it.
- Generic flatterymedium
really impressed by what you're building
→ Replace the compliment with one concrete, verifiable detail — or remove it.
- Generic flatterylow
hope this email finds you well
→ Replace the compliment with one concrete, verifiable detail — or remove it.
- Generic flatterymedium
We share the same values
→ Replace the compliment with one concrete, verifiable detail — or remove it.
- Empty fillerlow
hope this email finds you well
→ Delete sentences that carry no information.
Quick rule-based checks, run in your browser. The MailDignity API reads full context with AI and writes rewrites.
A compliment without a detail is a template.
"Loved your recent post" is the most recognised AI icebreaker in B2B. Without a concrete reference, it signals the opposite of attention.
One specific detail beats three adjectives.
Frequently asked questions.
Are compliments bad?
Specific ones are fine. Generic ones read as automation.
What makes a compliment specific?
A detail only that person would recognise: a number, a claim, a decision.
Should I remove "hope you are well"?
In cold emails, yes. It costs a line and carries nothing.
Is this AI?
No, deterministic rules. The API reads full context.
Check every email before it sends.
Same standard, with AI context and rewrites. One API call from Clay, Make, n8n or Zapier.
Explore the API