How to Write a Japanese Business Email: Keigo Guide
Learning how to write a Japanese business email means assembling the keigo you already know into the fixed tone and ritual structure of written correspondence (メール). The grammar is not new. The skill is knowing which stock phrase to use in each slot and what level of respect it encodes.12
Overview
Business email as applied keigo
A Japanese business email is an applied use of the honorific system, not a fresh grammar point. Every opener, closer, and request phrase is built from the same categories a learner has already studied, now combined into a conventional written register.
The 文化庁 (Agency for Cultural Affairs) classifies keigo into five categories, and Japanese business email draws on all of them.12 The pillars assumed here map onto that system as follows.
| Category | 文化庁 definition (abridged) | Listed examples |
|---|---|---|
| 尊敬語 (respect) | 相手側又は第三者の行為・ものごと・状態などについて，その人物を立てて述べるもの | いらっしゃる, おっしゃる, なさる, 召し上がる, お使いになる, 御利用になる2 |
| 謙譲語I (humble, directed) | 自分側から相手側又は第三者に向かう行為・ものごとなどについて，その向かう先の人物を立てて述べるもの | 伺う, 申し上げる, お目に掛かる, 差し上げる, お届けする2 |
| 謙譲語II / 丁重語 (courteous) | 自分側の行為・ものごとなどを，話や文章の相手に対して丁重に述べるもの | 参る, 申す, いたす, おる, 拙著, 小社2 |
| 丁寧語 (polite) | 話や文章の相手に対して丁寧に述べるもの | です, ます, （で）ございます2 |
| 美化語 (beautifying) | ものごとを，美化して述べるもの | お酒, お料理2 |
The claim that email is assembled keigo is editorial framing. What is sourced is the category each formula breaks down into, and those breakdowns are the spine of this article.
Email vs letter vs chat: where this register sits
Business email sits between casual chat and the ceremonial paper letter (手紙). It is conventionally simpler than a letter. The 頭語/結語 salutations a letter requires are normally dropped: gakumado states that 拝啓 and 敬具 are 原則不要 in a business email.3
In other words, the 頭語/結語 pairs such as 拝啓・敬具 that a formal letter requires are normally dropped in email.43 In their place, the letter's 拝啓-plus-seasonal-greeting slot is filled by a short greeting such as お世話になっております. The 敬具 slot is filled by a closing formula such as 何卒よろしくお願いいたします.3
JLPT level and what you should already know
This is N3 / N2 application material. It assembles already-learned keigo into a written register rather than introducing one new grammar point at a single level.
The component grammar is N4-level receiving and request grammar (～てもらう / ～ていただく, ～ていただけませんか).56 You should already have control of 丁寧語 (です・ます), the productive お〜になる (sonkeigo) and お〜する (kenjōgo) patterns, and the irregular verb tables such as いらっしゃる, 召し上がる, 伺う, 申す, and 拝見する.12
The structure of a business email
The skeleton: 件名 → 宛名 → 挨拶 → 本文 → 結び → 署名
A business email body is conventionally built from a fixed sequence. Native business-manner sources list it as 宛名 → 前文（挨拶文）→ 本題 → 結び → 署名, with 件名 as the subject line and a 名乗り (self-identification) inside the opening.78
The order is not decorative. Skipping the greeting and jumping straight to the request can read as abrupt and over-Western. The ritual blocks signal that the writer is observing the conventions of the relationship.
Each block has one job. 件名 is a scannable summary of the request. 宛名 is the addressee with the correct 敬称. 挨拶 is the opening formula. 本文 is the message proper, often 名乗り then 要旨 then 詳細. 結び is the closing formula. 署名 is the sender block.78
Subject line (件名)
The subject should let the reader grasp the business at a glance without opening the mail. Keep it short enough to read in the inbox list. A vague subject competes with dozens of others in an inbox and gets deferred.
Patterns such as 【ご連絡】 or 【お願い】 at the head of the subject line let the reader sort the request type before reading a word of the body. The tag classifies; the rest of the line specifies.
Addressing the recipient (宛名): 様, 御中, 各位
The 敬称 you attach depends on whether you are addressing a person, an organization, or a group.
| 敬称 | Used for | Rule |
|---|---|---|
| 様 | A named individual | Conventional order is 会社名＋部署名＋相手の名前＋様79 |
| 御中 | An organization | 企業や部署、官公庁、学校などの組織・団体に対して使用します9 |
| 各位 | A group of people at once | Itself a 敬称, so not rude even when superiors are included7 |
Never combine 御中 and 様 on the same name. Doing so duplicates the honorific: an organization takes 御中 only, and an individual takes 様 only.9
Opening formulae (書き出し)
お世話になっております: the default opener
The standard opener to an existing contact is お世話になっております.10118 It reports an ongoing relationship rather than a single past favor: "「お世話になっております」は過去から現在にかけての関係性に対しての言葉."10
The phrase breaks down cleanly. It raises the verb 世話になる ("to be looked after") with the beautifying お- prefix and renders いる as the courteous おります, the 丁寧語 form.11 The 文化庁 treats お世話になっております as a set expression of gratitude toward the other party.111
お世話になっております。8
"Thank you for your continued support."
Dialling formality up: 平素より大変お世話になっております
For clients and senior contacts, the opener can move up in formality to 平素より大変お世話になっております, with the variant 平素は大変お世話になっております.
The increase in formality is lexical, not categorical. 平素 means "habitually" or "ordinarily," and 大変 or 誠に are intensifiers. The keigo category does not change.
First contact: 初めまして and お世話になります
お世話になっております presupposes a prior relationship, so it is not appropriate for a true first contact: "初めての相手に対して『お世話になっております』という表現を利用することは不適切です。"10
The tense distinction matters. お世話になります carries a future expectation, while お世話になっております covers the past-to-present relationship: "「お世話になります」は未来の関係性への予測や期待が込められています."10
For a genuine cold open, native guidance offers set lines such as 突然のご連絡失礼いたします, 初めての連絡となりますが, 初めてメールをお送りいたします, and 〇〇様のご紹介でご連絡させていただきました.10 These phrases mean that you are contacting the person for the first time, or through someone else's introduction.
突然のご連絡失礼いたします。10
"Please forgive my sudden message."
初めてメールをお送りいたします。10
"I am writing to you for the first time."
The placeholder 〇〇 below is part of the verbatim formula. It marks where the referring party's name goes.
〇〇様のご紹介でご連絡させていただきました。10
"I am contacting you on the introduction of Mr./Ms. ___."
Internal vs external openers
The uchi-soto split shows up in the choice of greeting. The in-house opener is お疲れ様です, while the client-facing opener is お世話になっております.8
お疲れ様です。8
"Thank you for your hard work." (in-house opener)
Closing formulae (結び)
よろしくお願いいたします and 〜申し上げます
The standard closing is よろしくお願いいたします.12 It breaks down as お (prefix on 願い) plus いたします, where いたす is the 謙譲語II form of する and ます is 丁寧語.12
This combination is correct, not over-stacked. In 文化庁-aligned analysis, the productive お(ご)〜いたす pattern combines 謙譲語I and 謙譲語II. Two different honorific types are combined, rather than the same type stacked, so it is not 二重敬語.1314
よろしくお願いいたします。12
"Thank you in advance for your cooperation."
The elevated form swaps the 謙譲語II いたす for the 謙譲語I 申し上げる, which 文化庁 lists among 申し上げる, 伺う, 拝見する, and お届けする.2 That single substitution raises the level of deference.
何卒よろしくお願い申し上げます。12
"I sincerely ask for your kind cooperation."
When いたします is an auxiliary (補助動詞), as in お願いいたします, it is conventionally written in hiragana, not as お願い致します, in formal and official writing.12
Quick-note closers: 取り急ぎご連絡まで
For a brief stopgap message, the closer 取り急ぎご連絡まで signals that only the essentials are being passed along: "「取り急ぎご連絡まで」とは，『ひとまず急ぎで用件だけをお伝えします』という意味."15 Here 取り急ぎ means "for now, in a hurry" (とりあえず急いで), and the trailing まで omits a verb such as いたします.15
取り急ぎご連絡まで。15
"Just a quick note to let you know."
Because 取り急ぎ implies hurried, stopgap handling and the まで-ending drops the predicate, it can sound abrupt with clients or superiors and is best avoided upward.15 A politer rewrite keeps the full predicate.
まずはご連絡のみにて失礼いたします。15
"For now, please excuse this being only a brief note."
Letter-style sign-offs: 拝啓・敬具, 前略・草々
Formal paper letters open and close with paired 頭語/結語: 拝啓 pairs with 敬具 for a full letter, and 前略 pairs with 草々 for an abbreviated one.43 For higher ceremony, 謹啓 pairs with 謹白.4
Email normally omits these pairs; gakumado notes that 拝啓 and 敬具 are 原則不要 in a business email.3 They appear here so you recognize them, not so you use them in email. The 前略・草々 pair in particular signals that the opening pleasantries have been omitted. It can read as cutting corners, so it is treated as inappropriate for important or first correspondence.4
Stock phrases and the keigo behind them
Cushioning phrases (クッション言葉)
クッション言葉 are softeners placed before the main point when making a request, asking a favor, or declining, so the message does not sound too blunt.16 Common request cushions include 恐縮ですが, 恐れ入りますが, お手数をおかけしますが, お忙しいところ恐れ入りますが, and ご面倒をおかけしますが.1617
A cushion sets up the request that follows it. お忙しいところ恐れ入りますが introduces a request made of a busy reader. お手数をおかけしますが prefaces a task that puts the reader to some trouble.16
Making requests: 〜していただけますでしょうか
Requests sit on a ladder of deference. 〜てください is the plain polite request. 〜ていただく is the humble form of 〜てもらう. 〜ていただけませんか and 〜ていただけますか are negative- or potential-based polite requests. 〜していただけますでしょうか adds でしょうか for extra deference.56
The question form is softer because it leaves room for refusal. 〜ていただけませんか literally asks "could I not receive the favor of your doing X." It reads as more deferential than a direct order.5
ご確認いただけますでしょうか。18
"Could you kindly confirm this?"
Respecting the reader's actions: ご確認ください, ご査収ください
To request an action from the reader, attach the respectful ご- prefix to a Sino-Japanese noun and follow with ください, as in ご確認ください and ご査収ください.19 The default prefix split puts ご- on 漢語 and お- on 和語.
The two are not interchangeable. 査収 means "examine well and then receive." ご査収ください is for sending attachments or documents to be checked and kept, whereas ご確認ください carries no "receive" sense and is used when there is only content to check.19
添付の資料をご査収ください。19
"Please find the attached documents and check them over."
The 〜ください ending has an imperative flavor, so it can read as curt to a superior. Politer forms keep the request open with のほど or expand it with くださいますよう.19
ご査収のほど、よろしくお願いいたします。19
"I would appreciate it if you would check the attached."
Humbling your own actions: 〜いたします, 拝見しました, 存じます
For the writer's own side, the productive お(ご)〜いたす pattern supplies many of the humble verbs: お送りいたします, ご連絡いたします.14 Its 謙譲語I plus 謙譲語II makeup is exactly why it is correct rather than over-stacked.1314
Alongside it are the irregular humble forms: 拝見する (謙譲語I, the humble verb for 見る) and 存じる (a 謙譲語II-side humble for 思う and 知る).2
Forms such as 拝見いたしました and 〜と存じます lower the writer's own side. They pair with reader-side sonkeigo to keep the uchi-soto asymmetry consistent.2
Reporting and apologizing: ご連絡いたします, 申し訳ございません
A routine report uses ご連絡いたします. The standard apology is 申し訳ございません, which 誠に intensifies into the more emphatic 誠に申し訳ございません.1420
申し訳ございません comes from 申し訳ない ("there is no excuse"), with the ない part expressed through ございません, the 丁寧語 of ある. That makes it the most formal everyday apology grade, above 申し訳ありません.20
申し訳ございません。20
"I am very sorry."
Nuance and usage contexts
How relationship age changes the opener
The opener tracks the state of the relationship. A first email cannot honestly open with お世話になっております, which presupposes prior dealings. It calls for お世話になります or a first-contact line instead.10
By the hundredth exchange, お世話になっております is settled ritual rather than a fresh claim. Using the higher-formality 平素より大変 version for an important message keeps it from reading as hollow boilerplate.10
In-house, client, and superior registers
The same message shifts by uchi-soto. In-house, the opener is お疲れ様です; to a client, it is お世話になっております.8
The closing rises in step. To a client or superior, it moves from よろしくお願いいたします to 何卒よろしくお願い申し上げます, swapping in the 謙譲語I 申し上げる.214
When passive sonkeigo fits a written line
Japanese also forms respect for the reader's actions with the passive 〜られる, a lighter alternative to the fuller お〜になる sonkeigo. The dedicated article on respectful uses of the passive covers the mechanics of that passive-as-respect form and when it reads as natural rather than ambiguous.
In written business prose, the trade-off is between the lightness of 〜られる and the explicit respect of お〜になる. This article does not assert a fixed rule for which to prefer in email. That choice belongs to the passive-sonkeigo discussion, where it is grounded properly.
Good to know
Double keigo (二重敬語) in writing
二重敬語 means stacking the same honorific type twice on one word, which 文化庁 defines as "一つの語について，同じ種類の敬語を二重に使ったもの。"1 Its verdict is blunt: "「二重敬語」は，一般に適切ではないとされている。"1
The 文化庁 example is お読みになられる, where the sonkeigo お読みになる is already complete and the sonkeigo られる is added on top.13 The fix is to remove one layer and use お読みになる.13
お読みになられる。13
"(incorrect double keigo for) to read"
Two related forms are not errors. 文化庁 lists some double-keigo forms as established by custom and therefore acceptable, including respectful お召し上がりになる and お見えになる, and humble お伺いする, お伺いいたす, and お伺い申し上げる.13 Separately, 敬語連結 means linking two individually honored verbs with て, such as お読みになっていらっしゃる. It is allowed when each honorific is appropriate on its own, because it is not the same type stacked on one word.13
Self-honoring slips
A writer must humble their own actions with 謙譲語I or II and never elevate them with 尊敬語. The 文化庁 split is explicit: 尊敬語 is for the other party's or a third party's actions ("相手側又は第三者の行為"), and 謙譲語 is for your own side's actions ("自分側").2
Applying a respectful ご- to your own act inverts the system and quietly elevates yourself in front of the reader. The writer's side goes down. The reader's side goes up.2
御 readings: お vs ご vs おん
The default prefix split is お plus 和語 (native Japanese words) and ご plus 漢語 (Sino-Japanese words). That is why it is お願い (和語 願い) but ご確認 and ご連絡 (漢語 確認・連絡).
The same character 御 also reads おん in the fixed addressing word 御中 (おんちゅう).9
"Looked after" is not literal
お世話になっております is a phatic ritual, meaning a social-contact phrase, not a literal claim of being cared for. 文化庁 treats it as a set あいさつ and 感謝 expression, and bmb.jp frames it as acknowledging the relationship rather than describing real care.110
A memory hook for keeping it in the right slot: treat お世話になっております as the email handshake, the line you offer when making contact before any business is done. This is a learner aid, not a grammatical rule.
Why email avoids 拝啓/敬具
The 頭語/結語 pairs (拝啓・敬具, 前略・草々) belong to ceremonial paper letters. Business email developed a lighter convention in which 拝啓 and 敬具 are 原則不要.43
In their place, email uses お世話になっております for the 拝啓-plus-seasonal-greeting slot and 何卒よろしくお願いいたします for the 敬具 slot.43
See also
- Keigo Grammar Overview: How to Conjugate Honorific, Humble, and Polite Verbs
- How to Choose the Right Keigo Level: A Practical Guide
- Asymmetric Keigo: Humbling Your Own Boss (Uchi-Soto)
- Common Keigo Mistakes: 二重敬語 & Baito Keigo
- Japanese Giving and Receiving Verbs: あげる, くれる, もらう