email-composer

Email Composer

クイックスタート

目的と背景を教えていただければ、適切なメールを作成します。

必要な情報:

• メールの目的（依頼、フォローアップ、お知らせなど）
• 受信者との関係（同僚、顧客、上司、ベンダー）
• 盛り込むべき主要なポイント
• 希望するトーン（フォーマル、カジュアル、緊急、フレンドリー）

メールの構成

一般的なビジネスメールの形式:

Subject: [Clear, specific subject line]

[Greeting],

[Opening - context/purpose]

[Body - main points]

[Closing - call to action]

[Sign-off]
[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]

フォローアップメール

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: 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: 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 Team

会議の依頼

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]

トーンのガイドライン

フォーマルなトーン

• 完全な文を使う
• 短縮形を避ける
• ビジネスにふさわしい言葉遣いをする
• 適切な敬称を使う（Dr.、Mr.、Ms.）

カジュアルなトーン

• 短縮形の使用可
• 会話的な言葉遣いをする
• それでもビジネスらしさを保つ
• ファーストネームを使う

緊急のトーン

• 件名に [URGENT] または [ACTION REQUIRED] を明記する
• 重要なポイントを太字にする
• 明確な期限を示す
• 具体的な行動を直接求める

件名のベストプラクティス

良い件名の例:

• "Action required: Submit timesheet by Friday"
• "Q4 Sales Report - Review needed"
• "Meeting rescheduled: Project kickoff now Thursday"
• "Quick question about deployment process"

悪い件名の例:

• "Update"
• "Question"
• "Hello"
• "Following up"

メールのエチケット

すべきこと:

• 24時間以内に返信する（確認のみでも可）
• 明確で具体的な件名を使う
• 簡潔にまとめる
• 送信前に校正する
• 関連する背景情報を含める
• 複数の項目は箇条書きにする
• 明確な行動の呼びかけで締めくくる

避けるべきこと:

• すべて大文字で書く
• 感嘆符を多用する（!!!）
• すべてを緊急扱いにする
• 必要がないのに全員へ返信する
• 感情的になっているときに送信する
• 不要な受信者を含める
• メール内で言及した添付ファイルを付け忘れる

シナリオ別のテンプレート

丁寧に依頼を断る

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: 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: 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]

状況別の結びの言葉

フォーマル:

• Sincerely
• Best regards
• Respectfully
• Cordially

ビジネス:

• Best
• Thanks
• Kind regards
• Regards

カジュアル:

• Cheers
• Thanks!
• Talk soon
• Best

メール作成チェックリスト

• 明確で具体的な件名になっている
• 適切な挨拶が入っている
• 冒頭で目的を述べている
• 主要なポイントを箇条書きや番号付きリストで整理している
• 明確な行動の呼びかけor次のステップがある
• 読み手に合ったトーンになっている
• 誤字脱字を校正した
• 言及した添付ファイルを添付した（該当する場合）
• 受信者（To、CC、BCC）が正しい
• プロフェッショナルな署名がある