Write the subject line last, keep the body under 150 words, and put the ask in its own paragraph before the signature. Those three choices fix most unprofessional emails before you touch tone or greeting. The method below runs in the order you actually compose, from deciding whether email is the right channel through the pre-send check, with concrete limits you can apply today. It assumes standard business email in English, whether you're writing a colleague, a client, or a hiring manager.

Decide Within Two Minutes Whether Email Is the Right Channel

Email is the wrong tool for anything that needs a decision in under an hour or involves more than four back-and-forth exchanges. A quick chat or a call closes those faster. Reserve the inbox for requests that can wait half a day and for anything you need in writing.

Match the channel to the stakes. A scheduling change goes in a calendar invite or a chat message. A pricing exception, a scope change, or a performance conversation goes in email because someone may need the record later. Writing those in chat buries the paper trail.

Skip email entirely for emotional conversations. Criticism, conflict, and bad news land badly in text, and the recipient forwards them. A 2023 survey by the email provider Superhuman found the average professional spends roughly 2.5 hours a day in their inbox. That volume means your message competes with dozens of others, so it should be the one that needs a reply, not the one that should have been a call.

Check one more thing before drafting: whether the recipient is internal or external. Internal messages can drop formalities and use first names. External messages need a full signature, a clear subject, and slightly more context, because the reader may not know your project or your role.

Write a Subject Line That States the Ask in Six to Ten Words

A subject line should read like a headline, not a topic label. "Budget approval needed by Friday" beats "Budget" every time, because the recipient can triage it from the lock screen. Aim for 6 to 10 words and front-load the action.

Use one of four patterns. Request: "Need your sign-off on the Q1 deck." Status: "Client proposal sent β€” waiting on legal." Question: "Do we keep the Tuesday call?" Information: "Office moves to the third floor Monday." Each tells the reader what to do or what changed.

Put deadlines in the subject when they exist, and make them specific. "By Thursday 3 p.m." gives a real cutoff. "Soon" gives none. If you're replying within an existing thread, edit the subject to reflect the new ask rather than leaving a stale one from six messages ago. A thread titled "Quick question" that now contains a contract deadline wastes everyone's time.

If you're cold-emailing, name the connection or the reason in the subject. "Introduction from Dana Ruiz" or "Following your talk at the Denver conference" earns an open. Generic subject lines from strangers read as marketing and get archived unread.

Choose the Greeting and Closing by Relationship, Not Habit

Greeting choice signals how well you know the reader. "Hi [First Name]" works for colleagues, peers, and most clients in North America and Northern Europe. "Dear [Title] [Last Name]" fits formal first contact, legal correspondence, and conservative industries. "Hello [First Name]" is a safe middle for external contacts you've met once.

Avoid "To Whom It May Concern" when you can find a name. A quick look at the company site or a prior thread usually solves it. If you truly can't find one, "Hello [Team Name] team" reads less stiff. "Hey" belongs in chat, not email, unless you already use it with that person.

Closings follow the same logic. "Best," "Thanks," and "Regards" cover most situations. "Sincerely" is for formal or legal contexts. "Cheers" is fine internally in casual cultures and risky externally. Whatever you pick, keep it consistent with the greeting β€” "Dear Dr. Chen" paired with "Cheers" reads as a glitch.

One habit worth building: use the recipient's name once in the greeting and once in the closing paragraph if the email is longer than a few lines. It reads as attention, not repetition, when the body is substantive.

Open With the Point: Context Sits in Paragraph Two

The first sentence should tell the reader what the email is about and what you need. Everything else β€” background, history, the reason you're raising it now β€” comes after. This inverted structure is the single biggest difference between a professional email and a slow one.

Compare two openings. Weak: "I hope this email finds you well. I wanted to reach out regarding the project we discussed last month, which has been progressing and raised a few points." Strong: "I need your approval on two line items in the project budget before Friday." The second takes three seconds to understand. The first takes fifteen and still hasn't said what's wanted.

Keep pleasantries to one short line at most, and skip them in ongoing threads. "Hope you're well" on the fifth message in a chain is noise. On a first contact it's fine as a single sentence before the point. The reader will forgive a missing pleasantry. They won't forgive a buried ask.

