Honorific Language Support
Honorific language support enables AI and applications to properly recognize and generate respectful Japanese expressions (keigo) based on social hierarchy, relationship, and formality context, maintaining cultural appropriateness in communication.
What is Honorific Language Support?
Honorific language support refers to the capability—in humans or automated systems—to identify, generate, and appropriately use keigo (敬語), the formal respectful expressions in Japanese based on hierarchical, social, and cultural context. This includes understanding when and how to apply respectful language (sonkeigo), humble language (kenjougo), and polite language (teineigo) based on relationships, status differences, group membership, and situational formality. AI and automation systems must parse relationship cues, dynamically select correct honorific levels, and mimic native speaker etiquette complexity.
Core elements:
- Specialized verb forms, noun forms, honorific suffixes/prefixes, sentence patterns
- Cultural sensitivity to age, status, group affiliation, situational formality
- Practical implementation in customer service bots, translation platforms, email automation, educational software
Core Categories: Three Main Types
| Type | Japanese | Purpose | Usage Context |
|---|---|---|---|
| Respectful Language (Sonkeigo) | 尊敬語 | Elevates actions of others | Toward bosses, customers, guests |
| Humble Language (Kenjougo) | 謙譲語 | Lowers self/in-group actions | When speaking to outsiders about self |
| Polite Language (Teineigo) | 丁寧語 | General politeness | Default formal speech |
Respectful Language (Sonkeigo)
Definition and Purpose
Elevates the listener or third party, especially superiors, customers, guests. Demonstrates respect using special verb forms and honorific prefixes.
Grammatical Features
Key transformations:
| Plain Form | Polite Form | Respectful Form |
|---|---|---|
| iku (go) | ikimasu | irassharu (respectful going) |
| kuru (come) | kimasu | irassharu (respectful coming) |
| suru (do) | shimasu | nasaru (respectful doing) |
| iu (say) | iimasu | ossharu (respectful saying) |
| taberu (eat) | tabemasu | meshiagaru (respectfully eating/dining) |
| miru (see/look) | mimasu | goran ni naru (respectfully viewing) |
| shiru (know) | shirimasu | gozonji (respectfully knowing) |
Syntax Patterns
Pattern 1: Special respectful verbs
Standard: Manager comes (manager ga kimasu) Respectful: Manager arrives (manager ga irasshaimasu—elevated form)
Pattern 2: O + verb stem + ni naru
Standard: Read (yomimasu) Respectful: Respectfully reading (oyomi ni narimasu)
Standard: Write (kakimasu) Respectful: Respectfully writing (okaki ni narimasu)
Pattern 3: Honorific prefix + noun
O-namae (お名前) – honorific name Go-iken (ご意見) – honorific opinion
Usage Examples
Business context:
The manager reviewed it. (Buchō ga goran ni narimashita)
The customer is here. (Okyaku-sama ga irasshaimasu)
Humble Language (Kenjougo)
Definition and Purpose
Lowers the speaker or in-group’s actions when speaking to outsiders/external people, expressing modesty. Used when the speaker or their organization speaks to people outside their group.
Grammatical Features
Key transformations:
| Plain Form | Polite Form | Humble Form |
|---|---|---|
| iku/kuru (go/come) | ikimasu/kimasu | mairu (humbly visit) |
| iu (say) | iimasu | mōsu, mōshiageru (humbly say) |
| suru (do) | shimasu | itasu (humbly do) |
| morau (receive) | moraimasu | itadaku (humbly receive) |
| taberu (eat) | tabemasu | itadaku (humbly eat) |
| miru (see) | mimasu | haiken suru (humbly view) |
| kiku (hear) | kikimasu | ukagau, haichō suru (humbly listen) |
| au (meet) | aimasu | ome ni kakaru (humbly meet) |
Syntax Patterns
Pattern 1: Special humble verbs
Standard: I say (watashi ga iimasu) Humble: I humbly state (watashi ga mōshiagemasu)
Pattern 2: O/Go + verb stem + suru
Standard: Guide (annai shimasu) Humble: Humbly guide (goannai shimasu)
Standard: Contact (renraku shimasu) Humble: Humbly contact (gorenraku shimasu)
Usage Examples
Business context:
My name is Tanaka. (Tanaka to mōshimasu—humble form showing deference)
I will humbly review the materials. (Shiryō wo haiken itashimasu)
I will humbly visit tomorrow. (Ashita ukagaimasu)
Polite Language (Teineigo)
Definition and Purpose
Universal polite speech form safe to use with strangers, in business, most formal situations. The standard register for respectful communication.
Grammatical Features
Core elements:
| Form | Structure | Example |
|---|---|---|
| Verb ending | ~masu | eat (tabemasu) |
| Copula | desu | student (gakusei desu) |
| Polite negative | ~masen | not go (ikimasen) |
| Past polite | ~mashita | saw (mimashita) |
Usage Examples
I’m going tomorrow. (Ashita ikimasu)
This is a book. (Kore wa hon desu)
I ate yesterday. (Kinō tabemashita)
Honorific Suffixes and Prefixes
Name Honorifics (Suffixes)
| Suffix | Kanji | Usage | Example | Notes |
|---|---|---|---|---|
| -san | さん | Neutral, most common | Tanaka-san | Safe default in all situations |
| -sama | 様 | High respect | Customer (okyaku-sama) | For customers, VIPs, deities |
| -kun | 君 | For male juniors/equals | Tarō-kun | Never use for superiors |
| -chan | ちゃん | Affectionate, casual | Yumi-chan | Children, close friends, pets |
| -shi | 氏 | Formal, written | Tanaka-shi | News reporting, official documents |
| -sensei | 先生 | Teachers, doctors | Yamada-sensei | Experts with specialized knowledge |
Noun Prefixes
| Prefix | Kanji | Usage | Example |
|---|---|---|---|
| o- | お | For Japanese-origin words | Ocha (tea), Onamae (name) |
| go- | ご | For Sino-Japanese words | Gokazoku (family), Goiken (opinion) |
Critical rule: Never use honorific language for yourself—always use it toward others.
Cultural Context: Uchi-Soto Dynamics
In-Group vs. Out-Group
| Concept | Japanese | Meaning | Members |
|---|---|---|---|
| In-group | 内(uchi) | Internal group | Family, company, close friends |
| Out-group | 外(soto) | External group | Customers, strangers, other companies |
Core Principle
When speaking to outsiders about in-group members:
- Use humble language for your side (even for company president)
- Use respectful language for their side
Example:
Incorrect: The president is here. (Company president + respectful language)
Correct: The president will visit. (Speaking to customer about own company president—use humble language)
Social Hierarchy Factors
Honorific level determination:
| Factor | High Status | Low Status |
|---|---|---|
| Age | Older | Younger |
| Position | Manager, senior | Junior, new employee |
| Experience | Veteran | Beginner |
| Customer status | Customer, client | Service provider |
| Situation | Formal event | Casual setting |
AI and Automation Applications
AI Chatbot Implementation
Requirements:
| Component | Description |
|---|---|
| Context awareness | Identify user status, relationship, formality level |
| Dynamic selection | Choose appropriate honorific type based on context |
| Consistency maintenance | Maintain speech level throughout conversation |
| Escalation handling | Adjust formality when context changes |
Workflow example:
User query analysis → Relationship identification → Formality level determination → Honorific type selection (customer → respectful + polite; company → humble + polite; general → polite) → Response generation → Consistency verification
Business Process Automation
Email automation:
| Scenario | Honorific Usage | Opening Example |
|---|---|---|
| Customer email | Respectful + polite | “Thank you always for your patronage” |
| Internal memo | Polite | “Everyone, good work today” |
| To supervisor | Respectful + polite | “Manager, I apologize for the inconvenience” |
Customer support automation:
def generate_greeting(user_type):
if user_type == "customer":
return "Thank you for visiting." # respectful
elif user_type == "employee":
return "Good work everyone." # polite
else:
return "Hello." # general polite
def describe_company_action(action):
# Use humble language for own company
return f"Our company will humbly {humble_verb(action)}."
def describe_customer_action(action):
# Use respectful language for customer
return f"Customer will respectfully {respectful_verb(action)}."
Language Learning Applications
Features:
| Feature | Implementation |
|---|---|
| Contextual scenarios | Simulated business calls, social encounters |
| Real-time feedback | Immediate honorific error correction |
| Level progression | Gradual complexity introduction |
| Cultural notes | Social context explanations |
| Practice exercises | Role-play across different status relationships |
Common Implementation Challenges
Typical Errors
| Error Type | Description | Example |
|---|---|---|
| Self-elevation | Using respectful language for self | “I respectfully go” (incorrect) |
| Insufficient respect | Using plain/humble for customer | “Customer will humbly come” (incorrect) |
| Mixed speech levels | Inconsistent honorific levels | Starting respectful, ending casual |
| Overuse | Excessive honorific prefixes sound insincere | Every word with honorific prefix |
AI-Specific Challenges
Context detection:
- Difficulty identifying subtle status cues
- Ambiguous user relationships
- Lack of previous interaction context
- Cultural nuance interpretation
Dynamic adaptation:
- Relationship changes mid-conversation
- Formality level shifts
- Group affiliation changes
- Situational formality variations
Mitigation Strategies
Technical solutions:
| Challenge | Solution |
|---|---|
| Context ambiguity | Default to safer polite form (teineigo) when uncertain |
| Status uncertainty | Use -san suffix universally |
| Speech consistency | Track conversation state |
| Error recovery | Graceful fallback to standard polite form |
Process solutions:
- Human review for critical interactions
- Customer feedback mechanisms
- Continuous model training
- Cultural expert consultation
Comprehensive Verb Transformation Table
| Meaning | Plain | Polite | Respectful | Humble |
|---|---|---|---|---|
| to be | da | desu | de irassharu | de gozaimasu |
| to go | iku | ikimasu | irassharu | mairu |
| to come | kuru | kimasu | irassharu | mairu |
| to do | suru | shimasu | nasaru | itasu |
| to say | iu | iimasu | ossharu | mōsu / mōshiageru |
| to eat | taberu | tabemasu | meshiagaru | itadaku |
| to drink | nomu | nomimasu | meshiagaru | itadaku |
| to see | miru | mimasu | goran ni naru | haiken suru |
| to hear | kiku | kikimasu | okiki ni naru | ukagau / haichō suru |
| to know | shiru | shitte imasu | gozonji | zonjimasu |
| to give | ageru | agemasu | kudasaru | sashiageru |
| to receive | morau | moraimasu | – | itadaku |
| to ask | kiku | kikimasu | otazune ni naru | ukagau |
| to meet | au | aimasu | oai ni naru | ome ni kakaru |
| to think | omou | omoimasu | oomoi ni naru | zonjimasu |
Practical Implementation Guidelines
For AI Developers
Design principles:
- Default to safer polite form when uncertain
- Implement context tracking across conversation
- Provide override mechanisms for edge cases
- Log honorific usage for quality improvement
- Enable cultural expert review workflows
Testing requirements:
- Multi-persona scenario testing
- Cultural appropriateness verification
- Edge case handling verification
- Consistency across conversation flow
- Performance under ambiguous input
For Business Users
Deployment guidelines:
| Use Case | Recommended Approach |
|---|---|
| Customer service | Respectful + polite, with escalation to human |
| Internal tools | Polite default, contextual adaptation |
| B2B communication | Conservative respectful, expert review |
| Learning applications | All levels with explicit instruction |
For Language Learners
Learning path:
Level 1: Master polite language (teineigo) Level 2: Learn respectful language basics (common respectful verbs) Level 3: Add humble language basics (essential humble forms) Level 4: Understand Uchi-Soto dynamics Level 5: Practice situational switching Level 6: Master advanced forms and nuances
Regional and Generational Variation
Regional Differences
| Region | Characteristics |
|---|---|
| Kansai (Osaka, Kyoto) | More casual honorific usage in daily life |
| Tokyo | Stricter business honorific standards |
| Kyushu | Unique dialectal honorific forms |
Generational Patterns
| Generation | Honorific Usage Pattern |
|---|---|
| Elderly (60+) | Strict adherence, traditional forms |
| Middle-aged (30-60) | Business-appropriate, socially flexible |
| Young adults (20-30) | Casual among peers, formal in business |
| Youth (under 20) | Minimal honorifics in casual settings |
Business context: Regardless of age, traditional honorifics remain essential.
Frequently Asked Questions
Q: What’s the safest honorific approach when uncertain?
A: Use polite language (-masu/-desu forms) with the -san suffix. This neutral approach is appropriate in most situations.
Q: Can AI perfectly replicate native honorific usage?
A: Current AI handles standard patterns well but may struggle with subtle cultural nuances requiring deep context understanding. Human review is recommended for critical interactions.
Q: How important is honorific language for foreigners?
A: Essential in business environments. Native speakers appreciate learner efforts and recognize sincerity. Proper honorifics significantly impact professional credibility.
Q: What happens when using incorrect honorifics?
A: Minor errors are typically forgiven, especially for non-natives. Major errors (self-elevation) can appear rude or ridiculous.
Q: How do I know when to switch honorific levels?
A: Follow the other person’s lead, consider the setting (business vs. social), and default to formal politeness when uncertain.
Implementation Guidelines
For AI developers:
- Default to polite form when uncertain
- Track conversation context
- Implement relationship detection
- Provide cultural expert review
- Create fallback mechanisms
For business deployment:
- Use for customer-facing support (respectful + polite)
- Use for internal tools (polite)
- Use for B2B (conservative respectful)
- Always allow human review for sensitive communication
Real-World Scenarios
Customer support: “お客様、お待たせいたしました” (Customer, thank you for waiting—respectful and apologetic)
Internal memo: “各位、お疲れ様です” (Everyone, good work—polite)
Company announcement: “弊社が皆様のご期待に応えるべく努めてまいります” (Our company will strive to meet expectations—humble and polite)
Key Takeaway
Honorific language support is critical for any Japanese AI system serving business customers. While not perfect, combining AI with human review for important communications handles 95%+ of scenarios correctly. Default to polite forms, maintain context awareness, and include cultural expertise in implementation.
Related Terms
Cost Estimation
A process for pre-calculating AI adoption costs (token usage, infrastructure expenses) and properly ...
Disambiguation
The process by which AI chatbots and virtual assistants clarify a user's actual intent when input ha...
Query Expansion
Query expansion is a technique that automatically adds synonyms and related terms to a user's search...
Zero-Shot Chain of Thought
Zero-Shot Chain of Thought is a prompt engineering technique for LLMs that instructs models to perfo...
Multi-channel Support
Multi-channel support is a customer service strategy providing support across multiple independent c...
Typing Indicators
Typing indicators are visual cues that display when someone is composing a message in chat apps. The...