How To Start An Email

How to start an email (quick definition and default format)

Start an email with a clear subject line, an appropriate greeting, and one purpose-driven opening sentence. Choose the greeting based on your relationship, the formality level, and whether you know the recipient’s name.

I can usually tell, within the first eight words, whether an email will get a reply. Not because I have special intuition. Because most people start emails in one of two ways: they either sound like a robot (“To whom it may concern…”) or they sound like a text message sent to the wrong person (“hey quick question”).

The counterintuitive part: you do not start an email by being friendly. You start by being easy to respond to. Friendly helps. Clarity gets you answered.

The mistake that makes your first line feel “off”

I see this constantly in internal threads and customer emails: the sender writes a warm greeting, then wanders for three sentences before saying why they wrote. The recipient has to hunt for the ask. That is where replies die.

Bad openers usually have one of these problems:

• They bury the point. “I hope you’re doing well. I just wanted to reach out because…” (and the reason arrives 80 words later).
• They over-apologize. “Sorry to bother you” before they even ask anything.
• They assume context the recipient does not have. “Following up on our conversation” (which conversation, when, about what).
• They start with urgency without proof. “ASAP” in the first line for a non-urgent request.

Here is what works in the real inbox. Your first line should do one job: tell the recipient what this email is about, in plain language, with just enough context to act.

Pick a greeting that matches the relationship (not your mood)

People overthink greetings, then underthink the sentence that follows. Still, the greeting matters because it sets expectations. A too-formal greeting can make a simple request feel heavy. A too-casual greeting can make you look careless, especially when you are asking for time, money, approval, or a favor.

If you know the person’s name

• Neutral and safe: “Hi Priya,”
• More formal: “Hello Ms. Chen,”
• Warm but still professional: “Hi Jordan, hope your week’s going well.” (only if you actually have rapport)

My rule: default to “Hi [First Name],” unless the context is clearly formal (legal, HR, executive escalation, external partner with strict etiquette). If you are not sure, choose “Hello [First Name],” because it reads slightly more formal without feeling stiff.

If you do not know the person’s name

• Good: “Hello,”
• Good for support queues: “Hi there,”
• Avoid unless required: “To whom it may concern,” (it signals you did not try)

If you can find the name in 20 seconds (signature, website, LinkedIn, prior thread), do it. You get a small but real lift in replies.

Four opening lines that consistently get replies (with exact phrasing)

I keep a little stash of opening lines for different situations. Not templates you copy forever. More like reliable starting moves that reduce friction.

1) The direct request opener

Use when: you need a decision, approval, or quick action.

Subject: “Approval needed. Q2 webinar landing page copy”

Greeting + first line:
“Hi Sam,
Can you approve the attached landing page copy by Thursday at 3 pm ET?”

Notice what is missing. No preamble. No dramatic urgency. Just a clear ask and a deadline.

2) The context-first opener (for sensitive or complex threads)

Use when: the recipient may not remember the situation, or multiple stakeholders are involved.

First line:
“Hello Daniela,
I’m emailing about the invoice discrepancy on PO 10481 (the March shipment to Austin).”

This line earns the right to be longer later. You anchored the topic with something searchable.

3) The meeting opener that does not waste time

Use when: you are scheduling, rescheduling, or confirming.

First line:
“Hi Miguel,
Are you available for a 20-minute call Tuesday or Wednesday to finalize the rollout timeline?”

People respond faster when you offer two options and a purpose. If you have Calendly, you can add it after the options, not instead of them.

4) The follow-up opener that does not sound passive-aggressive

Use when: you already emailed, you need an answer, and you want to stay polite.

First line:
“Hi Aisha,
Quick follow-up on the contract redlines I sent Monday. Are you able to share feedback by end of day Thursday?”

“Quick follow-up” is fine if you include what you are following up on and a clear next step. “Just circling back” often reads like you are floating with no point.

The 30-second checklist I use before I hit send

I write a lot of emails where the opener is the difference between “Sure” and silence. When I am not getting replies, it is usually because I failed one of these checks.

