Skip to content

Guide

Writing a Professional Email in English When It Isn't Your First Language

A practical breakdown of the four decisions that actually make or break a professional email in English: which greeting fits the relationship, whether the ask is stated early enough to be read, how much context is too much, and whether the formality level matches how well you know the recipient. Written for people whose English is grammatically fine but who keep getting told their emails feel "off."

State your ask in the first two sentences — most non-native writers bury it under throat-clearing context the reader skims past. Match your greeting and sign-off to how well you actually know the recipient, not to a single "correct" formula. Keep paragraphs short, one idea each. A professional English email reads like a clear request, not a careful translation of a private thought.

THE PROCESS

Step by step

Pick a greeting that matches the relationship, not the most formal option you know

Cold outreach with no name: "Hello," not "To Whom It May Concern." Cold outreach with a name: "Dear [First Last]," in conservative industries, "Hi [First Name]," almost everywhere else. Ongoing colleague: first name only — dropping the greeting entirely after the first few replies in a thread is normal, not rude.

Put the ask in the first two sentences

Say what you need before you explain why you need it. If the reader has to scroll to find the request, assume they'll act on whatever they read in the preview pane and nothing else.

Cut the preamble to one line, max

One line of context before the ask is enough. Anything the reader needs to evaluate the request — numbers, deadline, background — goes after the ask, not before it.

Match formality to how you'd actually address this person out loud

If you'd say "hey, quick one" to them on a call, write that register. If you'd open with "good morning, do you have a moment," write closer to that. The mismatch, not the formality level itself, is what reads wrong.

Close with a sign-off at the same formality level as your greeting

"Best," or "Thanks," for people you already work with. "Best regards," or "Kind regards," for most external, semi-formal contact. Save "Sincerely," for genuinely formal, first-contact letters — using it with a colleague you email weekly reads as stiff, sometimes even cold.

Reread once for tone, separately from grammar

Do a pass that only asks "does this sound like how I'd actually talk to this person" — a grammar-clean email can still misjudge the relationship, and that's a different error than a typo.

Starting the email: picking a greeting that actually fits

The greeting isn't about finding the single "most professional" phrase — it's about matching how well you already know the person. "To Whom It May Concern" and "Dear Sir/Madam" read as form-letter openers now, even in fairly formal industries; they signal you don't know who you're writing to, which is sometimes true but rarely worth advertising.

A pattern worth noticing in your own writing: in many languages, the professional default is to address someone by title even in routine correspondence — "Dear Director," "Estimado Profesor." Carried directly into English, this reads as more distant than intended. English professional norm, especially in the US and in flatter/startup cultures: first name once you're already working together, title-plus-last-name mainly for a first cold contact or a genuinely hierarchical context (a judge, a partner you've never met, a government office).

  • First contact, no name available: "Hello," or "Hi there,"
  • First contact, name available: "Hi [First Name]," in most tech/startup contexts; "Dear [First Last]," in law, finance, government, or academia
  • Existing colleague: first name only — "Hi Daniela," — and it's fine to drop the greeting after the first reply in a thread
  • Someone senior you don't know well: "Hi [First Name]," if the org is flat; "Dear [Title] [Last Name]," if it clearly isn't

State the ask before the backstory

Readers skim the first two lines of an email and decide, often unconsciously, whether the rest is worth their full attention. If the ask sits at the bottom of a fourth paragraph, you're betting on the reader's patience — a bet you usually lose, especially with anyone senior or busy.

The habit of building up to a request — explaining the situation fully before naming what you want — is a reasonable instinct in plenty of languages and cultures, where a direct ask up front can feel presumptuous. In English workplace writing it reads as unclear, not humble.

Compare: "I hope you are doing well. I wanted to reach out because we've been working on the Q3 report and there have been some issues with the data from finance arriving late, and our manager also mentioned the deadline might move, so I was thinking maybe we should discuss this. Could we possibly find some time to talk about the report status?" versus: "Can we move the Q3 report deadline by three days? Finance's data arrived late and it's pushed our review into next week — happy to explain more if useful." Same facts, a fraction of the reading effort.

How much context is enough (the over-long preamble problem)

One line of context before the ask is usually enough. "I hope this finds you well" as a single opening line is harmless — it becomes a problem when it's followed by two more sentences of pleasantries, a full recap of prior conversations, and a restated project history, all before the actual point.

