Japanese Business Email Templates: 8 Scenarios for Internal and Client-Facing Use

Table of contents

Who this guide is for

• Expats working in Japanese companies who’ve memorized itsumo osewa ni natte orimasu but freeze when emailing a colleague — should it still open the same way?
• Recent arrivals at Japanese companies with an email to send today, tired of stitching together half-relevant snippets from five different blogs.
• Global HR managers and team leads onboarding non-Japanese staff who are corrected on email register more than they expect.

Textbooks teach you grammar. They don’t teach you that the apology you send to a client looks nothing like the apology you send to a teammate. This guide does.

The A/B/C politeness framework for email

At Real-World Japanese, we teach Japanese workplace language as three rephrasings of the same intent. Full framework lives in our keigo guide; here’s the email-specific cut:

In email, A is rare — that traffic has migrated to chat tools. The real call you’ll make every day is B vs. C, and the next section settles it.

Internal vs. external — the axis other guides skip

Most template collections assume “business email” means external. But in real expat life, most of your daily email is internal: status updates, schedule asks, document handoffs to teammates. Native Japanese speakers don’t open internal emails with haikei / keigu (拝啓・敬具), and they don’t write itsumo osewa ni natte orimasu to the person sitting two desks away.

Rule of thumb: Look at the email domain. Same domain as yours → B. Different domain → C. The only common exception is a long-running external partner who’s drifted into B over time.

Using C inside your own company reads as cold and standoffish — like you’re keeping people at arm’s length on purpose. When a non-native opens a coworker email with itsumo taihen osewa ni natte orimasu, the receiver immediately registers it as “still adjusting.”

Anatomy of a Japanese business email

A Japanese business email almost always has these six parts in this exact order:

The two parts non-natives mis-tune most often are the opening greeting and the closing. You can have flawless body Japanese and still sound off if these slip.

Subject line rules and 5 real examples

The reliable subject-line formula is bracketed category + content. Open with a 【】-enclosed tag for the email type, then the specific topic, then a date if relevant.

Tip: Avoid subject lines that contain only otsukaresama desu or osewa ni natte orimasu with no content. They look like spam in the inbox and won’t get opened.

When osewa ni natte orimasu fails

The default opener itsumo osewa ni natte orimasu covers about 90% of business emails. It fails in three specific situations:

• First-contact emails: You haven’t been taken care of yet, so itsumo (always) is unnatural. Use hajimete go-renraku itashimasu (初めてご連絡いたします) or totsuzen no go-renraku shitsurei itashimasu (突然のご連絡失礼いたします).
• Internal emails: Coworkers don’t take care of each other in this register. Use otsukaresama desu instead.
• Apology / incident emails: Opening with the routine pleasantry feels too light when something has gone wrong. Lead directly with kono tabi wa taihen go-meiwaku wo o-kake shi, makotoni mōshiwake gozaimasen (このたびは大変ご迷惑をおかけし、誠に申し訳ございません).

Recipient address — sama / onchū / kakui

Tip: Stacking suffixes is wrong. 田中部長様 and 田中様 御中 are double-honorifics. Pick one — either Tanaka-buchō or Tanaka-sama, never both.

Body: lead with the ask

Unlike many Western emails that build context first, Japanese business emails state the purpose in the first paragraph, then provide background. This is a courtesy to the busy reader, not a rudeness.

お世話になっております。
株式会社△△の山田です。

先日ご相談いただいた見積もりの件につきまして、
資料を添付しましたのでご確認をお願いいたします。

“I’m sending the document” goes in the lead paragraph. Save the background, the why, and the thank-you for the second half. Bury the ask and the busy reader closes the tab before reaching it.

Closing phrases (itashimasu vs. mōshiagemasu)

Tip: Yoroshiku onegai shimasu (without itashimasu) is too casual for external email. The added itashimasu (the kenjougo form) is the minimum bar.

Signature block — full example

─────────────────
株式会社△△
営業部 山田太郎（Yamada Taro）
〒100-0001東京都千代田区○○ 1-2-3
TEL: 03-1234-5678 / Mobile: 090-1234-5678
Email: [email protected]
URL: https://example.co.jp
─────────────────

Add your name in romaji alongside the kanji — your Japanese counterparts will appreciate not having to guess the reading. Mobile number to external counterparties is a judgment call (privacy).

