| Length | 25 to 125 words, signature and mentions not counted | To review: −15% · Problem: −35%, cap 65 · Under 12 words: cap 40 | A first email is read in a few seconds, often on a phone. |
|---|
| First sentence | No “I hope this email finds you well”, “My name is…”, “I’m reaching out…”, “I’m X, a sales rep at Y”… | To review: −15% | The first line shows in the inbox preview. |
|---|
| Focused on the prospect | Fewer words about the sender (I, we, our, “At X, we”) than about the prospect (you, your). “I saw that your…” does not count | To review: −20% · Problem: −30%, cap 65 | A prospect replies to what concerns them, not to a company presentation. |
|---|
| One question only | 1 or 2 question marks | To review: −20% · Problem: −25%, cap 65 | With no question, nothing invites a reply; with three, it is not clear which to pick. |
|---|
| Light ask | No meeting, call, video call, demo or calendar link (Calendly…) in the first email | To review: −15% | Saying yes to a question costs less than blocking a slot in a calendar. |
|---|
| Readability | 25 words per sentence on average, 60 per paragraph | To review: −10% | A block of text gets skimmed; short sentences get read. |
|---|
| Variables | No variable like {{firstName}} or {{company}} in a ready-to-send email | Problem: cap 40 | It is the most visible mistake in an automated email. |
|---|
| Badly closed variables | No brace too many or too few, even in a template | Problem: cap 40 | A single forgotten brace goes out as it is in every email of the campaign. |
|---|
| Subject line length | 1 to 6 words, 45 characters at most | To review: −8% · Problem: −20%, cap 65 | Mail apps cut long subject lines, especially on phones. |
|---|
| Capitals, exclamation marks and emojis in the subject line | No word in capitals (acronyms aside), exclamation mark or emoji | To review: −10% · Problem: −20%, cap 65 | A subject line that shouts looks like advertising. |
|---|
| Fake thread | “RE:” or “FWD:” only when replying to a quoted message; “Following up on our conversation” only after a real exchange | To review: −25% · Problem: −25%, cap 65 | Making someone believe in a conversation misleads the recipient; in the United States, the CAN-SPAM Act forbids misleading subject lines. |
|---|
| Ad-like subject line | No “free”, “promo”, “exclusive offer”, “last chance”… | To review: −12% | The subject line decides whether the email gets opened. |
|---|
| Links | 0 or 1 link in the message, addresses without “https://” included (the signature is not counted) | To review: −15% · Problem: −25%, cap 65 | Several links make an email look commercial, to the reader and to the filters alike. |
|---|
| Shortened links | No bit.ly, tinyurl or other link shorteners | Problem: −20%, cap 65 | They hide the destination and are often filtered. |
|---|
| Attachments | No attachment in a first email | To review: −10% | An attachment from a stranger raises suspicion and weighs on deliverability. |
|---|
| Words in capitals | 2 words in capitals at most (acronyms like B2B, GDPR or SIRET do not count) | To review: −10% | Capitals read like shouting. |
|---|
| Exclamation marks | 1 exclamation mark at most | To review: −6% | Forced enthusiasm sounds like selling. |
|---|
| Emojis | 1 emoji at most | To review: −8% | In a professional first email, they look less serious. |
|---|
| Ad-like phrases | No “100% guaranteed”, “click here”, “exclusive offer”, “act now”… | To review: −12% | These phrases rarely send an email to spam on their own, but they make it look like an ad. |
|---|
| Refusing future emails | In every message (CNIL) | Problem: −20%, cap 65 | The CNIL requires every message to offer a simple, free way to object to the following ones. |
|---|
| Sender identified | Name and company in the signature (CNIL) | To review: −5% · Problem: −15%, cap 65 | The CNIL requires the company on whose behalf the message is sent to be identified. |
|---|
| Information on personal data | At first contact: a link to a page that gives the information required by article 14 of the GDPR | To review: −3% | When the address was not collected from the person, the GDPR requires you to inform them no later than the first message: who is writing, why, on what legal basis, for how long, with which rights and where the address came from, among other things. The usual practice: the email says who is writing and how to refuse, and a link leads to the detail. |
|---|
| Postal address (United States) | Emails in English: a valid postal address (CAN-SPAM) | To review: −3% | In the United States, the CAN-SPAM Act requires a valid postal address in every commercial email. |
|---|