Japanese Honorific Language (Keigo): A Practical Guide for Business

In Japan, keigo (honorific language) is a cornerstone of professional communication. The key to mastering it is not memorizing word forms, but first identifying whose action you are describing. If it is the other person's action, use sonkeigo (respectful form); if it is your own or your organization's action, use kenjougo (humble form); and use teineigo (polite form) to set the overall register of the sentence.

This guide is for new employees, job seekers, and business professionals who hesitate over keigo in emails and phone calls. It builds on Japan's Agency for Cultural Affairs (Bunkacho) Guidelines on Honorific Language (2007) and focuses on the confusion most common in real business settings. Research in professional training contexts suggests that most keigo errors come from misidentifying the subject of the action — once the habit of "determine the subject first" is established, accuracy improves significantly.

From a conversion table of common verbs to clear examples of double-honorific errors and "role + sama" mistakes, and ready-to-use templates for emails, phone calls, and in-person interactions — this guide treats keigo as a practical professional skill, not just a politeness convention.

What Is Keigo? The Three Core Types

Definition and Purpose

Keigo is the system for expressing consideration toward the person you are speaking to or about through the structure of your language. It is not simply about "choosing polite-sounding words" — the essence is adjusting the direction of respect in your language, depending on who is performing the action and who it is directed toward.

Its function goes beyond elevating the other person. Keigo smooths conversation and correspondence, calibrates social distance, and reduces unnecessary friction. In business, content accuracy matters — but how you communicate is equally evaluated. Think of keigo as a professional skill that makes consideration visible.

The Three Basic Types

For most practical purposes, three categories cover the majority of situations: sonkeigo, kenjougo, and teineigo. The key distinction is "the subject" and "the direction of respect."

Sonkeigo (respectful form) elevates the actions or state of the person you are speaking to or about. Examples: 「社長がおっしゃいました」("The president said") or 「お客様がいらっしゃいます」("The customer is here"). The subject is the other person, and respect is directed toward them.

Kenjougo (humble form) expresses your own or your organization's actions with humility, thereby honoring the person the action is directed toward. Examples: 「明日伺います」("I will visit tomorrow"), 「資料を拝見しました」("I have looked at the documents"). The subject is yourself, but respect flows toward the recipient of the action. This is why saying 「部長がおっしゃっていました」("The manager said," in respectful form) to an outside party is incorrect — you are elevating your own manager rather than humbling your organization to the client.

Teineigo (polite form) does not elevate or humble any particular subject — it simply makes the tone of the whole sentence polite for the listener. The core markers are 「です」, 「ます」, and 「ございます」. It can be added to any subject and any verb.

Note: The form 「〜れる・られる」can mean respectful, passive, or potential, and the correct reading depends on context. For unambiguous respect, use dedicated sonkeigo forms: for example, 「部長が言われました」could be respectful or passive, but 「部長がおっしゃいました」is clearly respectful.

The Bunkacho Five-Category System (2007)

For more precise analysis, the Bunkacho Guidelines on Honorific Language (answered February 2, 2007) establishes a five-category system: sonkeigo, kenjougo I, kenjougo II (choujougo), teineigo, and bikago (beautification language).

The common three-category framework is a useful entry point, but understanding that "humble form" splits into two categories — and that "beautification language" is separate — helps explain many common errors.

Kenjougo I expresses humility toward the recipient of your action — for example, 「伺う」(to visit/ask), 「申し上げる」(to say). These forms clearly honor the person your action is directed toward.

Kenjougo II (choujougo) expresses a formal, refined tone toward the listener rather than directly humbling yourself to a specific recipient — for example, 「参る」(to go/come), 「申す」(to say). For instance, 「東京へ参ります」("I am going to Tokyo") is not elevating the destination but speaking with formality to the listener.

Bikago adds elegance or refinement to language, as in 「お茶」(tea) or 「お手洗い」(restroom). Crucially, bikago does not inherently express respect for the listener. Adding 「お・ご」to anything does not automatically create a respectful expression — 「おビール」or 「おジュース」would sound unnatural in most business contexts.

Practical approach: learn the three-category framework first, then return to the five-category system when a specific expression is causing confusion — especially the 「伺う」vs. 「参る」distinction and the role of bikago.

Modern Keigo: Mutual Respect