The 15–25 character line break rule

This is the formatting rule that visibly marks a non-native email. In Japanese business email, lines wrap at 15–25 characters — not at paragraph breaks like in English. These are intra-paragraph hard breaks that follow meaning units.

Wrong (what non-natives ship)

平素より大変お世話になっております。先日ご相談いただいた件について、社内で検討した結果、以下のとおりご提案させていただきます。ご確認のほどよろしくお願いいたします。

→ Long lines wrap unpredictably on phones, and the reader’s eye loses the meaning units.

Right (the native standard)

平素より大変お世話になっております。

先日ご相談いただいた件について、
社内で検討した結果、
以下のとおりご提案させていただきます。

ご確認のほど
よろしくお願いいたします。

→ Breaks at clause boundaries. The eye moves through one idea at a time.

Tip: You don’t have to break only at periods (。). Breaking after a comma (、) is also fine. Optimize for meaning units, not character count.

To / Cc / Bcc / kakui — Japan-specific etiquette

To and Cc priority

• To: People who need to act (reply, do something).
• Cc: Information sharing only — replies are not expected.
• Bcc: Hide-from-other-recipients use only. Avoid in external email.

Cc ordering for internal mail

When listing multiple Cc recipients, rank them by seniority, top-to-bottom. The same applies in external email when you Cc your manager — they go above you. This isn’t pedantic — Japanese readers do glance at the order to assess whether you understand internal hierarchy.

Using kakui

Kakui (各位 — “everyone”) is a recipient line for sending to multiple people at once: kankeisha kakui (関係者各位 — “to all relevant parties”), o-kyaku-sama kakui (お客様各位 — “to all customers”). Because kakui already encodes respect, do not write kakui-sama. That’s a double honorific.

Tip: In a Japanese office, omitting your manager from Cc on a significant matter signals “they didn’t loop me in” — a hōrensō (報連相 — report/contact/consult) failure. When in doubt, Cc them.

8 copy-paste templates

The actual templates. Replace the ○○, △△, and ○月○日 placeholders with your specifics and the email is ready to send. Each template is tagged with its register level (A/B/C) and use case (internal vs. client).

1. Thank-you / follow-up to a client (C)

件名：【御礼】先日のお打ち合わせの件

株式会社○○
営業部 田中様

いつも大変お世話になっております。
株式会社△△の山田でございます。

先日はお忙しい中、貴重なお時間を頂戴し、
誠にありがとうございました。

ご相談いただいた件につきまして、
社内で検討のうえ、
改めて今週中にご提案資料をお送りいたします。

引き続きどうぞよろしくお願い申し上げます。

2. Thank-you to a colleague (B)

件名：先ほどはありがとうございました

田中さん

お疲れ様です。山田です。

先ほどは打ち合わせにご参加いただきありがとうございました。

決定事項について、後ほど議事録を共有します。
ご確認のうえ、修正点があればお知らせください。

よろしくお願いいたします。

3. Apology to a client (C)

件名：【お詫び】納期遅延のご連絡

株式会社○○
営業部 田中様

いつも大変お世話になっております。
株式会社△△の山田でございます。

このたびは、ご依頼いただいた○○の納品につきまして、
当初お約束した○月○日までに完了が困難な状況となり、
ご迷惑をおかけして誠に申し訳ございません。

現在の見込みとしては、○月○日までに納品できる見通しです。
今後このようなことがないよう、社内体制を見直してまいります。

何卒ご容赦いただけますようお願い申し上げます。

Tip: For serious apologies, you can drop the itsumo osewa opener entirely and lead with the apology. Routine pleasantries before a real apology dilute the sincerity.

4. Apology to a colleague (B)

件名：資料の修正点について

田中さん

お疲れ様です。山田です。

先ほど共有した資料に誤りがありました。
3ページ目のグラフの数値が古いバージョンのものです。

修正版をすぐに送りますので、
お手数ですが差し替えをお願いします。

失礼いたしました。

5. Meeting request to a client (C)

件名：【日程調整】お打ち合わせのご依頼

株式会社○○
営業部 田中様

いつもお世話になっております。
株式会社△△の山田でございます。

○○の件につきまして、改めて
お打ち合わせのお時間を頂戴できればと存じます。

