email-composer
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseEmail Composer
邮件撰写助手
Quick start
快速开始
Provide context and purpose, and I'll draft an appropriate email.
What I need:
- Purpose of email (request, follow-up, announcement, etc.)
- Recipient relationship (colleague, customer, manager, vendor)
- Key points to include
- Desired tone (formal, casual, urgent, friendly)
提供相关背景和目的,我会为你起草合适的邮件。
我需要以下信息:
- 邮件目的(请求、跟进、通知等)
- 收件人关系(同事、客户、经理、供应商)
- 需要包含的核心要点
- 期望的语气(正式、随意、紧急、友好)
Email structure
邮件结构
Standard professional email format:
Subject: [Clear, specific subject line]
[Greeting],
[Opening - context/purpose]
[Body - main points]
[Closing - call to action]
[Sign-off]
[Your name]标准专业邮件格式:
Subject: [Clear, specific subject line]
[Greeting],
[Opening - context/purpose]
[Body - main points]
[Closing - call to action]
[Sign-off]
[Your name]Common email types
常见邮件类型
Request for information
信息请求
Subject: Question about Q4 project timeline
Hi [Name],
I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.
Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of
This will help us coordinate with the marketing team for the launch materials.
Thanks in advance for your help!
Best regards,
[Your name]Subject: Question about Q4 project timeline
Hi [Name],
I hope this email finds you well. I'm reaching out regarding the Q4 product launch timeline.
Could you provide an update on:
- Current progress on feature development
- Expected completion date for testing phase
- Any blockers or dependencies we should be aware of
This will help us coordinate with the marketing team for the launch materials.
Thanks in advance for your help!
Best regards,
[Your name]Follow-up email
跟进邮件
Subject: Following up: Proposal for new payment system
Hi [Name],
I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.
To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience
I'd be happy to schedule a brief call to discuss any questions you might have.
Looking forward to hearing from you.
Best,
[Your name]Subject: Following up: Proposal for new payment system
Hi [Name],
I wanted to follow up on the payment system proposal I sent last week. I understand you're busy, so I wanted to make sure it didn't get lost in your inbox.
To recap, the proposed system would:
- Reduce transaction fees by 30%
- Integrate with existing accounting software
- Improve customer checkout experience
I'd be happy to schedule a brief call to discuss any questions you might have.
Looking forward to hearing from you.
Best,
[Your name]Technical update
技术更新
Subject: API Maintenance Window - [Date]
Team,
This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].
During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed
Expected downtime: 2 hours
What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes
If you have any concerns or conflicts with this schedule, please let me know by [Date].
Technical details available in our status page: [link]
Thanks,
[Your name]Subject: API Maintenance Window - [Date]
Team,
This is a reminder that we'll be performing scheduled maintenance on our API infrastructure on [Date] from [Time] to [Time] [Timezone].
During this window:
- API endpoints will be unavailable
- Database will be upgraded to v14
- SSL certificates will be renewed
Expected downtime: 2 hours
What you need to do:
- Notify your users of the planned downtime
- Ensure retry logic is in place for API calls
- Monitor your application after maintenance completes
If you have any concerns or conflicts with this schedule, please let me know by [Date].
Technical details available in our status page: [link]
Thanks,
[Your name]Customer support
客户支持
Subject: Re: Issue with order #12345
Hi [Customer name],
Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.
I've looked into your order (#12345) and found the following:
[Explanation of the issue]
To resolve this, I've:
- [Action taken 1]
- [Action taken 2]
You should see [expected outcome] within [timeframe].
If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].
We appreciate your patience and understanding.
Best regards,
[Your name]
Customer Support TeamSubject: Re: Issue with order #12345
Hi [Customer name],
Thank you for reaching out about your order. I'm sorry to hear you're experiencing this issue.
I've looked into your order (#12345) and found the following:
[Explanation of the issue]
To resolve this, I've:
- [Action taken 1]
- [Action taken 2]
You should see [expected outcome] within [timeframe].
If you continue to experience any problems, please don't hesitate to reply to this email or call us at [phone number].
We appreciate your patience and understanding.
Best regards,
[Your name]
Customer Support TeamMeeting request
会议请求
Subject: Meeting request: Discuss database migration strategy
Hi [Name],
I'd like to schedule a meeting to discuss our approach for the upcoming database migration.
Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities
Estimated duration: 45 minutes
I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM
Please let me know what works best for you, or feel free to suggest alternative times.
Best,
[Your name]Subject: Meeting request: Discuss database migration strategy
Hi [Name],
I'd like to schedule a meeting to discuss our approach for the upcoming database migration.
Agenda items:
- Review migration timeline and milestones
- Discuss rollback strategy
- Identify potential risks and mitigation plans
- Assign team responsibilities
Estimated duration: 45 minutes
I'm available:
- Monday 2-4 PM
- Wednesday 10 AM - 12 PM
- Friday 1-3 PM
Please let me know what works best for you, or feel free to suggest alternative times.
Best,
[Your name]Tone guidelines
语气指南
Formal tone
正式语气
- Use complete sentences
- Avoid contractions
- Professional language
- Proper titles (Dr., Mr., Ms.)
- 使用完整句子
- 避免使用缩写
- 使用专业用语
- 使用恰当称谓(博士、先生、女士)
Casual tone
随意语气
- Contractions acceptable
- Conversational language
- Still professional
- First names
- 可使用缩写
- 使用口语化表达
- 保持专业度
- 使用名字称呼
Urgent tone
紧急语气
- Clear subject line with [URGENT] or [ACTION REQUIRED]
- Bold key points
- Explicit deadline
- Direct call to action
- 主题行明确标注[URGENT]或[ACTION REQUIRED]
- 核心要点加粗
- 明确截止日期
- 直接的行动指令
Subject line best practices
主题行最佳实践
Good subject lines:
- "Action required: Submit timesheet by Friday"
- "Q4 Sales Report - Review needed"
- "Meeting rescheduled: Project kickoff now Thursday"
- "Quick question about deployment process"
Bad subject lines:
- "Update"
- "Question"
- "Hello"
- "Following up"
优秀主题行示例:
- "需执行:周五前提交工时表"
- "Q4销售报告 - 需审核"
- "会议改期:项目启动会改为周四"
- "关于部署流程的快速咨询"
糟糕主题行示例:
- "更新"
- "问题"
- "你好"
- "跟进"
Email etiquette
邮件礼仪
DO:
- Respond within 24 hours (even if just to acknowledge)
- Use clear, specific subject lines
- Keep it concise
- Proofread before sending
- Include relevant context
- Use bullet points for multiple items
- End with clear call to action
DON'T:
- Use ALL CAPS
- Over-use exclamation marks!!!
- Mark everything as urgent
- Reply all unless necessary
- Send when emotional
- Include unnecessary recipients
- Forget attachments mentioned in email
需要做到:
- 24小时内回复(哪怕只是确认收到)
- 使用清晰、具体的主题行
- 内容简洁
- 发送前校对
- 包含相关背景
- 多项内容使用项目符号
- 结尾给出明确行动指令
不要做:
- 全部使用大写字母
- 过度使用感叹号!!!
- 所有内容都标记为紧急
- 非必要不要点击“全部回复”
- 情绪激动时不要发送邮件
- 不要添加无关收件人
- 不要遗漏邮件中提到的附件
Templates by scenario
场景化模板
Decline request politely
礼貌拒绝请求
Subject: Re: [Original subject]
Hi [Name],
Thank you for thinking of me for [request/opportunity].
Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].
I appreciate your understanding, and I hope we can collaborate on future opportunities.
Best regards,
[Your name]Subject: Re: [Original subject]
Hi [Name],
Thank you for thinking of me for [request/opportunity].
Unfortunately, I won't be able to [participate/help/attend] due to [brief reason - optional]. However, I'd recommend [alternative suggestion if applicable].
I appreciate your understanding, and I hope we can collaborate on future opportunities.
Best regards,
[Your name]Apologize for mistake
为错误致歉
Subject: Apology and correction: [Issue]
Hi [Name],
I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.
To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]
I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.
If you have any concerns or questions, please don't hesitate to reach out.
Sincerely,
[Your name]Subject: Apology and correction: [Issue]
Hi [Name],
I'm writing to apologize for [specific mistake]. This was an error on my part, and I take full responsibility.
To correct this:
- [Action 1 already taken]
- [Action 2 in progress]
- [Preventive measure for future]
I understand this may have caused [impact], and I'm committed to ensuring it doesn't happen again.
If you have any concerns or questions, please don't hesitate to reach out.
Sincerely,
[Your name]Share good news
分享好消息
Subject: Great news: [Achievement/milestone]
Team,
I'm excited to share that we've [accomplished goal]!
This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]
Impact:
- [Metric improvement]
- [Business benefit]
Thank you all for your hard work and dedication. Let's keep up the momentum!
Cheers,
[Your name]Subject: Great news: [Achievement/milestone]
Team,
I'm excited to share that we've [accomplished goal]!
This success is thanks to:
- [Team/person contribution 1]
- [Team/person contribution 2]
Impact:
- [Metric improvement]
- [Business benefit]
Thank you all for your hard work and dedication. Let's keep up the momentum!
Cheers,
[Your name]Closing phrases by context
分场景结束语
Formal:
- Sincerely
- Best regards
- Respectfully
- Cordially
Professional:
- Best
- Thanks
- Kind regards
- Regards
Casual:
- Cheers
- Thanks!
- Talk soon
- Best
正式场合:
- 谨上
- 此致 敬礼
- 敬上
- 诚挚问候
专业场合:
- 祝好
- 感谢
- 亲切问候
- 问候
随意场合:
- 祝好
- 谢谢!
- 稍后联系
- 祝好
Email composition checklist
邮件撰写核对清单
- Clear, specific subject line
- Appropriate greeting
- Purpose stated upfront
- Key points organized with bullets/numbers
- Clear call to action or next steps
- Appropriate tone for audience
- Proofread for typos
- Attachments included (if mentioned)
- Recipients correct (To, CC, BCC)
- Professional signature
- 清晰、具体的主题行
- 恰当的问候语
- 开篇明确目的
- 核心要点用项目符号/编号整理
- 明确的行动指令或后续步骤
- 符合受众的语气
- 校对拼写错误
- 附上邮件中提及的附件
- 收件人正确(收件人、抄送、密送)
- 专业的签名