The traditional view of keigo as a one-way tool for deferring to superiors has evolved. As the Bunkacho guidelines emphasize, contemporary keigo is understood through the lens of mutual respect — not a mechanism for elevating one party, but a linguistic tool for communicating without discomfort, regardless of formal hierarchy.

This means keigo is not only for use with clear superiors. It functions in first-contact situations with clients, applicants, phone callers, and anyone whose social position relative to you is unclear. It creates a register that is neither excessively familiar nor cold.

Common misuses — double honorifics like 「おっしゃられる」, combining role and title like 「社長様」— arise from the good intention of wanting to be polite. But quantity of honorific elements does not equal quality. An unnatural expression signals inexperience more clearly than a simpler form does.

Modern keigo prioritizes accuracy, clarity, and communicated consideration over maximalist deference. Choosing 「いらっしゃる」over the ambiguous 「おられる」, using dedicated respectful forms rather than the all-purpose 「〜れる・られる」— these are not just rules but expressions of the desire to communicate clearly.

Keigo Conversion Table: Sonkeigo, Kenjougo, and Teineigo

The most useful table presents the most commonly used forms in an immediately accessible format. Three columns are sufficient for most situations; the distinction between kenjougo I and II is noted only where it affects real-world choice.

In training contexts, the rows for 「言う」and 「行く」attract the most attention — being able to produce 「おっしゃる／申し上げる」and 「いらっしゃる／伺う」instantly changes the quality of phone conversations.

Common Verb Conversion Table

The critical axis: if the subject is the other person → sonkeigo; if the subject is yourself or your organization → kenjougo. For example, 「部長が申しました」is correct when referring to your own manager to an outside party — but if discussing a client's manager, use 「おっしゃいました」.

The teineigo column (rightmost) shows the polite base form. In actual usage, sonkeigo and kenjougo are built on top of teineigo: 「ご覧になります」, 「拝見します」.

The 「お・ご」Pattern for Nouns and Verbs

Beyond verb changes, the 「お・ご」prefix is frequent in business Japanese. The patterns:

• Respectful: お(ご) + verbal noun + になる — e.g., 「ご覧になる」, 「お待ちになる」
• Request (softened): お(ご) + verbal noun + ください — e.g., 「ご確認ください」
• Humble: お(ご) + verbal noun + する／いたす — e.g., 「ご案内する」, 「お送りいたします」
• Polished noun: お + noun — e.g., 「お名前」, 「お電話」; ご + noun — e.g., 「ご連絡」, 「ご説明」

General rule: 「お」for native Japanese words, 「ご」for Sino-Japanese (on-reading) words. But convention overrides the rule for established expressions — 「ごゆっくり」, 「お電話」, etc. When in doubt, use established forms rather than applying the rule mechanically.

Important: when a verb has a dedicated respectful form, use it. Say 「ご覧になる」not 「お見になる」for "see," 「召し上がる」not 「お食べになる」for "eat," 「おっしゃる」not 「お言いになる」for "say." Dedicated forms reduce ambiguity.

Commonly Confused Similar Forms

「伺う」vs. 「参る」: Both humble equivalents of "go" and "come," but different. 「伺う」is kenjougo I — it honors the person or place your action is directed toward: 「明日、御社に伺います」("I will visit your company tomorrow"). 「参る」is kenjougo II — it expresses formality toward the listener: 「ただいま参ります」("I am on my way"). Choose based on whether you are honoring a recipient or simply speaking formally.

「拝見する」: Humble form of "see," applicable to documents, emails, business cards, and more. Use 「拝見します」rather than the longer 「見させていただきます」— the shorter form is cleaner and less cumbersome.

「存じる」vs. 「存じ上げる」: For knowing facts, use 「存じております」. For knowing a person, use 「存じ上げております」. Example: 「その件は存じております」("I am aware of that matter") vs. 「田中様は以前より存じ上げております」("I have known Mr. Tanaka for some time").

「召し上がる」: Respectful form of both "eat" and "drink." Use 「どうぞ召し上がってください」rather than 「食べられますか」or 「飲まれますか」.

「いただく」: Humble form of "receive," but also humble form of "eat" and "drink." Context determines meaning: 「資料をいただく」(receive a document) vs. 「昼食をいただく」(eat lunch).

