Table of contents
Open Table of contents
- Who this guide is for
- Three ways Japanese business email differs from English
- Step 0: Three decisions before you type
- Step 1: Subject line (kenmei, 件名)
- Step 2: Pick TO, CC, BCC, or kakui
- Step 3: Addressee line (atena, 宛名)
- Step 4: Opening greeting (kakidashi, 書き出し)
- Step 5: Self-introduction (nanori, 名乗り)
- Step 6: Body (honbun, 本文)
- Step 7: Closing (musubi, 結び)
- Step 8: Signature (shomei, 署名)
- Pre-send 10-item checklist
- If you already sent it wrong — recovery
- Frequently asked questions
- Do I use osewa ni natte orimasu (お世話になっております) inside my own company?
- When do I use sama (様) versus san (さん)?
- Are seasonal greetings required in Japanese business email?
- Is it rude to send otsukaresama desu (お疲れさまです) to an external client?
- How do I handle the 15–25 character line-break rule on mobile?
- Related guides and next steps
- Try it on today’s email
Who this guide is for
- Expats 1–6 months into a Japanese company who’ve copy-pasted enough templates to know that copy-pasting doesn’t transfer to new scenarios.
- JLPT N3–N2 learners who understand desu/masu but realized workplace email is its own thing.
- Recent arrivals corresponding with Japanese clients from abroad, who need to ship today’s email at a register that won’t burn the relationship.
- Anyone who already read our Japanese business email template guide and now wants the underlying system rather than another set of templates.
This guide is process-first. If you want finished, copy-pasteable email bodies for 8 common scenarios, jump to the sibling Japanese business email templates. Come back here when you need to write something the templates don’t cover.
Three ways Japanese business email differs from English
Before the first keystroke, three foundations decide every later choice.
The structure is fixed
English business email is loosely structured. Japanese business email is not — 8 parts in a fixed order: subject → TO/CC/BCC selection → addressee line → opening greeting → self-introduction → body → closing → signature. Skipping a part, or reordering them, signals “doesn’t know the form” before the recipient reads a single content word.
Keigo is always mixed in — the A/B/C framework
Every sentence ending, address term, and verb in a Japanese business email carries a politeness level. We use a 3-level shorthand throughout the site, explained in detail in the keigo guide. In this article each step will tell you which level to pick.
| Level | When to use | Email reality |
|---|---|---|
| A | Same-year peers, friendly juniors | Almost never used in email — handled in Slack |
| B | Bosses, other departments, internal | Internal email default |
| C | Clients, first contact, apology, formal notice | External email default |
In practice, the email choice is binary: B for internal, C for external. A has almost no role in email.
Line breaks decide how the email looks
English email relies on auto-wrap. Japanese business email expects manual line breaks every 15–25 full-width characters. Skip this, and a paragraph-length sentence renders as a wall of characters to your recipient. The body section below has a worked example.
Step 0: Three decisions before you type
Before the subject field is even open, settle three things. Skipping this step means re-deciding mid-write.
Is your recipient uchi (内, internal) or soto (外, external)?
Look at the recipient’s email domain. Your domain = internal = B. Other company’s domain = external = C. The one exception: long-running external relationships where the other side already writes informally — those can drift toward B over time. When in doubt, pick C; over-formal beats under-formal every time.
One recipient or many?
One person: Tanaka-sama (external) or Tanaka-san (internal). Many people: kakui (各位, “everyone concerned”), go-tantōsha kakui (ご担当者各位), or kankei kakui (関係各位). Kakui contains the respect marker, so kakui-sama and kakui-dono are both wrong.
Information-sharing scope: TO, CC, BCC, or kakui?
| Field | Use it when | Example |
|---|---|---|
| TO | You expect a reply or an action | The primary owner |
| CC | Share for awareness; no reply expected | Boss, related team, PM |
| BCC | Silent share — others must not see this address | External mass-send privacy |
Common failures: TO-ing everyone (no one knows who should reply), BCC-ing your manager (looks furtive when discovered), and TO-ing multiple external clients at once (their addresses leak to each other). Default patterns: external mass-send → BCC; internal report → primary owner in TO, manager in CC.
Step 1: Subject line (kenmei, 件名)
What to decide
A one-glance summary of your purpose. The recipient should know, from the subject alone, what the email is about and how urgent it is.
The rule
- Keep it under 20 full-width characters (longer subjects get cut off in mailers).
- Use the pattern: topic noun + connector (ni tsuite について, no ken の件, go-renraku ご連絡, go-irai ご依頼).
- Prefix with bracketed category markers: 【ご相談】, 【日程調整】, 【至急】, 【ご案内】. These let the recipient sort and prioritize at a glance.
Picking the level
| Level | Recipient | Subject example |
|---|---|---|
| B | Internal | 進捗共有:プロジェクトAの今週分 |
| B | Internal | 【日程調整】定例MTGの来週分 |
| C | External | 【ご相談】◯◯案件のお見積りについて |
| C | External | 【ご案内】貴社訪問日程のご相談 |
Common mistakes
- Greetings in the subject (konnichiwa, otsukaresama desu) — the greeting belongs in the body. Subject is for the topic only.
- One word like ご報告 or ご相談 — what report, about what? Always include a topic noun.
- Subjects so long they truncate — compress aggressively: 「先日ご相談させていただきました件のお見積もりの件についてご確認いただきたく」 → 「【見積り確認】◯◯案件」.
Need the finished version of a subject line for a specific scenario? Jump to the Japanese business email templates — 8 scenarios.
Step 2: Pick TO, CC, BCC, or kakui
Execute the Step 0 decision
You already chose this in Step 0. Step 2 is execution: TO for the person you want a reply from, CC for everyone who needs awareness, BCC for silent shares.
One-line rules
- TO: someone you expect a response from. Default to one primary owner.
- CC: “for your awareness” recipients — manager, neighboring team, PM, secondary client contact.
- BCC: external mass-send where addresses must not leak to each other.
Choosing the addressee form for the body line
| Situation | Body’s addressee line |
|---|---|
| One external person | 株式会社○○ 営業部 田中様 |
| One internal person | 田中さん |
| A department or company | 株式会社○○ 営業部 御中 |
| Several people (mixed roles) | 関係者各位 |
| An internal project group | プロジェクトAメンバー各位 |
Common mistakes
- Everyone in TO: 5 people in TO means everyone assumes someone else will reply. Pick one owner.
- Boss in BCC: looks like you’re operating behind their back when it surfaces. CC them openly.
- External clients batch-TO’d: their email addresses become visible to one another — a real privacy incident in some industries. Default to BCC.
Step 3: Addressee line (atena, 宛名)
What to decide
The first line of the body, equivalent to “Dear ___” in English — whom you’re addressing.
Picking the level
| Level | Situation | Format |
|---|---|---|
| C | External, one person | 株式会社○○ 営業部 田中様 |
| C | External, department | 株式会社○○ 営業部 御中 |
| C | External, multiple | 関係者各位 |
| B | Internal, one person | 田中さん |
| B | Internal, multiple | プロジェクトAメンバー各位 |
External recipients get the full set: company name + department + title + family name + sama. Title placement follows the recipient’s own signature — some sign as “営業部長 田中” (title before name), others as “田中部長” (title after). Match what they use.
Common mistakes
- Bare “Tanaka-sama” on external email — drop the company line and you sound like an old contact you’re not.
- Double respect markers: “Tanaka-buchō-sama” stacks title-and-respect. Pick one: “Tanaka-buchō” or “Tanaka-sama”.
- “Kakui-sama” or “kakui-dono”: kakui already includes respect.
- Misspelling the family name: confirm against their signature before sending. If you catch it after sending, ship a 30-second correction (see the recovery section).
Step 4: Opening greeting (kakidashi, 書き出し)
What to decide
The single line between the addressee and the body — the standard email greeting. No “I hope this finds you well.” Japanese business email uses a fixed opener.
Picking the level
| Level | Situation | Phrase |
|---|---|---|
| C | External, ongoing relationship | itsumo osewa ni natte orimasu (いつもお世話になっております) |
| C | External, first contact | hajimete go-renraku itashimasu (初めてご連絡いたします) |
| C | External, after a long gap | go-busata shite orimasu (ご無沙汰しております) |
| B | Internal, daytime | otsukaresama desu (お疲れさまです) |
| B | Internal, morning thread | ohayō gozaimasu (おはようございます) |
The rule
- External: write itsumo osewa ni natte orimasu on its own line, then break.
- Internal: otsukaresama desu is enough. Writing osewa ni natte orimasu to your own colleagues reads as awkwardly distant.
- Skip seasonal greetings in routine email. Haikei (拝啓) and jika masu-masu go-seiei… (時下ますますご清栄…) belong to physical letters and ceremonial correspondence.
Common mistakes
- Osewa ni natte orimasu to internal colleagues — over-formal, reads like distance.
- Osewa ni natte orimasu to a first-contact stranger — you haven’t been in their care yet. Use hajimete go-renraku itashimasu.
- Otsukaresama desu to an external client — covered in the FAQ; recovery section below has the fix.
Step 5: Self-introduction (nanori, 名乗り)
What to decide
Immediately after the greeting, identify yourself in 1–2 lines. This is one of the strongest contrasts with English email — even on a long-running thread, Japanese business writers re-introduce.
The rule
- External: re-introduce every single message. The thread can be 30 emails deep; the first body line of #31 still starts with “Yamada from XYZ Corp.”
- Internal: re-introduce only when crossing departments. Same-department thread? “Yamada here” works alone — or skip entirely.
- Don’t pile on your title. Writing “Sales department head Yamada speaking” sounds like self-promotion. Title belongs in the signature.
Picking the level
| Level | Situation | Phrase |
|---|---|---|
| C | External | kabushiki-gaisha △△ no Yamada de gozaimasu (株式会社△△の山田でございます) |
| C | External, softer tone | kabushiki-gaisha △△ no Yamada desu (株式会社△△の山田です) |
| B | Internal, other department | eigyō-ika no Yamada desu (営業1課の山田です) |
| B | Internal, same department | Yamada desu (山田です) |
Common mistakes
- Skipping the self-introduction externally — the recipient thinks “who is this again?” for a beat. Re-introduce every time.
- Inflating your title — “Director of Sales Operations Yamada” reads as posturing. The signature does the title work.
Step 6: Body (honbun, 本文)
This is the heaviest step. Three rules keep you out of the weeds.
Rule 1: Break lines every 15–25 full-width characters
This single rule shapes how your email looks more than anything else. Without it, your body lands in the recipient’s window as a paragraph-shaped block.
❌ No line breaks
お世話になっております。先日ご相談させていただいた件につきまして、社内で検討した結果、来週水曜日の14時からの打ち合わせでよろしいかご確認をお願いしたく、ご連絡いたしました。
✅ 15–25 character breaks
お世話になっております。
先日ご相談させていただいた件につきまして、
社内で検討した結果、
来週水曜日14時からの打ち合わせで
よろしいかご確認をお願いいたします。
Break after periods (。) and before connectors (ni tsuite について, no tame のため, desu ga ですが). When ASCII letters or numbers are mixed in, aim for 30–50 half-width characters per line as the equivalent. Outlook and Gmail render line widths slightly differently, but 15–25 full-width keeps you safe in both.
Rule 2: Conclusion → reason → ask
English email often opens with relationship niceties (“Hope you’re well…”). Japanese business email leads with the conclusion.
❌ Conclusion last
お世話になっております。
先日のお打ち合わせありがとうございました。
社内で検討した結果、いくつか確認事項が出てきました。
ご多忙のところ恐縮ですが、改めて打ち合わせのお時間を頂戴できますでしょうか。
✅ Conclusion first
お世話になっております。
来週、改めてお打ち合わせのお時間を頂戴したく、ご連絡いたしました。
先日のお打ち合わせでご相談した件について、
社内で検討した結果、確認事項が3点ございます。
ご都合のよい日時を2〜3候補お知らせいただけますと幸いです。
Rule 3: Final keigo sweep
Before closing the body, re-scan for three things: the o-/go- honorific prefix on relevant nouns, itashimasu vs. shimasu (humble vs. polite), and the -sasete itadaku (させていただく) count. Heavier verbs and lookup tables live in the keigo cheat sheet. For external mail, default everything to the C side; for internal, B.
Want a ready-to-paste body for 8 common scenarios — scheduling, thanks, apology, ask, nudge, decline, inquiry, confirmation? See the Japanese business email templates.
Common mistakes
- Three or more -sasete itadaku in one email — covered in detail in the 8 keigo mistakes non-natives make. The verb sounds humble in isolation and overbearing in volume.
- Stacking connectors — one tsukimashite wa (つきましては) or nao (なお) per email is enough.
- Emoji or kaomoji — fine in Slack, never in external email.
Step 7: Closing (musubi, 結び)
What to decide
A one- or two-line sign-off above the signature. The English equivalent is “Best regards.”
Picking the level
| Level | Situation | Phrase |
|---|---|---|
| C | Universal (works internal + external) | nani-tozo yoroshiku onegai mōshiagemasu (何卒よろしくお願い申し上げます) |
| C | External default | yoroshiku onegai itashimasu (よろしくお願いいたします) |
| C | After an apology | go-meiwaku o o-kake shimasu ga, nani-tozo yoroshiku onegai mōshiagemasu (ご迷惑をおかけしますが、何卒よろしくお願い申し上げます) |
| C | Requesting a reply | go-kakunin no hodo, yoroshiku onegai itashimasu (ご確認のほど、よろしくお願いいたします) |
| B | Internal | yoroshiku onegai shimasu (よろしくお願いします) |
| B | Internal, ongoing thread | hikitsuzuki yoroshiku onegai shimasu (引き続きよろしくお願いします) |
Common mistakes
- Closing with ijō desu (以上です) only — fine internal-only, lands as curt externally. Add yoroshiku onegai itashimasu.
- English sign-offs (“Thanks,” “Best”) in external Japanese email — reads as you haven’t fully made the switch.
Step 8: Signature (shomei, 署名)
What to decide
A fixed block at the bottom with your contact information. Many companies provide an official template — check yours first.
The required 5 lines
株式会社△△
営業1課
山田 太郎(やまだ たろう)
TEL: 03-1234-5678
Email: [email protected]
Picking the level
| Level | Situation | Contents |
|---|---|---|
| C | External | Full 5 lines + company address + URL |
| B | Internal, same department | Family name alone is fine |
| B | Internal, other department | ”Department + family name” |
Common mistakes
- No signature on external email — your reply lands without contact details; the recipient has to dig.
- Inflated job titles — “Senior Director of Strategic Operations” reads as theatrical. Use the title HR officially assigned you.
- URL only, no phone or email — leaves the recipient with no fallback when something urgent comes up.
Pre-send 10-item checklist
Run this top-to-bottom before pressing send. The first week it takes a minute; by week 3 it takes 5 seconds.
| # | Check | What to confirm |
|---|---|---|
| 1 | Subject ≤ 20 full-width chars + bracketed category | 【ご相談】, 【日程調整】, etc. |
| 2 | Addressee honorific is correct | sama / san / kakui / onchū matches recipient type |
| 3 | Family name spelling and kanji are right | 田中 vs. 田仲, 佐藤 vs. 佐東 |
| 4 | TO / CC / BCC are intentional | Mass-send goes BCC; manager goes CC |
| 5 | Greeting matches uchi-soto | External: osewa ni natte orimasu. Internal: otsukaresama desu |
| 6 | Lines break at 15–25 full-width chars | No wall-of-text paragraphs |
| 7 | Full-width / half-width is consistent | ”3つ” vs. “3つ” — pick one |
| 8 | Attachment is attached + file name is external-safe | Avoid “final_v3_fix.docx” type names |
| 9 | No keigo gaps; sasete itadaku count ≤ 2 | Skim for honorific drift |
| 10 | Closing + signature are in place | yoroshiku + 5-line block |
Bookmark this list, or stash it as a draft in your mail client until it becomes muscle memory.
If you already sent it wrong — recovery
Knowing the recovery move matters more than perfect prevention. Move within 30 seconds of realizing the mistake and the damage stays small.
Common misfires and the 30-second move
| Misfire | First move (within 30 seconds) |
|---|---|
| Wrong family name | Send a correction email (template below) |
| Wrong recipient in TO/CC | Correction email: “the previous message was sent in error — please disregard” + corrected version |
| Otsukaresama desu to an external client | Correction email: brief apology + reissue with osewa ni natte orimasu |
| Forgot the attachment | Correction email: “the attachment was missing from my previous message; re-sending now” |
| Confidential info in the wrong thread | Loop in your manager and your info-security team immediately — this is not a do-it-yourself recovery |
Correction email after a name mistake (C-level external)
件名:【お詫び・訂正】先ほどのメールについて
○○株式会社
営業部 田中様
お世話になっております。
株式会社△△の山田でございます。
先ほどお送りしたメールにて、
お名前を誤って記載しておりました。
心よりお詫び申し上げます。
正しくは「田中様」でございます。
重ねてのご無礼、誠に申し訳ございません。
引き続きよろしくお願い申し上げます。
──
株式会社△△
営業1課 山田 太郎
TEL: 03-1234-5678
The three moves to internalize: no excuses, apologize fast, restate the correct info. A short apology plus correct content recovers trust faster than a long explanation of how it happened.
For heavier apologies — financial loss, missed deadline, data leak — start from the apology template in the Japanese business email templates, and loop in your manager.
Frequently asked questions
Do I use osewa ni natte orimasu (お世話になっております) inside my own company?
No, not in everyday in-house email. Internal email opens with otsukaresama desu (お疲れさまです); external email opens with itsumo osewa ni natte orimasu (いつもお世話になっております). Writing the external opener to your own colleagues reads as oddly distant — like an over-formal opening to someone you sit next to. The exception is internal-but-ceremonial mail to senior executives in another division, where the formal opener can fit.
When do I use sama (様) versus san (さん)?
External email defaults to sama (Tanaka-sama); internal email defaults to san (Tanaka-san). The exception is a long-running external relationship where the other side has started writing -san to you — match their register. For groups, use kakui (各位) — it already contains the respect marker, so kakui-sama is wrong. For an entire company or department, use onchū (御中).
Are seasonal greetings required in Japanese business email?
No. Everyday business email opens with itsumo osewa ni natte orimasu and that’s enough. Seasonal greetings such as haikei (拝啓) and jika masu-masu go-seiei no koto to o-yorokobi mōshiagemasu (時下ますますご清栄のこととお慶び申し上げます) belong to physical letters, New Year cards, and ceremonial correspondence. Adding them to a routine work email reads as theatrical.
Is it rude to send otsukaresama desu (お疲れさまです) to an external client?
Yes — it crosses an unspoken boundary. Otsukaresama is an in-house greeting that assumes a shared workplace context; you’re not in a position to thank an external counterpart for their day’s labor. Default to itsumo osewa ni natte orimasu externally. If you’ve already sent it, fire off a 30-second correction email using the template in the recovery section above.
How do I handle the 15–25 character line-break rule on mobile?
Break manually anyway, with line breaks before connectors (ni tsuite, no tame) and after periods. Your recipient most likely reads on a PC, where one un-broken Japanese sentence becomes a wall of text. The mobile composer hides this from you — what looks fine on your screen renders as a paragraph block on theirs.
Related guides and next steps
You now have the scaffold. The next two moves are stocking up on finished templates and tightening your keigo accuracy.
- Want finished email bodies for 8 common scenarios? Go to the sibling Japanese business email templates — scheduling, thanks, apology, follow-up, decline, inquiry, confirmation, and ask.
- Keigo foundations — The A/B/C keigo guide covers the politeness framework we used throughout this guide.
- Look up a specific verb’s polite, humble, and respectful forms — Keigo cheat sheet.
- The 8 keigo mistakes non-natives make most — Keigo mistakes guide.
- Phrases to memorize in your first week — 10 polite Japanese phrases for the office.
- 30 scenarios in PDF-friendly format — Japanese business phrases PDF.
- Self-introduction (chōrei 朝礼, client visits, interviews) — Japanese business self-introduction.
Try it on today’s email
Pick the email you most want to send today and write it from a blank screen, working through the 8 steps in order. Skip the template tab — close it. Run the 10-item checklist at the end. The first one will take 10 minutes; by the fifth, it’s under 2.
For the days when you’d rather paste than think, the Essential 30 pack covers 30 real-world business email and phone scenes with full-sentence templates at three politeness levels — a backstop while the 8-step process becomes second nature.