下記日程でご都合いかがでしょうか。

・○月○日（○）14:00〜15:00
・○月○日（○）10:00〜11:00
・○月○日（○）16:00〜17:00

いずれもご都合がつかない場合、
別日程をご提示いただけますと幸いです。

何卒よろしくお願い申し上げます。

6. Internal meeting request (B)

件名：○○の件で打ち合わせさせてください

田中さん

お疲れ様です。山田です。

○○の件で30分ほどお打ち合わせさせていただきたいです。
今週中で下記いずれかご都合いかがでしょうか。

・○月○日14:00〜
・○月○日10:00〜

会議室は私の方で確保します。

よろしくお願いいたします。

7. Document or information request (B / C)

件名：【ご依頼】○○資料のご提供について

株式会社○○
営業部 田中様

いつもお世話になっております。
株式会社△△の山田でございます。

先日のお打ち合わせの件につきまして、
下記の資料をご提供いただけますと幸いです。

・○○の仕様書
・○○の見積もり明細

恐れ入りますが、○月○日までに
お送りいただけますでしょうか。

お忙しいところ恐縮ですが、
よろしくお願い申し上げます。

Tip: otesū desu ga (お手数ですが), osore irimasu ga (恐れ入りますが), and o-isogashii tokoro kyōshuku desu ga (お忙しいところ恐縮ですが) are the three cushion phrases. One or two before any ask shifts the tone substantially.

8. First contact / cold introduction (C)

件名：【初めてのご連絡】○○のご相談について

株式会社○○
営業部 田中様

突然のご連絡失礼いたします。
株式会社△△の山田と申します。

このたび、貴社の○○について
ぜひご相談させていただきたくご連絡いたしました。

弊社は○○を提供しており、
貴社の○○に貢献できる可能性があると考えております。

つきましては、一度オンラインで
30分ほどお時間を頂戴できないでしょうか。

ご都合のよろしい日時をお知らせいただけますと幸いです。

何卒よろしくお願い申し上げます。

Tip: For a first contact you can’t write itsumo osewa ni natte orimasu — you haven’t been taken care of yet. Use totsuzen no go-renraku shitsurei itashimasu or hajimete go-renraku itashimasu to open instead.

4 non-native email pitfalls

Pitfall 1: Over-formal opener with a colleague

Writing itsumo taihen osewa ni natte orimasu. Kabushiki gaisha △△ no Yamada de gozaimasu to a teammate is overkill. Internal email opens with otsukaresama desu. Yamada desu — that’s the full template. Excess formality reads as deliberate distance, not respect.

Pitfall 2: Mistuning toriaezu

Toriaezu go-renraku made (取り急ぎご連絡まで — “a quick heads-up before the full reply”) is a useful phrase, but its real meaning is “the formal version is coming later.” If you slap it on an email that’s complete on its own, the reader is left waiting for a follow-up that never arrives.

Pitfall 3: Reply-all that out-ranks your boss

In multi-recipient threads, replying with your opinion before your manager has weighed in can read as not understanding the chain of command. For anything sensitive, check with your manager first, then reply-all — or let them lead. External counterparts will assume the senior voice on your side carries the decision.

Pitfall 4: Attachment language that pushes blame

“Please let me know if you can’t see the attachment” is fine. “It should be attached, please confirm” is not — it puts the responsibility for the attachment on the reader. Either keep it neutral (tempu fairu wo go-kakunin kudasai — 添付ファイルをご確認ください) or make the request explicit: tempu no ○○ ni tsuite, go-kakunin no ue go-henshin itadakemasu to saiwai desu.

Recovery: what to send after the wrong email

The moment you most need a template is the moment after you realize you sent the wrong one. Competitor template collections almost universally skip this. Here are four common cases.

Case A: You misaddressed the recipient

Send a follow-up immediately. Open with: Saki hodo no mēru, atena wo ayamatte sōshin shite shimaimashita. Shitsurei itashimashita. Aratamete o-okuri itashimasu (先ほどのメール、宛先を誤って送信してしまいました。失礼いたしました。改めてお送りいたします). Then resend the correct version.

Case B: You used too low a register

You sent a B-level email to an external party, or replied ryōkai shimashita to your boss. You do not need to send a follow-up apology. Quietly recalibrate to C in your next message. A frantic “I’m so sorry I was too casual” email amplifies the awkwardness more than the original miss.