「差し上げる」vs. 「お送りする」: 「差し上げる」(humble form of "give") can sound slightly self-congratulatory in transactional business contexts. In many situations, 「お送りします」("I will send it") or 「お渡しします」("I will hand it to you") is more natural.

「承知しました」vs. 「かしこまりました」: Both are more formal than 「わかりました」. 「承知しました」is widely usable in both internal and external communication. 「かしこまりました」carries a more service-oriented register, common in customer-facing and phone contexts.

The Core Principle: Determine the Subject First

Decision Flow

Keigo becomes unreliable when you try to memorize forms without the subject-first habit. The practical decision sequence:

1. Identify the subject — who is performing the action?
2. If the subject is the other person/client/superior → sonkeigo
3. If the subject is yourself or your organization (including your own manager) → kenjougo
4. Set the sentence-level tone with teineigo (です・ます)

Example: you need to tell a client that your colleague Tanaka will visit. The subject is Tanaka — a person in your organization. To an outside party, Tanaka is "in-group," so: 「田中が後ほど伺います」("Tanaka will visit you shortly") or 「田中が後ほど参ります」("Tanaka will be there shortly"). Not: 「田中がいらっしゃいます」— that elevates your own colleague.

Conversely, if discussing the client's contact person coming to your office: subject is the other party → 「ご担当者様がいらっしゃいます」.

The phone handoff moment is the most common source of subject confusion. Within seconds, you switch between "the caller's message" and "our representative's response" — the subject flips, and errors like 「部長がおっしゃっております」creep in. Practicing a small mental check — "is the subject now the client or our team?" — reduces these errors noticeably.

Quick quiz:

1. You want to tell a client you will visit tomorrow: "明日、御社に伺います" or "明日、御社にいらっしゃいます"?

→ 「明日、御社に伺います」— subject is yourself.

1. Explaining your trading partner's manager's statement to a colleague: "部長が申しました" or "部長がおっしゃいました"?

→ 「部長がおっしゃいました」— subject is the other party's manager.

1. Conveying your own manager's statement to an outside party: "弊社部長がおっしゃっていました" or "弊社部長が申しておりました"?

→ 「弊社部長が申しておりました」— subject is in-group, speaking to outside party.

Inside vs. Outside Your Organization

The most error-prone boundary in keigo is in-group vs. out-group, not just senior vs. junior. When speaking internally, you show deference to superiors. When speaking to external parties, your own superiors become in-group and are humbled relative to the outside party.

To an outside contact: 「部長の田中が申しておりました」("Our manager Tanaka said..."), not 「部長の田中がおっしゃっていました」— the latter elevates your own manager to the external person.

Internal conversations follow their own logic: when your superior is the subject, use sonkeigo; when you are the subject, use kenjougo. The rule: inside = seniority-based; outside = in-group vs. out-group.

Phone calls are where this distinction comes up most frequently and most rapidly. Example: 「課長はただいま席を外しております。
戻りましたら、こちらからご連絡いたします」("Our section chief has stepped away from his desk. We will contact you when he returns.") Both the chief's status and your own action are in-group, so neither receives sonkeigo — the external party receives the overall politeness of teineigo.

In one sentence: when speaking to outsiders, do not elevate in-group members.

Kenjougo I vs. Kenjougo II: Simple Guide

Kenjougo I: honors the recipient of your action. 「伺う」, 「申し上げる」, 「拝見する」. Use when you are acting toward or for the other party. "I will visit your company" → 「御社に伺います」. "I will explain" → 「ご説明申し上げます」.

Kenjougo II (choujougo): expresses a refined, formal tone toward the listener, without specifically humbling yourself to a named recipient. 「参る」, 「申す」, 「おる」. "I am on my way" → 「ただいま参ります」. "My name is Takahashi" → 「高橋と申します」. "I am in the meeting room" → 「会議室におります」.

Practical heuristic: if your action is directed at or for the other party, think kenjougo I; if you are formally describing your own state or movement, think kenjougo II. For phone calls, having 「御社に伺います」, 「ただいま参ります」, and 「○○と申します」immediately accessible covers most scenarios.

Business Keigo in Practice: Emails, Phone Calls, and In-Person

Email Templates

In email, having ready-to-use patterns for five situations — opening, request, report, handoff, and closing — provides stability for most communications. Keep sentences to around 60 characters; use line breaks every 20–30 characters for readability. Avoid emojis and exclamation marks; adjust warmth through sentence-final expressions.