If you're writing to someone senior or outside your organization, add one line of context after the ask: "We met at the Denver conference in March; you suggested I follow up about the vendor pilot." That's enough. Your life story goes no further.

Keep the Body Under 150 Words and Use Three Short Blocks

Most professional emails fit in 75 to 150 words. That's roughly the length of two short paragraphs, or one paragraph plus a numbered list. Longer messages get skimmed, replied to late, or never answered. The writer who respects the reader's time gets answered first.

Structure the body in three blocks. Block one: the ask or the news, in one or two sentences. Block two: the minimum context the reader needs to act β€” a date, a number, a link, a document title. Block three: the specific next step and who owns it. Then stop. No summary, no restating what you just said.

Use a numbered list when the email contains more than two action items. Three bullets beat a paragraph of commas, and the reader can reply "2 and 3 are fine, 1 needs a call" without re-reading the whole thing. Skip bullets for a single request; they dress up a two-line email as a memo.

If the email genuinely needs to be long β€” a proposal summary, a post-mortem, a detailed handoff β€” put the ask and a one-line summary at the top, then label sections underneath. Long emails that open with the point still get read. Long emails that build to the point don't.

Separate the Ask From the Context So It Can't Be Missed

The most common failure in professional email is an ask buried mid-paragraph. The reader skims, misses it, replies to the easier part, and the request stalls for a week. Give the ask its own line, its own paragraph, or its own bullet.

A workable pattern: state the ask in sentence one, give context in the middle, then restate the ask as a single line before the sign-off. That last line is not repetition if it's the actionable version. "So: can you approve the $4,200 line by Thursday?" is a cleaner restatement than "Looking forward to your thoughts."

Be concrete about what you want. "Let me know" is not an ask. "Reply with yes or no by Wednesday" is. If you need a document, name it. If you need a meeting, propose two time windows. If you need a decision, say what happens on each branch: "If I don't hear back by Friday, I'll go with option A."

On deadline pressure, name the reason rather than inventing urgency. "The printer needs final files Friday" justifies the ask. "ASAP" without a reason reads as poor planning and gets deprioritized by busy readers.

Set a Reply Deadline and Make It Easy to Say No

Every request email needs a deadline, and it should be a real date, not a feeling. "By end of day Thursday" works. "When you get a chance" doesn't, because it gives the reader permission to file the email under "someday" and forget it. A named date, even a generous one, produces replies.

Make the default easy. If a no is acceptable, say so: "If this isn't feasible, tell me and I'll take it to the vendor instead." That sentence removes the awkwardness of refusing and often gets you a faster, clearer answer than a vague yes. Readers respond faster when they know a no won't cost them the relationship.

When you're the one who might not respond in time, say when you will. A line like "I'll be offline Thursday, so I'll confirm Friday morning" sets a boundary honestly and prevents the sender from chasing you. That's a professional courtesy, not an excuse.

Track what you've promised. If you tell someone you'll reply by Friday, put it in your own task list. Nothing erodes professional trust faster than a stated deadline you miss without a note.

Match Tone to the Relationship, and Read It Aloud Before Sending

Tone is the hardest thing to get right because email strips voice. The same sentence that sounds dry in your head can read as curt in someone's inbox. Read the draft aloud β€” that catches clipped sentences, accidental sharpness, and hedging you didn't intend.

Match formality to the existing thread. If the person writes "Hi Sam," reply "Hi Alex." If they sign off "Best regards," don't reply "Thx." Mirroring the other person's register is one of the most reliable tone tools, and it costs nothing. It also tells the reader you've paid attention.

Watch for the three tone killers: all-caps emphasis, exclamation stacking, and conditional demands. "PLEASE CONFIRM ASAP!!" reads as panic. "You should have told me sooner" reads as blame, even if it's true. If you need to raise a problem, lead with the fix: "The file needs re-exporting β€” can you redo it by noon?" That names the issue without the attack.

Humor lands in about half of email relationships and bombs in the other half. Skip it in first contact, in cross-cultural emails, and anywhere money or deadlines are involved. Save wit for people who've already written back with some.