The exception: if the recipient signals visible irritation, a single line in your next email is enough — Saki hodo wa shitsurei na hyōgen ga gozaimashita nara mōshiwake gozaimasen (先ほどは失礼な表現がございましたら申し訳ございません).

Case C: You sent wrong information or numbers

Correct it immediately:

件名：【訂正】先ほどのメールについて

先ほどお送りしたメールに誤りがございました。
正しくは下記のとおりです。

【誤】○○○○
【正】△△△△

混乱を招き、誠に申し訳ございません。
お手数ですが、こちらの内容にてご対応のほどお願い申し上げます。

Case D: You sent to the wrong person (data exposure risk)

This is the urgent one. Notify your manager. Send the misaddressed recipient a request to delete: Saki hodo no mēru wa go-sōshin desu. O-tesū desu ga haiki itadakemasu deshō ka (先ほどのメールは誤送信です。お手数ですが破棄いただけますでしょうか). Loop in your security team if the data was sensitive.

Frequently asked questions

Do Japanese business emails use haikei and keigu?

Not for everyday business email. Haikei (拝啓) and keigu (敬具) belong to formal printed letters and ceremonial correspondence — New Year cards, formal apologies on physical letterhead. Using them in regular email reads as old-fashioned or theatrical. Modern email opens with itsumo osewa ni natte orimasu and closes with yoroshiku onegai itashimasu.

Who can I use otsukaresama desu with?

Internally — everyone. Peers, seniors, juniors, other departments — otsukaresama desu works across the whole org chart. It does not work with external counterparts; external email opens with itsumo osewa ni natte orimasu. Note: go-kurō-sama desu (ご苦労様です) is a top-down phrase only — never use it with seniors.

How quickly should I reply to a Japanese business email?

Within one business day is the workplace expectation. Even if you can’t fully answer, a quick naiyō wo kakunin no ue, aratamete go-renraku itashimasu (内容を確認のうえ、改めてご連絡いたします) goes a long way. Going past 24 hours signals that the sender will need to chase you with a reminder, which costs them planning time.

What’s the difference between ryōkai shimashita and shōchi itashimashita?

The literal meaning is similar, but ryōkai (了解) carries a faintly top-down acknowledgment tone for many native ears. Inside your team it’s fine. With clients, vendors, or anyone senior to you, shōchi itashimashita (承知いたしました) or kashikomarimashita (かしこまりました) is the safer choice. When in doubt, default to shōchi itashimashita.

How do I handle a subject that has accumulated multiple “Re:” prefixes?

Strip the chain back to a single Re:. The convention is one Re: maximum — anything beyond that is visual noise. If the topic has shifted, give the email a new subject line entirely: 【御礼】○○の件 → 【続き】○○の進捗について is a clean handoff.

Want more workplace phrases?

We’ve published Polite Japanese for Work: The Essential 30 — a PDF with 30 daily office phrases, each at three A/B/C levels with romaji and situational notes. Many of the templates in this guide build on phrases from the pack — the closing lines, the cushion phrases, and the apology openers are all expanded with usage notes.

→ Get The Essential 30 on Gumroad

More articles in this cluster:

• The full politeness framework → keigo guide — A/B/C and the uchi-soto axis (pillar)
• Verb-by-verb lookup → keigo cheat sheet — 30 verbs × A/B/C
• Saveable scenario phrases → Japanese business phrases PDF page — copy-paste rows that extend these email templates into Slack and meetings
• 10 spoken phrases for your first week → polite Japanese phrases for the office — the chronological office-day complement to these written templates
• Self-introduction template → Japanese self-introduction for business — the first-day intro paragraph that often opens the first email
• Mistakes to avoid in email → keigo mistakes guide — ryōkai shimashita with clients, gokurōsama upward, and 6 more diagnosed by severity
• The step-by-step writing process → How to write a Japanese business email — 8 steps from subject line to signature for composing one of these templates from scratch

For HR managers and team leads: The single fastest upgrade for a non-native employee’s first 90 days isn’t grammar — it’s getting the email register right (B internally, C externally). Forward this guide to your incoming hires, or use the 8 templates above as the starter set in your onboarding doc.