The anatomy of an email people answer

AI for email and communication · Lesson 2 / 21

Four mandatory parts

Emails that get answered are built the same way across every industry: subject, first line, request, deadline. Everything else — context, attachments, pleasantries — is optional and lives further down.

Subject

A subject line is not a document title, it is a trailer for an action. The formula is object + what is needed + deadline. Compare "Report" with "March report: your edits needed by Thu". The second answers "is this mine and is it urgent?" while still in the inbox list, where the decision takes half a second.

First line

The first line is visible in the preview next to the subject. Do not spend it on "Hope this email finds you well". Put the substance there: "I need your signature on the attachment before anything else can move."

Request

One email, one request. Given three, the recipient answers the easiest and forgets the rest. Phrase it as a verb addressed to a named person: not "this needs approving" but "Anna, approve clause 4 or tell me what to change."

Deadline

Give a date and a weekday: "by Thursday 14 March". "As soon as possible" means never, because the recipient has their own queue. If there is genuinely no deadline, say so: "not urgent, any time this week" is still a deadline.

The frame

Subject: Ortex contract: clause 4 edits needed by Thu 14 Mar

Anna, good morning.

Please review clause 4 of the attached contract and either
approve it or tell me which wording to use instead.

Deadline: Thursday 14 March — legal goes on leave after that.
Context: the client wants auto-renewal removed; our exposure
is on receivables. My proposed wording is on page 2.

Thanks,
Igor

Note the order: the request and the deadline sit above the context. A reader with no time already knows what to do; a reader who needs detail will keep going.

Insight. A typical manager decides what to do with an email in four to six seconds, looking only at the subject and the first line. Anything that did not fit into those two lines influences the outcome far less than people assume.

Common mistake. Saving the request for the end, after the explanation. School-essay structure works against you here: fewer than half of recipients reach the conclusion.

Pro tip. Reread your draft with everything below line three covered. If that fragment does not make the ask obvious, reorder the paragraphs rather than adding more words.

Cheat sheet

Subject = object + action + deadline.
First line carries substance, not a greeting formula.
One email, one request, named verb, named person.
A deadline without a date is not a deadline.

1. Which subject line does its job?

2. Why does the request go above the context?

3. What is wrong with "please reply as soon as possible"?

Task — checked by AI

Take three emails you sent in the past week that were answered later than you wanted, or not at all. For each, write out the current subject line and first line, then rebuild the email on the frame: subject as object plus action plus deadline, a first line carrying the substance, one request as a verb addressed to a named person, a dated deadline. Show the full before and after pairs and explain in one or two sentences what specifically made the original hard to answer.

← Back

🔒 Answer the question correctly to move on to the next lesson.