Sample request email:

Thank you for your continued support. This is Takahashi from Company A.

Regarding what we discussed the other day, I have attached the relevant documents.

I would be grateful if you could review the contents and share your feedback at your convenience.

With sincere regards,

Sample report email:

Thank you for your continued support. This is Takahashi from Company A.

I am pleased to inform you that the documents you requested were dispatched today.

We appreciate your patience as we await their arrival.

With sincere regards,

For external handoffs and conveying messages, the in-group/out-group principle applies directly. 「部長の田中が申しておりました通り、来週中にご回答申し上げます」("As our manager Tanaka stated, we will provide a response by next week.") — the in-group manager uses kenjougo, and the response is expressed humbly toward the external party.

Phone Call Templates

Phone calls require pattern knowledge more than phone calls anywhere else — there is no time to compose, and errors are hard to retract. Master four patterns: handoff, absence response, callback request, and conveying a superior's message.

For reducing misunderstandings, confirm: company name, person's name, purpose in that order. Example: "You are Ms. Yamada from Company A, calling for Tanaka in Sales regarding the contract — I have that noted."

Absence responses (convey only what is needed):

1. 「申し訳ございません。田中はただいま席を外しております。」
2. 「あいにく佐藤は外出しております。戻りましたら申し伝えます。」
3. 「ただいま会議中でございます。終了後、こちらからご連絡いたします。」

Callback requests:

1. 「かしこまりました。戻りましたら、折り返しご連絡するよう申し伝えます。」
2. 「承知いたしました。ご都合のよろしいお時間はございますか。」
3. 「念のため、お電話番号を確認させていただいてもよろしいでしょうか。」

Conveying your superior's message to an outside party:

1. 「部長の田中が申しておりました通り、本件は来週ご回答いたします。」
2. 「先ほど部長の田中が申しておりました件で、お電話いたしました。」
3. 「担当の佐藤が申しておりました内容を、あらためてご説明いたします。」

Note: 「部長の田中がおっしゃっていました」is unnatural for an external call — it elevates your own in-group member.

Handoff phrases:

1. 「少々お待ちください。担当におつなぎいたします。」
2. 「ただいまお電話をおつなぎいたしますので、そのままお待ちください。」
3. 「担当者に確認いたします。少々お時間をいただけますでしょうか。」

When taking a message: summarize without over-editing. "You wish to confirm the delivery timing for the contract documents — I will pass that on to Tanaka."

Greeting and Guiding Visitors

For visitor reception, having ready phrases for each micro-moment — entry, guidance, seating, serving drinks — prevents the halting impression of searching for words between each step.

At reception:

1. 「いらっしゃいませ。お待ちしておりました。」
2. 「本日はご来社いただき、ありがとうございます。」
3. 「恐れ入りますが、お名前を頂戴してもよろしいでしょうか。」

Guiding to a meeting room:

1. 「ただいま担当をお呼びいたします。」
2. 「会議室までご案内いたします。」
3. 「こちらへどうぞ。」
4. 「足元にお気をつけください。」

Inviting to be seated:

1. 「こちらでお掛けになってお待ちください。」
2. 「どうぞお掛けください。」
3. 「担当が参りますまで、少々お待ちください。」

Serving drinks:

1. 「お待たせいたしました。お飲み物をお持ちしました。」
2. 「どうぞごゆっくりお過ごしください。」
3. 「熱いので、お気をつけください。」

When you are the visitor:

1. 「お世話になっております。株式会社Aの高橋と申します。」
2. 「本日14時にお約束しております、高橋と申します。」
3. 「営業部の田中様にお取次ぎをお願いいたします。」

Simple expressions like 「本日はお時間をいただき、ありがとうございます」are entirely sufficient once inside. Complexity of expression matters less than correctly directed, naturally delivered keigo.

Common Errors and NG Examples

Double Honorifics (Nijuu Keigo): NG vs. OK

A very common error: stacking honorific elements out of a desire to seem polite, when the base form is already a complete honorific. The principle: do not add another honorific of the same type to a form that is already complete.

「〜させていただく」 is extremely useful but chronically overused. It is appropriate when you are performing an action with the other party's permission or under their consideration. For example, 「本日は休憩を取らせていただきます」is natural when the context involves the employer's approval. But 「資料を拝見させていただきます」overloads a simple viewing action — 「拝見します」is sufficient.