1. Is the subject line specific enough to scan? If it could describe 50 different emails, it is too vague.
2. Does the greeting match status and context? “Hey” to a new CFO contact is a gamble.
3. Does the first line name the topic? A person should know what this is about without scrolling.
4. Is the ask explicit? “Let me know your thoughts” is not an ask. “Please confirm if we should proceed with Option B” is.
5. Did I include the minimum context needed to decide? One sentence often does it. Three is fine. Nine is not.

Users should verify recipient names, titles, and deadlines before sending time-sensitive or formal messages. A perfect opener cannot fix a wrong name or incorrect date.

Starting lines that sound polite but quietly sabotage you

I have watched smart people lose momentum with these openers. They feel courteous. They also create work for the reader.

• “I hope this email finds you well.” Not offensive. Just empty. If you use it, follow immediately with the point: “I’m reaching out to confirm the delivery date for Order 8832.”
• “Sorry to bother you…” It frames your request as an imposition. If you need something, ask cleanly.
• “Per my last email…” Sometimes you are tempted. I get it. It escalates tension fast. Use “Following up on…” and restate the needed next step.
• “Just checking in.” Checking in about what. Replace with a noun: “Checking in on the pricing approval for Acme.”

If you want an opener that is both human and useful, tie your nicety to something real. “Hope your trip to Chicago went smoothly. I’m emailing to confirm the final attendee list for Friday.” That reads like an actual person. It also gets to the point.

How I start emails in three common high-stakes situations

Most advice ignores the emotional reality of email: sometimes you are nervous, sometimes you are annoyed, sometimes you are asking for something you do not fully deserve yet. The opener has to handle that.

Cold outreach (you have no relationship)

You cannot start with “Hope you’re doing well” and expect magic. You need relevance.

Subject: “Question about your Q3 onboarding flow”

Opener:
“Hi Nora,
I noticed you’re hiring for Customer Ops. Are you the right person to discuss onboarding process improvements?”

This gives an easy out (“not the right person”) and an easy yes.

Asking for a favor (you are consuming someone’s time)

Do not hide that it is a favor. Name the time cost and make the exit painless.

Opener:
“Hi Dev,
Could you review my one-page proposal and share two or three edits by Friday? If you’re swamped, no worries, I can ask someone else.”

Delivering a correction (you need to fix something without blame)

Start with the fix, then provide context. Not the other way around.

Opener:
“Hello team,
Correction: the deadline for the client deck is Wednesday at 11 am ET, not Thursday.”

That line prevents downstream confusion. Then you can add: “The calendar invite has been updated.”

Using AI without sending AI-sounding openers

I use AI Email Writer style tools for drafts when I am tired or when I need five variations fast. The risk is sameness. AI tends to start with polite fog. You can fix that with one instruction: “Write the first line as a specific purpose statement with a clear ask.”

If you want a structured starting point for client-facing messages, a Professional Email Writer workflow usually nudges the tone into “confident and clear” instead of “overly formal.” For stricter scenarios (HR, legal, government, finance), a Formal Email Generator can help you start correctly without sounding like you swallowed a handbook. If you need multiple options for the same scenario, an AI Email Generator can produce variants so you can pick the one that feels like you.

My habit: I generate three openers, then I manually edit one sentence to add a detail only I would know (a date, an item number, a meeting reference). That tiny specificity is what makes it sound real.

Copy-and-use opener library (swap the bracketed parts)

• “Hi [Name], I’m reaching out to confirm [specific detail] for [project].”
• “Hello [Name], can you share an update on [deliverable] and the expected ETA?”
• “Hi [Name], do you want me to proceed with [Option A] or [Option B]?”
• “Hello, I’m contacting you about [issue] on [account/order/ticket number].”
• “Hi [Name], thanks for [recent action]. Next step on my side is [X]. Do you need anything else from me?”

If you only change one thing after reading this, change your first line. Make it a label plus a request. People do not reply to vibes. They reply to clear next steps.