Run the Pre-Send Check: Six Items in Ninety Seconds

Before you hit send, run the same six checks every time. It takes about ninety seconds and prevents most of the errors that make an email look careless.

1: Recipient field: confirm every address, especially internal versus external, and check for the reply-all trap on threads with large distribution lists. 2: Subject line: does it state the ask or the news in 10 words or fewer? 3: First sentence: does it say what you want or what changed? 4: The ask: is it one line, specific, and paired with a deadline? 5: Attachments and links: are they actually attached, and do the names make sense to the recipient? "Final_Final_v3.docx" reads as chaos. 6: Sign-off and signature: name spelled the way the person spells it, signature block current, no leftover draft text.

When a check fails, fix it before sending. When you can't tell whether a sentence is clear, cut it. The email is usually stronger without it.

A seventh habit for high-stakes messages: save the draft as a draft, not a send. Sleep on anything going to a client, a manager, or a lawyer. The error you catch in the morning is almost always the one that mattered.

Handle the Failure Cases: Wrong Recipient, Angry Reply, and the Escalation

The most common email failure is sending to the wrong person. If it happens, send a short correction immediately: "Correcting an earlier note β€” that was meant for the vendor, disregard." Don't delete and hope. The recipient already has it, and a quick note reads as professional rather than panicked.

If you receive an angry or accusatory reply, wait before responding. Draft in a separate document if needed, then reply within a day with the facts and the next step, not the reaction. "Understood β€” here's what happened and here's the fix" de-escalates better than any apology paragraph. Never counter-accuse in writing.

When an email thread stops producing answers, escalate to a call or a short meeting rather than sending a fourth message. A thread that's gone quiet for a week after two follow-ups isn't going to resolve in text. Say so plainly: "This is getting complicated by email β€” can we take 15 minutes Thursday?"

Finally, respect the reply window. The 2023 Superhuman survey found most professionals expect a response within a day and get fewer than they'd like. If you can't answer fully, acknowledge: "Got it β€” full answer by Thursday." That one sentence buys you time and keeps the relationship intact.

FAQ

How many words should a professional email be?

Aim for 75 to 150 words for a request or update. Anything under 50 words usually lacks context, and anything over 200 gets skimmed or postponed. Long emails work only when the ask and a one-line summary sit at the top, with labeled sections underneath.

Is "Dear" still acceptable in a business email?

Yes, and it's the safer choice for first contact in law, finance, academia, and much of Europe and Asia. "Hi [First Name]" is standard for colleagues and most North American clients. When in doubt, match the greeting the person used with you, not the one you prefer.

Should I reply-all on a company-wide email?

Only when you have something the whole list needs, such as a correction to a date or a status update others are waiting on. Reply-all for a simple acknowledgment clogs inboxes and reads as unprofessional. Reply to the sender alone, then confirm whether they want it shared.

How fast should I respond to a professional email?

Expectations vary, but most professionals check email several times a day and expect a reply within one business day for work messages. If you can't answer fully, send a short acknowledgment with a time you'll follow up. That one-line reply preserves trust better than a silent inbox.

Can I use emojis or "Best" in a professional email?

"Best," "Thanks," and "Regards" are safe closings in nearly every business context. Emojis work in casual internal threads with people you know, and they can misfire across generations, cultures, and formal industries. When unsure, drop them.

What's the biggest mistake in a professional email?

A buried ask. Readers triage fast, and a request that sits in paragraph three gets skimmed past. Put the ask in the first sentence and again as a single line before the signature, paired with a specific deadline. That one structural change fixes most unprofessional-sounding emails.

Should I use a read receipt or follow up if no one replies?

Skip read receipts unless policy requires them; they annoy more recipients than they inform. Follow up once after two to three business days with a fresh, short message that restates the ask and deadline. If that gets no reply, call or escalate rather than sending a third email.

Does a professional email need a signature block?

Yes for external mail and first contact, with your full name, title, company, and one contact method. Internal replies can drop the block after the first message in a thread. Keep the block under five lines and skip inspirational quotes, which read as filler in a work inbox.