Skip to content
Real-World Japanese
Go back

How to Write a Japanese Business Email: 8 Steps from Subject to Signature

Table of contents

Open Table of contents

Who this guide is for

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.

LevelWhen to useEmail reality
ASame-year peers, friendly juniorsAlmost never used in email — handled in Slack
BBosses, other departments, internalInternal email default
CClients, first contact, apology, formal noticeExternal 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?

FieldUse it whenExample
TOYou expect a reply or an actionThe primary owner
CCShare for awareness; no reply expectedBoss, related team, PM
BCCSilent share — others must not see this addressExternal 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

Picking the level

LevelRecipientSubject example
BInternal進捗共有:プロジェクトAの今週分
BInternal【日程調整】定例MTGの来週分
CExternal【ご相談】◯◯案件のお見積りについて
CExternal【ご案内】貴社訪問日程のご相談

Common mistakes

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

Choosing the addressee form for the body line

SituationBody’s addressee line
One external person株式会社○○
営業部 田中様
One internal person田中さん
A department or company株式会社○○ 営業部 御中
Several people (mixed roles)関係者各位
An internal project groupプロジェクトAメンバー各位

Common mistakes


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

LevelSituationFormat
CExternal, one person株式会社○○
営業部 田中様
CExternal, department株式会社○○
営業部 御中
CExternal, multiple関係者各位
BInternal, one person田中さん
BInternal, 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


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

LevelSituationPhrase
CExternal, ongoing relationshipitsumo osewa ni natte orimasu (いつもお世話になっております)
CExternal, first contacthajimete go-renraku itashimasu (初めてご連絡いたします)
CExternal, after a long gapgo-busata shite orimasu (ご無沙汰しております)
BInternal, daytimeotsukaresama desu (お疲れさまです)
BInternal, morning threadohayō gozaimasu (おはようございます)

The rule

Common mistakes


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

Picking the level

LevelSituationPhrase
CExternalkabushiki-gaisha △△ no Yamada de gozaimasu (株式会社△△の山田でございます)
CExternal, softer tonekabushiki-gaisha △△ no Yamada desu (株式会社△△の山田です)
BInternal, other departmenteigyō-ika no Yamada desu (営業1課の山田です)
BInternal, same departmentYamada desu (山田です)

Common mistakes


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


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

LevelSituationPhrase
CUniversal (works internal + external)nani-tozo yoroshiku onegai mōshiagemasu (何卒よろしくお願い申し上げます)
CExternal defaultyoroshiku onegai itashimasu (よろしくお願いいたします)
CAfter an apologygo-meiwaku o o-kake shimasu ga, nani-tozo yoroshiku onegai mōshiagemasu (ご迷惑をおかけしますが、何卒よろしくお願い申し上げます)
CRequesting a replygo-kakunin no hodo, yoroshiku onegai itashimasu (ご確認のほど、よろしくお願いいたします)
BInternalyoroshiku onegai shimasu (よろしくお願いします)
BInternal, ongoing threadhikitsuzuki yoroshiku onegai shimasu (引き続きよろしくお願いします)

Common mistakes


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

LevelSituationContents
CExternalFull 5 lines + company address + URL
BInternal, same departmentFamily name alone is fine
BInternal, other department”Department + family name”

Common mistakes


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.

#CheckWhat to confirm
1Subject ≤ 20 full-width chars + bracketed category【ご相談】, 【日程調整】, etc.
2Addressee honorific is correctsama / san / kakui / onchū matches recipient type
3Family name spelling and kanji are right田中 vs. 田仲, 佐藤 vs. 佐東
4TO / CC / BCC are intentionalMass-send goes BCC; manager goes CC
5Greeting matches uchi-sotoExternal: osewa ni natte orimasu. Internal: otsukaresama desu
6Lines break at 15–25 full-width charsNo wall-of-text paragraphs
7Full-width / half-width is consistent”3つ” vs. “3つ” — pick one
8Attachment is attached + file name is external-safeAvoid “final_v3_fix.docx” type names
9No keigo gaps; sasete itadaku count ≤ 2Skim for honorific drift
10Closing + signature are in placeyoroshiku + 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

MisfireFirst move (within 30 seconds)
Wrong family nameSend a correction email (template below)
Wrong recipient in TO/CCCorrection email: “the previous message was sent in error — please disregard” + corrected version
Otsukaresama desu to an external clientCorrection email: brief apology + reissue with osewa ni natte orimasu
Forgot the attachmentCorrection email: “the attachment was missing from my previous message; re-sending now”
Confidential info in the wrong threadLoop 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.


You now have the scaffold. The next two moves are stocking up on finished templates and tightening your keigo accuracy.


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.

Get Essential 30 on Gumroad


Share this post on:

Previous Post
How to Say Sorry in Japanese Politely: 8 Scenarios with Email Templates
Next Post
Japanese Business Etiquette: 9 Rituals and the Exact Words for Each