If that pattern feels automatic, it's often a transferred formula: a formal opening line that's standard in business correspondence in your first language (common in Russian, French, and Spanish formal writing, among others) doesn't need to disappear, but it needs to shrink to one line, with everything the reader needs to evaluate the request moved after the ask — as a short list if there's more than one fact, not stacked into another paragraph of prose.

Matching formality to the relationship, not to "correct" English

This is the mistake that causes the most confusion, because it isn't a grammar error and spellcheck won't catch it. There are two failure directions. Too formal with someone you actually know well — "Dear Mr. Chen, I would be most grateful if you could kindly consider..." sent to a manager you talk to daily — reads as distant, and in English office culture, unexpected formality can even register as passive-aggressive. Too casual with someone senior or external — dropping into slang, no capitalization, heavy abbreviation with a client or a VP three levels up — reads as not taking the relationship seriously.

The fix isn't a formality chart; it's a translation test. Write the email in roughly the register you'd use if this person called you right now. If you'd say "hey, quick thing," write that. If you'd say "good morning, do you have a moment," write closer to that.

Closing the email without overthinking it

Sign-offs sort roughly by formality: "Best," and "Thanks," are casual-to-neutral and the safe default with people you already work with. "Best regards," and "Kind regards," are neutral-to-formal and cover most external, semi-formal contact. "Sincerely," is worth reserving for genuinely formal or first-contact letters — using it with a colleague you've emailed twenty times this month tends to read as stiff rather than polite.

It's also completely normal in English to drop the sign-off entirely by the third or fourth reply in a thread; not every message needs to be a complete letter.

If you're genuinely unsure whether a draft reads too stiff or too casual for a specific relationship, that's a formality-matching problem more than a vocabulary one — it's the kind of formality mismatch a tone preset (direct, warm, formal) is built to fix — you pick the register and Copynote rewrites toward it, which is one of the reasons Copynote treats tone as a separate control from grammar rather than folding both into one generic "fix" pass.

FAILURE MODES

What goes wrong, and what to do instead

An over-long preamble — several sentences of context, history, or pleasantries before the actual point.

Cut to one line of context before the ask. Move any facts the reader needs to evaluate the request to after the ask, as a short list if there's more than one.

No clear ask at all — the email reads as a status update or a vent, and the reader isn't sure what to do with it.

End the first paragraph with a direct question or explicit next step: "Can you approve X by Friday?" not "I wanted to share where things stand."

Wrong formality level for the relationship — textbook-formal with a colleague you talk to daily, or too casual with a client or senior stakeholder.

Write in the register you'd actually use if this person called you right now, not the most "correct"-sounding English you know.

A politeness formula translated word-for-word from your first language — heavy apologetic hedging, or an ornate closing line that has no natural English equivalent.

Use English's own politeness markers (please, a direct-but-softened ask) instead of importing your language's hedge structure sentence by sentence.

Greeting and closing at mismatched formality levels — "Hi Sarah," to open, "Sincerely yours," to close.

Pick one formality level and keep the greeting and sign-off on it; a mismatch reads as uncertain rather than as a deliberate style choice.

Questions writers ask about this

Is "Dear [Name]" always the safest greeting for a work email?

No — it's safe for a first, fairly formal contact, but it starts to read as stiff with someone you already email regularly. Once you're in an ongoing exchange, first name only ("Hi Daniela,") is the more natural default in most English-speaking workplaces.

Is it rude to state my request in the first sentence?

In English professional writing, no — the opposite is usually the problem. Readers skim the first two lines and often miss a request buried in paragraph three. A direct ask followed by brief context reads as clear and respectful of the reader's time, not as abrupt.

How do I know how formal to be with someone I've never emailed before?

Use one notch more formal than you'd guess, then match whatever register they use in their reply. "Hi [First Name]," plus a neutral sign-off ("Best regards,") is a safe opening move in most industries outside law, government, and academia, where title-plus-last-name first contact is still standard.

Should I mention that English isn't my first language?

Generally no, unless it's directly relevant (asking someone to clarify jargon, for example). It doesn't change how the email should be structured, and flagging it upfront can read as an apology for something the reader wasn't going to notice.

How short should a professional email actually be?

Short enough to be read on a phone without scrolling, for most routine requests: an ask, one line of context, and a next step. Longer is fine when the topic genuinely needs it — but check whether the length is coming from the content or from preamble that could be cut.

Knowing the moves
is half of it

The other half is an editor that keeps meaning, tone and grammar in one pass. Copynote is in beta — apply and we’ll reach out as spots open.

Apply for beta

*Beta opens this season — starting with people who write at work in a second language.

The Copynote writing workspace