Chapter 02

商务邮件全攻略

第二章 · 主题行、开头、12 类邮件模板,全部可直接复制使用。

2.1 主题行:决定邮件是否被打开

主题行是最便宜也最被低估的写作环节。一封邮件能不能让对方在 30 秒内回复,60% 取决于主题行。优秀的主题行有三个特征:具体可搜索带行动

为什么
Hello[Action needed by Fri] Q3 budget approval对方扫一眼就知道要做什么、什么时候
QuestionQuick question — Stripe webhook timeout“Quick question” 暗示低成本
UpdateStatus: Project Atlas — on track for Sept 15包含项目名 + 状态 + 日期
MeetingInvite: Roadmap sync, Tue 10am PT (30min)包含时间、时区、时长
FYIFYI: Customer A churned — postmortem inside说清是什么 FYI,对方决定是否细读

常用前缀(写在主题行最前,方便筛选):

2.2 开头称呼:Hi / Hello / Dear 怎么选

称呼使用场景正式度
Hi Alex,同事、合作过的客户、招聘官Neutral
Hello Alex,第一次联系,比 Hi 略正式Neutral
Dear Alex,正式商务、求职、Cold emailFormal
Dear Mr. Smith,不知名陌生人、合规、法务Formal
Dear Hiring Manager,不知道收件人名字时Formal
Hi team, / Hi all,群发同事Neutral
Hey Alex,熟人、内部 Slack 之外的轻松邮件Casual
注意

不要写 Dear Sir or Madam,To whom it may concern,——在 2026 年的英语世界,这两个表达已被普遍认为过时且懒惰。花 30 秒在 LinkedIn 找到对方名字。

2.3 开篇句:第一句话决定阅读体验

第一句话的任务是建立连接 + 声明意图。下面是 5 类常用开篇。

// 第一次联系
Hope you're doing well — my name is Lei, I lead growth at Studio.

// 跟进
Following up on my note from last Tuesday.

