约8分钟阅读
电子邮件是职场沟通的支柱。无论你是在求职、与同事协调、联系客户,还是在会后跟进,你邮件的结构和语气都决定了你的信息会被怎样接收。一封结构良好的邮件会被阅读、被理解、被付诸行动。一封结构糟糕的邮件则会被匆匆扫过、被误解,或者被忽略。
本节讲解职场电子邮件必不可少的组成部分、怎样有效地组织它们,以及让你的信息清楚可信的语气和格式原则。
每一封职场电子邮件都由五个结构部分组成。把它们想象成你这条信息的骨架。当五个部分都齐全、都写得用心时,你的邮件在读者还没读懂内容之前,就已经传达出了专业感。
主题行是你邮件中最重要的一行。它决定了你的信息会不会被打开、什么时候被打开,以及读者在心里怎样给它归类。主题行含糊或者干脆没有,是最常见的邮件错误之一。
好的主题行做到了什么:
行之有效的主题行公式:
| 公式 | 例子 |
|---|---|
| 话题 + 行动 | Budget Report - Review by Friday |
| 项目 + 进展 | Website Redesign: Phase 2 Complete |
| 请求 + 背景 | Meeting Request: Q3 Planning Discussion |
| 状态 + 细节 | Action Required: Client Contract Approval |
| 跟进 + 所指事项 | Follow-Up: Interview on March 10 |
主题行的常见错误:
| 错误 | 为什么行不通 | 更好的版本 |
|---|---|---|
| "Hi" or "Hello" | 没有任何信息。会被淹没在收件箱里。 | "Introduction: Sarah Chen, Marketing Consultant" |
| "Quick question" | 每封邮件都可能是「一个小问题」。 | "Question About Invoice #4892 Payment Terms" |
| "Important!!!" | 被用滥了,也很含糊。读起来像垃圾邮件。 | "Deadline Change: Report Due Wednesday Instead of Friday" |
| "FYI" | 没有告诉读者要让他们知道的是什么。 | "FYI: Office Closed December 24-26" |
| (空白) | 很多垃圾邮件过滤器会标记没有主题的邮件。有些读者不会打开它。 | 始终写上主题行。 |
长度指南: 让主题行保持在 60 个字符以内,以便在移动设备上完整显示。把最重要的词放在前面,因为在较小的屏幕上,末尾的部分可能会被截掉。
问候语为整封邮件定下基调。它表明了正式程度,以及你和读者的关系。
正式的问候语(用于不太熟悉的人、上级或外部联系人):
半正式的问候语(用于同事、已经建立的职场关系):
随意的问候语(用于关系密切的同事、团队内部沟通):
职场电子邮件中要避免的问候语:
| 问候语 | 问题 |
|---|---|
| Hey(单独使用,不带名字) | 对大多数职场语境来说太随意 |
| To Whom It May Concern | 过时且缺乏人情味。尽量找到收件人的名字。 |
| Dear Sir/Madam | 过时了。用 "Dear Hiring Manager" 或者对方真实的名字。 |
| Yo / Sup / Hiya | 在职场电子邮件中从来都不合适 |
| 完全没有问候语 | 显得唐突而不礼貌 |
当你不知道收件人的名字时: 使用对方的头衔或角色:"Dear Admissions Office"、"Dear Hiring Committee"、"Dear Customer Support"。这比 "To Whom It May Concern" 更具体,也更亲切。
正文是你的信息所在的地方。职场电子邮件的正文遵循一个一致的内部结构:
开头句——说明你为什么写这封邮件。不要让读者去猜。
中间部分——提供必要的细节、背景或解释。合乎逻辑地组织信息:
结束句——说明下一步、提出一个请求,或者表示感谢。
「一屏法则」: 尽量让邮件正文不用滚动就能完整看到。如果你的信息需要不止一屏,就想一想其中有些信息是否应该放进附件里。长邮件会被匆匆扫过,而不是被认真阅读。
结束语在正式程度上与问候语相呼应。它是一种社交惯例,标志着信息的结束,并留下最后的印象。
正式的结束语:
半正式的结束语:
随意的结束语(仅用于内部沟通):
要避免的结束语:
| 结束语 | 问题 |
|---|---|
| Love, | 在职场电子邮件中从来都不合适 |
| XOXO | 在职场电子邮件中从来都不合适 |
| Thx | 缩写得太厉害;显得草率 |
| Sent from my iPhone(作为你唯一的结束语) | 这不是结束语。在它上面加上一个像样的落款。 |
| 完全没有结束语 | 显得唐突 |
你的电子邮件签名档就是你的电子名片。它应该包括读者识别你、或者通过其他渠道联系你可能需要的基本信息。
标准的职场签名档格式:
Full Name
Job Title
Company/Organization Name
Phone Number
Email Address (optional, since they already have it)
Website or LinkedIn (optional)
例子:
Sarah Chen
Senior Marketing Analyst
BrightPath Consulting
+1 (555) 234-5678
www.brightpathconsulting.com
签名档指南:
即使是一封写得好的邮件,如果排版成一堵文字墙,也可能会失败。职场电子邮件应该在视觉上便于浏览。
让段落保持简短——最多两到四个句子。在电子邮件中,一个在文章里算是正常长度的段落,会显得又长又密。段落之间的空白让读者的眼睛有地方歇息。
难以阅读(一整块密集的文字):
I wanted to update you on the Henderson project. We completed the initial research phase last week and have begun drafting the proposal. There are a few issues I need to flag. First, the budget estimate from the vendor came in 15% over our projection. Second, the timeline they proposed would push our delivery date back by two weeks. I think we need to discuss these issues before proceeding. Could we schedule a call this week?
易于阅读(分成了几个短段落):
I wanted to update you on the Henderson project. We completed the initial research phase last week and have begun drafting the proposal.
I need to flag two issues:
- The vendor's budget estimate came in 15% over our projection.
- Their proposed timeline would push our delivery date back by two weeks.
Could we schedule a call this week to discuss next steps?
只要你有三个或更多的事项、行动或论点,就使用项目符号列表或编号列表。列表比嵌在句子里的事项更容易浏览。
嵌在句子里(更难处理): For the meeting, please bring your laptop, the Q3 report, the updated budget spreadsheet, and any notes from the client call last Thursday.
列成清单(更容易处理): For the meeting, please bring:
少用粗体,只用它来突出关键信息:截止日期、待办事项或关键细节。不要把整个句子或整个段落都加粗——当所有东西都被强调时,就什么都没有被强调。
The revised deadline is Friday, March 15 at 5:00 PM. Please submit all materials to shared-drive/Q3-reports.
语气是你邮件的个性。在职场沟通中,合适的语气传达出能力、礼貌和清晰。
要直接,但不要生硬。 清楚地说明你的目的,但不要失礼。
| 生硬 | 直接而礼貌 |
|---|---|
| Send me the report. | Could you please send me the report by Thursday? |
| You made a mistake on page 3. | I noticed a discrepancy on page 3 — could you take a look? |
| This is wrong. | I believe there may be an error here. Could we review it together? |
要简洁,但不要简慢。 让邮件保持简短,但要包含足以让人理解的背景和足以表示尊重的礼貌。
| 简慢 | 简洁而礼貌 |
|---|---|
| No. | Unfortunately, I am unable to accommodate that request at this time. Would an alternative date work? |
| See attached. | Please find the requested document attached. Let me know if you have any questions. |
要积极,但不要不诚实。 尽可能以建设性的方式呈现信息,但不要误导。
| 消极的表述 | 积极的表述 |
|---|---|
| We failed to meet the deadline. | We are finalizing the project and expect to deliver by Wednesday. |
| You forgot to include the data. | Could you add the data to the report when you get a chance? |
| 情境 | 语气上的做法 |
|---|---|
| 提出请求 | 礼貌,清楚地说明你需要什么、什么时候需要 |
| 传达坏消息 | 有同理心,以事实为依据,提出下一步 |
| 跟进 | 友好、简短,提及最初的那条信息 |
| 回应投诉 | 承认问题,必要时道歉,以解决问题为导向 |
| 自我介绍 | 亲切、专业,说明你们之间的联系 |
| 感谢某人 | 真诚,具体说明你感谢对方的是什么 |
不同的目的需要不同的长度:
| 目的 | 目标长度 |
|---|---|
| 简短的确认或回执 | 1-2 个句子 |
| 简单的请求或问题 | 3-5 个句子 |
| 进展更新或状态报告 | 5-10 个句子 |
| 详细的提案或解释 | 10-15 个句子(更长的内容考虑放进附件) |
| 冷启动式联系或自我介绍 | 5-8 个句子 |
一般的规则是:越短几乎总是越好。 忙碌的职场人士每天会收到几十甚至几百封邮件。直奔主题,就是尊重他们的时间。
| 组成部分 | 关键原则 |
|---|---|
| 主题行 | 具体、以行动为导向、60 个字符以内 |
| 问候语 | 让正式程度与彼此的关系和语境相匹配 |
| 正文 | 开头说明目的,细节有条理,结尾清楚 |
| 落款 | 与问候语的正式程度相匹配 |
| 签名档 | 4-6 行,基本的联系信息 |
| 排版 | 段落简短,多个事项用列表,少用粗体 |
| 语气 | 直接而礼貌,简洁而有礼 |
| 长度 | 在完整的前提下尽可能简短 |
约9分钟阅读
学习邮件结构的最好方法,是研读真实的例子。本节针对五种常见的职场目的——请求、跟进、自我介绍、投诉和致谢——把结构糟糕的邮件和结构良好的邮件并排比较。每一组都作了分析,让你确切地看到差别在哪里。
请求邮件要求读者做某件事——提供信息、批准一个决定、安排一次会议,或者分享一份资源。它们是最常见的职场邮件类型,而当请求被埋没、含糊不清或者没有截止日期时,它们也最常失败。
主题: Hey
Hi,
So I was wondering if you could maybe help me out with something. I've been working on this project and there are some things I need. It would be great if you could get back to me when you get a chance. There's no rush but it would be nice to have it soon.
Thanks! Alex
问题在哪里:
主题: Request: Q3 Sales Data for Annual Report
Hello David,
I am preparing the annual report and need the Q3 sales data for the North American region. Specifically, I am looking for:
- Monthly revenue totals (July, August, September)
- Year-over-year comparison for each month
- Top 10 accounts by revenue
Could you send this by Thursday, March 13 so I can include it in the draft before the review meeting on Monday?
If you have any questions about the format or scope, please let me know.
Best regards, Alex Martinez Financial Analyst, Reporting Team ext. 4521
好在哪里:
跟进邮件用来查问你之前请求过的事情、提及过去的一次谈话,或者委婉地提醒某人兑现承诺。难点在于跟进的时候不显得不耐烦或被动攻击。
主题: STILL waiting
Hi,
I sent you an email last week about the budget report and I haven't heard back. I really need this ASAP. I don't understand why it's taking so long. This is the third time I've had to follow up. Can you PLEASE just send it?
Thanks.
问题在哪里:
主题: Follow-Up: Budget Report Request (Sent March 5)
Hello Jennifer,
I hope you are doing well. I am following up on my email from March 5 regarding the Q3 budget report. I understand you may have a full workload, but I wanted to check whether you have had a chance to compile the figures.
The report is needed for the executive review meeting on Friday, March 21. If possible, could you send the data by Wednesday, March 19 to allow time for formatting?
If there are any obstacles or if you need additional information from me, please do not hesitate to let me know. I am happy to help however I can.
Thank you for your time, Alex Martinez Financial Analyst, Reporting Team ext. 4521
好在哪里:
自我介绍邮件是你给人的第一印象。在联系一个你以前从未打过交道的人时——潜在的客户、人脉联系人、新同事,或者别人推荐给你的人——就会用到它。
主题: Hello!
Hey there!
My name is Alex and I work at a marketing company. I found your profile online and thought it would be cool to connect. I do a lot of different stuff — social media, content, SEO, analytics, branding, you name it. We should totally talk sometime. Let me know if you're interested!
Cheers, Alex
问题在哪里:
主题: Introduction: Marketing Consultant Specializing in B2B Content
Dear Ms. Nakamura,
My name is Alex Martinez, and I am a content marketing consultant at BrightPath Consulting. I came across your recent article on B2B lead generation in Marketing Weekly, and I was impressed by your insights on content-driven customer acquisition.
I specialize in helping mid-size B2B companies develop content strategies that generate qualified leads. Over the past two years, I have helped clients increase their inbound lead volume by an average of 35%.
I would welcome the opportunity to discuss how our services might complement your team's efforts. Would you be available for a brief 15-minute call next week?
Thank you for your time and consideration.
Best regards, Alex Martinez Content Marketing Consultant BrightPath Consulting +1 (555) 234-5678 alex.martinez@brightpath.com
好在哪里:
投诉邮件需要坚定而不咄咄逼人,具体而不东拉西扯,并且以解决问题为导向,而不只是发泄。一封写得好的投诉邮件,远比一封怒气冲冲的邮件更有可能得到积极的回应。
主题: TERRIBLE SERVICE!!!
This is absolutely unacceptable!!! I ordered a laptop from your website THREE WEEKS AGO and it STILL hasn't arrived. Your customer service is a joke. I called twice and both times I was put on hold for like 45 minutes before someone picked up, and they couldn't even tell me where my order was. This is the worst experience I've ever had with any company. I want a full refund RIGHT NOW or I'm going to tell everyone I know to never buy from you.
VERY unhappy customer
问题在哪里:
主题: Unresolved Delivery Issue — Order #LP-78432
Dear Customer Service Team,
I am writing regarding Order #LP-78432, a laptop computer placed on February 15, 2026, with an estimated delivery date of February 22. As of today, March 8, the order has not arrived, and the tracking information has not been updated since February 20.
I have contacted your support line twice (February 28 and March 4), but the representatives were unable to provide information on the shipment's status or an updated delivery estimate.
I would appreciate it if you could:
- Investigate the status of my shipment and provide an updated delivery date
- Arrange expedited shipping if the original package has been lost
- Process a full refund if delivery cannot be confirmed within 5 business days
My account email is alex.martinez@email.com and my contact number is +1 (555) 234-5678. I am available during business hours and happy to provide any additional information needed to resolve this matter.
Thank you for your prompt attention to this issue.
Sincerely, Alex Martinez
好在哪里:
致谢邮件能加强职场关系。在面试、会议、帮忙、合作之后,或者在任何有人帮助了你、为你花了时间的情况下,都可以发送致谢邮件。写好致谢邮件的关键在于具体——泛泛的感谢让人觉得空洞。
主题: Thanks
Hi,
Thanks for the meeting today. It was great. Let me know if you need anything.
Best, Alex
问题在哪里:
主题: Thank You — Productive Discussion on Q4 Marketing Strategy
Dear Rachel,
Thank you for taking the time to meet with me this afternoon. I found our discussion about the Q4 marketing strategy extremely valuable, particularly your insights on shifting budget allocation toward video content.
I have already started drafting the revised content calendar based on the priorities we discussed. I will send you a first draft by Friday for your review.
I also wanted to follow up on your suggestion to connect with James Park in the analytics team. I will reach out to him this week to set up a meeting.
Thank you again for your guidance and support. I look forward to continuing our collaboration.
Best regards, Alex Martinez Content Marketing Specialist ext. 4521
好在哪里:
把正面的例子放在一起看,可以看出几个模式:
| 模式 | 为什么行之有效 |
|---|---|
| 具体的主题行 | 读者在打开之前就知道邮件是关于什么的 |
| 带名字的问候语 | 个人化,表示尊重 |
| 第一句就说明目的 | 不需要猜 |
| 具体的细节(日期、数字、名字) | 显示出专业,也让行动成为可能 |
| 项目符号或编号列表 | 便于浏览,便于执行 |
| 清楚的下一步或请求 | 读者确切地知道该做什么 |
| 专业的结束语和签名档 | 留下一个精致的最后印象 |
再看反面的例子:
| 反模式 | 为什么行不通 |
|---|---|
| 含糊的主题行 | 会被淹没,以后也搜不到 |
| 没有问候语或问候语过于随意 | 从一开始就定错了基调 |
| 目的被埋没或者没有说出来 | 读者得费力去弄清你想要什么 |
| 情绪化或咄咄逼人的语言 | 损害关系,降低对方的合作意愿 |
| 没有具体的细节 | 即使读者愿意,也无法采取行动 |
| 没有清楚的截止日期或下一步 | 这条信息会被无限期地往后放 |
结构不是可有可无的。 每一封职场电子邮件都需要清楚的主题、问候语、有条理的正文、结束语和签名档。
要具体。 含糊的邮件会造成困惑,还需要再发邮件去澄清,浪费每个人的时间。
语气决定结果。 同一个请求,写得咄咄逼人和写得专业得体,得到的回应会截然不同。
同理心能改善结果。 承认读者的视角——他们的工作量、他们受到的限制、他们的专业知识——会让他们更愿意帮忙。
每一封邮件都是一份职场文件。 像对待一份报告或一次演讲展示那样用心对待邮件。在你发出之后很久,它们还在收件人的收件箱里代表着你。
约6分钟阅读
本节是一份职场电子邮件写作的速查指南。把它加入书签,每当你需要一个模板、一份清单,或者对最佳做法的提醒时,就回来查阅。
这些模板为常见的邮件类型提供了结构框架。把方括号里的占位内容换成你具体的细节。
Subject: Request: [What You Need] — [Context/Project Name]
Dear [Name],
[One sentence: why you are writing.]
[One to two sentences: context or background the reader needs.]
Specifically, I am requesting:
- [Item 1]
- [Item 2]
- [Item 3]
Could you please send this by [date]? [One sentence: why the deadline matters.]
Please let me know if you have any questions or need additional information.
Best regards,
[Your Name]
[Your Title]
[Contact Information]
Subject: Follow-Up: [Original Subject] (Sent [Date])
Hello [Name],
I am following up on my email from [date] regarding [brief description of the original request].
[One sentence acknowledging they may be busy or offering context.]
The [document/information/decision] is needed by [date] for [reason]. If possible, could you [specific action] by [date]?
If there is anything I can provide to help move this forward, please let me know.
Thank you,
[Your Name]
[Your Title]
[Contact Information]
Subject: Introduction: [Your Name], [Your Role/Company]
Dear [Name],
My name is [your name], and I am [your role] at [your company/organization]. [One sentence: how you found them or why you are reaching out.]
[Two to three sentences: what you do and why it is relevant to the recipient. Include one specific, concrete result if possible.]
I would welcome the opportunity to [specific, low-commitment ask — e.g., "schedule a brief 15-minute call" or "learn more about your team's approach"]. Would you be available [proposed timeframe]?
Thank you for your time.
Best regards,
[Your Name]
[Your Title]
[Your Company]
[Phone]
[Email]
Subject: [Issue Type] — [Reference Number or Key Detail]
Dear [Name / Department],
I am writing regarding [order number / account / service], [purchased/initiated] on [date]. [One sentence describing the expected outcome.]
[One to two sentences describing what went wrong, with specific dates and details.]
[If applicable: One sentence noting previous attempts to resolve.]
I would appreciate it if you could:
1. [Resolution option 1]
2. [Resolution option 2]
3. [Resolution option 3 / fallback]
My contact details are [email] and [phone]. I am available [availability].
Thank you for your prompt attention to this matter.
Sincerely,
[Your Name]
Subject: Thank You — [Meeting/Interview Topic or Position]
Dear [Name],
Thank you for [meeting with me / taking the time to interview me / your help with X] [today/yesterday/on date]. I particularly appreciated [one specific thing discussed or offered].
[One to two sentences about a follow-up action you are taking based on the meeting.]
[Optional: one sentence referencing a specific topic, showing you were engaged and attentive.]
Thank you again for your [time / guidance / support]. I look forward to [specific next step].
Best regards,
[Your Name]
[Your Title / Relevant Detail]
[Contact Information]
Subject: Update: [Project/Topic] — [Brief Indication of Change]
Dear [Name],
[One sentence of positive or neutral context, if available.]
Unfortunately, [state the bad news clearly and factually]. [One sentence explaining the reason, if appropriate.]
To address this, we are [taking specific action]. [One sentence about the revised plan, timeline, or alternative.]
I understand this may be inconvenient, and I apologize for any disruption. Please let me know if you would like to discuss this further.
Best regards,
[Your Name]
[Your Title]
[Contact Information]
用这些公式,为任何情境写出清楚、有效的主题行:
| 公式 | 结构 | 例子 |
|---|---|---|
| 行动 + 话题 | [Action Required/Requested]: [Topic] | Action Required: Approve Budget Revision |
| 话题 + 细节 | [Topic] — [Key Detail] | Website Redesign — Revised Timeline |
| 目的 + 背景 | [Purpose]: [What/Who] | Meeting Request: Q4 Strategy Discussion |
| 跟进 + 所指事项 | Follow-Up: [Original Topic] ([Date]) | Follow-Up: Vendor Proposal (March 5) |
| 进展 + 项目 | [Project Name] Update: [What Changed] | Atlas Project Update: Phase 2 Launch Delayed |
| 致谢 + 具体内容 | Thank You — [What For] | Thank You — Insightful Discussion on Market Trends |
| 自我介绍 + 身份 | Introduction: [Name], [Role/Company] | Introduction: Maria Lopez, Acme Corp |
| 确认 + 细节 | Confirming: [What] on [When] | Confirming: Team Lunch on Friday, March 14 |
| 问题 + 话题 | Question About [Specific Topic] | Question About Invoice #7892 Payment Terms |
| 告知 + 细节 | FYI: [What the Reader Should Know] | FYI: Office Parking Lot Closed March 15-17 |
主题行的规则:
| 该做 | 为什么 |
|---|---|
| 在第一句说明你的目的 | 尊重读者的时间 |
| 在问候语中使用收件人的名字 | 个人化而专业 |
| 请求对方采取行动时,写上具体的截止日期 | 含糊的时间会被往后放 |
| 有多个事项时使用项目符号 | 更容易浏览和执行 |
| 发送之前校对 | 错别字会损害可信度 |
| 让结束语的正式程度与问候语相匹配 | 语域一致 |
| 在 24 个工作小时之内回复 | 显示出专业 |
| 使用清楚、描述性的主题行 | 帮助读者,也便于搜索 |
| 第一次联系时附上完整的签名档 | 提供必要的背景 |
| 让段落保持在 2-4 个句子 | 留白有助于阅读 |
| 不该做 | 为什么 |
|---|---|
| 用全大写来强调 | 读起来像是在大喊 |
| 写超过 5 个句子的段落 | 会被匆匆扫过,而不是被认真阅读 |
| 在正式的职场邮件中使用表情符号 | 削弱专业的语气 |
| 除非每个人都需要你的回复,否则不要「全部回复」 | 会塞满别人的收件箱 |
| 不加说明就转发 | 收件人不知道自己为什么会收到它 |
| 使用 "per my last email" | 普遍被认为是被动攻击 |
| 以为语气(讽刺、幽默)能通过文字传达 | 通常传达不了 |
| 生气的时候发邮件 | 先写好草稿,等一个小时,再修改 |
| 把重要的请求埋在最后 | 大多数读者只浏览开头 |
| 让主题行空着或含糊不清 | 会降低打开率,也更难找到 |
问题: 邮件花了三段讲背景,然后才说出需要什么。
改法: 以请求开头。之后再提供背景。
| 改写前 | 改写后 |
|---|---|
| As you know, the Q3 review is coming up, and we have been working on compiling data from multiple departments. The process has been somewhat complicated because the new reporting system was only implemented last month. Additionally, there were some discrepancies in the data from the sales team that required clarification. With all of this in mind, I was hoping you could send me the finalized revenue numbers by Thursday. | Could you please send me the finalized Q3 revenue numbers by Thursday? We are compiling data for the quarterly review, and your figures are the last piece we need. |
问题: 没有分段,没有列表,没有视觉上的结构。
改法: 把内容分成短段落。有多个事项时使用列表。截止日期用粗体。
问题: 邮件结束时没有一个清楚的下一步。
| 含糊 | 清楚 |
|---|---|
| Let me know what you think. | Could you review the attached proposal and share your feedback by Wednesday? |
| We should discuss this sometime. | Are you available for a 30-minute call on Thursday or Friday afternoon? |
| Hope to hear from you soon. | I will follow up next Tuesday if I have not heard back. |
问题: 对外部联系人使用过于随意的语言,或者对关系密切的队友使用过于正式的语言。
改法: 让语域与彼此的关系相匹配。第一次联系外部的利益相关方,需要第 3-4 级的正式程度。给队友发一条简短的消息,可以用第 2 级。
问题: 在沮丧或生气的时候写邮件并发送出去。
改法: 使用「先写草稿再等待」的规则。写好邮件,存为草稿,至少等一个小时(对于事关重大的信息,最好等一个晚上),然后以清醒的头脑修改之后再发送。
让问候语的正式程度与结束语相匹配,以保持语气一致:
| 正式程度 | 问候语的选择 | 结束语的选择 |
|---|---|---|
| 正式 | Dear Mr./Ms./Dr. [Last Name], | Sincerely, / Respectfully, / Kind regards, |
| 半正式 | Hello [First Name], / Good morning [Name], | Best regards, / Best, / Thank you, |
| 随意 | Hi [Name], / Hey [Name], | Thanks, / Cheers, / Talk soon, |
经验法则: 拿不准的时候,就比你认为必要的程度再正式一级。随着时间的推移逐渐变得随意,比从第一次联系时过于随便的印象中挽回要容易。
在任何一封职场电子邮件上点击发送之前,都要确认:
| 资源 | 涵盖的内容 |
|---|---|
| 6 个邮件模板 | 请求、跟进、自我介绍、投诉、致谢和坏消息的现成框架 |
| 主题行公式 | 10 种写出清楚、可搜索的主题行的成熟结构 |
| 该做与不该做 | 10 条基本做法和 10 个常见错误 |
| 常见错误及改法 | 5 种常见的邮件错误及具体的解决办法 |
| 问候语与结束语的搭配 | 相互匹配的正式程度,保持语气一致 |
| 发送前的检查清单 | 每封职场邮件发送前的 13 项核查 |