When checking double honorifics: ask "does this word already function as a complete honorific?" If yes, do not add another element of the same type. Politeness is achieved by reducing excess, not by adding more.

Referring to In-Group Members to External Parties

Role + title stacking: Because role titles (社長, 部長, 課長) already function as honorifics, adding 「様」after them is redundant and incorrect. 「田中社長」is natural; 「田中様」is natural; but 「田中社長様」is to be avoided. The same applies to 「部長様」, 「課長様」.

This is one of the most commonly flagged errors in business email review. Auto-populated signature lines often include titles, making it easy to accidentally add 「様」on top. A simple rule: either use the title, or use 「様」— not both.

When introducing in-group members externally: state the title as fact, but humble the action. 「弊社部長の田中が申しておりました」, 「担当の佐藤よりご連絡いたします」— the title is present, the action is in kenjougo.

「お・ご」 and Bikago

As noted earlier, bikago (e.g., 「お電話」, 「ご案内」, 「お茶」) adds elegance but is distinct from sonkeigo. The presence of 「お・ご」does not make an expression automatically respectful toward the other party.

Errors arise from mechanical application: 「おコピー」, 「ごメール」, or 「おミーティング」would all sound forced. Established phrases are natural; invented compounds are not.

Bikago also does not solve the in-group/out-group question. 「部長のお話」is gracious-sounding, but does not change whether the in-group/out-group principle is correctly applied.

Excessive 「お・ご」also makes text heavy and hard to read. 「ご確認のほどよろしくお願いいたします」is natural; 「お資料をご送付いただけますでしょうか」piles up unnecessary prefixes.

Checklist for Uncertain Situations

Five Checkpoints

1. Who is the subject?
2. Is the subject the other party or your organization?
3. Is the direction of respect correct?
4. Is there double-stacking of the same type of honorific?
5. Is a role title combined with 「様」?

First, confirm the subject. If the subject is the other party or their colleague → sonkeigo. If the subject is anyone in your organization, even your manager → kenjougo when addressing outside parties. This single check prevents a large proportion of keigo errors.

Second, verify in-group vs. out-group. Errors here come from role-confusion, not vocabulary gaps. Ask: "Am I elevating someone in my organization to an outside party?" If yes, switch to kenjougo.

Third, check the direction of respect: are you pointing sonkeigo at the right person? Are you using kenjougo I (for a specific recipient) vs. kenjougo II (for the listener in general) appropriately?

Fourth, check for double stacking. For any word that is already a complete honorific form, do not add another element that performs the same function.

Fifth, check role + title combinations in salutations, body text, and signatures. The rule is simple: title only, or 「様」only — not both.

A practical training approach: choose one "keigo target expression" each day, practice five variants with subject alternation, and build active recall rather than passive recognition. Repetition converts understanding into fluency.

Pre-Send Email Check

Before sending, review in four separate passes: content, keigo, visual readability, attachments.

• Subject line: is the purpose immediately clear?
• Salutation: is the name/title correct, no role+様 stacking?
• Body: are sentences within approximately 60 characters? Line breaks every 20–30 characters?
• Closing: does the sign-off match the tone of the message?
• Attachments: are they actually attached? File names correct?

Backup phrases to keep on hand:

• 「失礼ですが、お名前を頂戴できますでしょうか」
• 「恐れ入ります、少々お待ちくださいませ」
• 「差し支えなければ、ご都合のよいお時間をお知らせください」
• 「確認のうえ、改めてご連絡いたします」

Having a few safe, flexible phrases ready means language does not break down under pressure.

Next Steps for Improvement

Understanding keigo through reading is not enough for practical fluency. The fastest path: convert commonly used expressions into paired practice (subject A → sonkeigo; subject B → kenjougo), starting with the highest-frequency verbs.

For example, practice converting 「言う」、「見る」、「行く」、「待つ」、「確認する」in both directions. Add "whose action is this?" as a prompt with each example.

For external emails: make "am I elevating an in-group member?" your final check before sending. This one habit alone improves the overall impression of your keigo quickly. The goal is not mastering rare expressions — it is reliably applying the same checks each time, so email and phone language stabilizes across the board.