// 介绍
Introducing you two — Sarah, meet Tom (cc'd). Tom runs payments at Acme.

// 紧急
Heads up — we just hit a P1 issue affecting checkout.

// 道歉
Apologies for the delay in getting back to you.
禁忌开篇

不要用 I hope this email finds you well 作为开篇——它太被滥用,已经成为 ChatGPT 风的标志。换成 Hope your week's off to a good start 或干脆省略寒暄。

2.4 12 类常见邮件模板

① 请求 Request

Subject: [Action needed by Thu] Sign-off on Q3 budget

Hi Sarah,

Could you take a look at the attached Q3 budget and let me know if
you're comfortable approving it by Thu EOD? Two items I'd like your
read on:

  1. The 18% bump in tooling — driven by Datadog renewal.
  2. New headcount for the platform team (1 SRE).

Happy to walk through on a quick call if easier.

Thanks,
Lei

② 回复 Reply

Hi Tom,

Thanks for sending this over. Quick reactions:

  • Section 2 looks good to me.
  • On Section 3, I'd push back gently on the timeline — Q4 feels
    tight given the Black Friday freeze. Could we move to Q1?
  • Section 4: deferring to Mike since he owns billing.

Let me know if you'd like to discuss live.

Best,
Lei

③ 追单 Follow-up(对方没回)

// 第一次追单(3-5 天后)
Subject: Re: Q3 roadmap sync

Hi Sarah,

Just bumping this up in your inbox — happy to wait if you're in
the middle of something. Let me know if there's anything I can
do to help unblock.

Thanks,
Lei

// 第二次追单(一周以上)
Subject: Following up — anything I can do?

Hi Sarah,

I know things are busy. Should I assume this is a no-go for now,
or would it help if I sent a shorter version? Either is fine.

Best,
Lei

④ 拒绝 Decline

Hi Mark,

Really appreciate you thinking of me for this. After looking at
my plate over the next few weeks, I don't think I can take it
on without dropping the ball on the launch.

If timing shifts, I'd love to revisit. In the meantime, I'd
suggest reaching out to Priya — she has deeper context on the
billing module anyway.

Thanks for understanding.

Lei

⑤ 道歉 Apology

Hi Sarah,

I owe you an apology — the report I sent yesterday had the
wrong attribution numbers (pulled the staging dataset by mistake).
The corrected version is attached.

To prevent this from happening again, I've added a check in our
pipeline that flags non-prod data sources before send.

Thanks for your patience.

Lei
道歉公式

Apology = 承认 + 说明影响 + 修复动作 + 防复发。不要解释一长串“为什么不是我的错”,那会让事情更糟。

⑥ 感谢 Thank you

Hi Tom,

Just wanted to say thanks for jumping on the migration call last
night — staying up till 11pm PT made the difference. The cutover
landed clean and we're seeing 30% lower latency on the new cluster.

Owe you a coffee.

Lei

⑦ 介绍 Intro(双连介绍)

Subject: Intro — Sarah (Acme) ↔ Tom (Studio)

Hi both,

Pleasure to introduce you two — moving you to BCC so your inbox
isn't cluttered.

Sarah, meet Tom — Tom leads infra at Studio and has been thinking
about the same Postgres scaling issues you mentioned last week.

Tom, Sarah is the head of platform at Acme. They just went through
a similar migration to Aurora and have great learnings to share.

I'll let you take it from here.

Best,
Lei

⑧ 转交 Forward / Loop in

Hi Tom,

Looping in Sarah (cc'd) since this falls under her team's scope.

Sarah — Tom is asking about the SAML SSO timeline for enterprise
customers. Could you share the latest from your roadmap?

Thanks,
Lei

⑨ 请假 PTO

Subject: PTO — Sept 9-13 (out of office)

Hi team,

I'll be out Sept 9-13 for vacation. Coverage:

  • On-call: swapped with Priya.
  • Standups: Mike will run.
  • Urgent issues: page Priya via PagerDuty.

I'll be back online Mon Sept 16. Slack will be silent unless
something breaks.

Thanks,
Lei

⑩ 辞职 Resignation

Subject: Notice of resignation

Dear Sarah,

I'm writing to let you know I'll be leaving Studio. My last
day will be Friday, Oct 17, giving us four weeks for transition.

I'm incredibly grateful for the past three years here — the
team and the work have shaped me as an engineer. I'll do
everything I can to make the handoff smooth: documenting the
billing service, training Priya on the on-call runbook, and
wrapping up the Q3 milestones I committed to.

Happy to chat whenever works for you.

With appreciation,
Lei
辞职信原则

不抱怨、不解释跳槽去哪、不夸张感激;给出具体最后日期 + 交接计划。这封邮件以后会进 HR 档案,写得越克制越职业。

⑪ 会议邀请 Meeting invite

Subject: Roadmap sync — Tue 10am PT (30 min)

Hi Sarah, Tom,

Setting up 30 min next Tue to align on the Q4 roadmap. Goal:

  • Walk through 3 candidate themes.
  • Decide on top 2 by end of call.

Pre-read: roadmap doc (link). 5 min skim.

Calendar invite to follow.

Lei

⑫ 合同跟进 Contract follow-up

Hi Sarah,

Following up on the MSA — legal sent the redlines back yesterday.
Two outstanding items:

  • Section 7 (data retention): we'd need 30 days, not 14.
  • Section 12 (auto-renew): comfortable with 60 days notice.

Could your team turn this around by Wed? Aiming to countersign
end of week.

Thanks,
Lei

2.5 签名规范

签名是邮件的“名片”。原则:精简、信息密度高、不要营销标语。

// 极简(适合内部)
Lei

// 标准(适合外部)
Lei Wang
Engineering Lead, Studio
+1 (415) 555-0123
linkedin.com/in/leiwang

// 不要这样
Lei Wang
Senior Software Engineer at Studio Inc.
"Innovate, Inspire, Iterate"
[一张笑脸照片]
[长长的免责声明]
[Twitter / Instagram / TikTok 全家桶链接]
本章心法

邮件不是作文,是工作工具。它要回答三个问题:谁在说?说什么?我要做什么?用 30 秒能让对方答出这三个问题,邮件就成功了。

2.6 本章小结