Japanese Business Phone Etiquette | Answering, Calling, and Transferring

In Japan, every business phone call is answered in the company's name, which means the person who picks up the phone shapes the caller's entire impression of the organization. This guide organizes the essential patterns for receiving calls, making calls, and transferring — covering everything from your opening phrase to putting callers on hold, handling absences, and taking messages.

The most common stumbling points in new employee training are the same everywhere: an uncertain opening, missing the caller's name or contact number, and leaving callers on hold too long. Knowing when to say "moshi moshi" (and why to avoid it at work), how to transfer gracefully, and how to handle voicemail, recording laws, and training standards are all covered here. The goal isn't just knowledge — it's building a consistent, reliable pattern that anyone can execute.

Business Phone Basics | Five Core Principles

Answer by the Third Ring, and Nail the Opening

In Japanese business culture, the standard is to answer within three rings. This minimizes the sense that the caller was kept waiting, and signals that your team is ready. If you do miss the three-ring window, don't just launch into your opening as if nothing happened — acknowledge the wait with a brief word and move on.

The most important thing about your opening is this: you're speaking as a representative of the company. Keep your voice warm and clear — not flat. Speak at a slightly relaxed pace, and finish your sentences completely. Since callers can't see your face, smiling slightly while you talk actually comes through in the tone.

The standard format for identifying yourself: company name → department → your name. For example: "Thank you for calling. This is [Name] from the [Department] at [Company Name]." This gives the caller immediate confirmation that they've reached the right place.

OK vs. NG:

OK: "Thank you for calling. This is [Name] at [Company Name]." NG: "Hello, this is [Name]."

For missed calls and call-backs, don't just leave the caller guessing. If you're returning a call, say clearly: "Thank you for calling earlier. I'll have [Name] return your call shortly." This tells the caller what to expect next.

Cut Mistakes with Repetition and Notes

Most phone call errors don't come from how you speak — they come from failing to confirm. The most common gaps: mishearing the caller's company name, getting the name wrong, missing the contact number, the matter, or the date and time. The solution is simple: repeat back and take notes, in the moment.

For example: "So that's Ms. Yamada from Yamada Trading, calling about the meeting schedule next Tuesday — is that correct?" Breaking confirmation into short segments is more accurate than trying to confirm everything in one go. People who are nervous on the phone try to hold it all in memory — but in real business, writing it down is far more reliable than remembering.

Every message note should cover the minimum: caller's company and name, date and time of the call, the matter, a callback number, whether a callback is needed, and the name of the person who took the call. Templates for this exist because phone communication is one area where structured forms dramatically outperform free-form notes.

{{OGP_PRESERVED_0}}

Why to Avoid "Moshi Moshi" at Work

Saying "moshi moshi" (もしもし) when answering a business call is generally considered a bit casual. It's fine at home, but on a company line, the caller needs to immediately know who picked up — not just a generic greeting. The priority is identifying who and where.

When your company name comes first, the caller instantly knows they've reached the right place. That's more useful than any vocal warm-up. In practice, the reflex to say "moshi moshi" is a habit — fixing it isn't about understanding the rule, it's about drilling your opening phrase until it comes out automatically. Once "Thank you for calling, [Company Name], [Name] speaking" becomes reflex, the old habit disappears.

End Calls Cleanly

A phone call isn't over when the conversation ends — it's over when you hang up. The standard: let the caller hang up first. If you hang up first with force, all the polite phrasing you used beforehand gets undercut by a sharp click at the end.

The sound of hanging up is something that's easy to overlook — but trainers often cite examples where callers remembered a jarring hang-up sound long after everything else was forgotten. Use your hand to gently press the cradle down when the call ends. That one action is part of professional phone etiquette.

After releasing a hold, the same care applies. Say "Thank you for your patience, goodbye" and wait a moment before putting the phone down.

A Note on Terms: "Outou" vs. "Taiou"

The Japanese terms denwa outou (電話応対) and denwa taiou (電話対応) are used interchangeably in practice, but there's a subtle difference. Outou (応対) focuses on the interpersonal quality of the exchange — how you engage with the caller. Taiou (対応) leans more toward handling the task — processing the request, resolving the issue.

When discussing manner of speech, tone, and the craft of listening, outou fits better. When talking about the full workflow — callback arrangements, absence handling, logging — taiou is appropriate. This guide uses both terms as they naturally appear in practice.

Receiving vs. Calling vs. Transferring

These three situations look similar but have different objectives. When receiving a call, your primary goal is accurately capturing the caller's needs — that means identifying yourself clearly, getting the caller's company and name, their matter and contact number, and confirming by repeating back. When making a call, the focus shifts to conveying your needs concisely — that requires checking whether the timing is convenient, and stating your conclusion first. When transferring, the goal is connecting the caller to the right person accurately — who they're asking for, a brief summary of the matter, and whether a callback is needed if the person is unavailable. The failure modes differ too: for incoming calls it's missing names; for outgoing calls it's rambling; for transfers it's wrong connections and message gaps.

How to Receive Calls | From Opening to Confirming the Matter

Opening Line and Identification Order

Incoming calls create their first impression within seconds. The general standard is to answer within three rings, and your opening should not be "moshi moshi" — it should identify your company and department. The standard format: brief thank-you → company → department → your name. "Thank you for calling. This is [Name] from the [Department] at [Company Name]."

This sequence matters because the caller receives your voice as the company's representative. Speak clearly to the end of each sentence — if you rush through and the company name gets garbled, you've just created work for yourself because the caller will need to ask again. Short as it is, cutting any part creates more confusion, not less.

The standard flow for receiving a call:

1. Notice the incoming call and pick up
2. Deliver your opening: "Thank you for calling. [Company Name], [Name] speaking."
3. Ask for the caller's company and name
4. Confirm the matter
5. Repeat back the key information, then transfer or respond
6. Close with a polite goodbye and hang up gently

Small phrasing differences make a real impact. "Could you hold for just a moment?" sounds professional; "Wait a second" sounds casual. The same content, delivered through the standard template, creates a consistently better impression.

Confirming and Repeating Back the Caller's Name and Company

Right after your opening, your next priority is accurately confirming the caller's company name and name. This is where the most common incoming call errors begin. Unlike exchanging business cards, there's no visual reference — if you assume you heard correctly and move forward, the transfer or message can go wrong.

The standard way to ask: "May I ask your company name and your name, please?" Once the caller has introduced themselves, repeat back their company and name separately. "So that's Ms. Yamada from Yamada Trading, is that right?" gives the caller a clear chance to correct you.

For unfamiliar company names — which are especially prone to misunderstanding — one reliable practice is to write it out phonetically first, then confirm. "Excuse me, could you help me confirm the spelling? For the company name, I have [Katakana spelling] — is that right?" For personal names, "Could we confirm your name character by character?" or "How would you write your name in kanji?" raises the accuracy of message notes significantly. This extra step prevents downstream confusion.

When you can't hear clearly, don't try to confirm everything at once. Confirm company, department, and name separately so neither party loses track. Repeating back is a verification step — it's professional, not presumptuous. Most callers receive it as a sign of care.

Summarizing and Noting the Matter

After confirming who you're speaking with, summarize and receive the matter in a brief form. A useful phrase here: "What is this regarding?" This opens the floor without being blunt. Once the caller explains, repeat back: "So this is about [matter], regarding [detail] — is that correct?" Confirming with a summary makes the subsequent transfer or response much cleaner.

When noting the matter, don't try to retain everything in your head — jot down key terms first. The most commonly missed items are dates, quantities, product numbers, amounts, and callback details. Pull out single words: "next Wednesday," "10am," "estimate," "model AB123," "callback requested." Notes that a third party can act on later are better than notes only you can decode.

A structured template beats free-form notes every time:

With this template in place, handoffs lose far fewer details. The quality of phone etiquette isn't just in how you speak — it's in the notes you leave.

{{OGP_PRESERVED_1}}

Phrases for Asking Someone to Repeat

Unclear connections are inevitable. If you proceed with guesswork, the transfer or message will have errors. Asking someone to repeat themselves is not rude — it's confirming for accuracy. Ask briefly, politely, and target the specific gap.

Standard phrases:

• "I'm sorry, could you give me your name one more time?"
• "I apologize, the line is a little faint on this end."
• "Could you confirm the company name for me?"
• "Could you spell that out for me, letter by letter?"
• "Let me read that back: [details]. Is that correct?"
• "I have the date as [month] [day] at [time] — confirming that now."

The key: don't just say "Huh?" or "What?" Identify what you didn't catch. If only the name was unclear, ask only about the name. For numbers, repeat back in segments: "03," "090," etc. For model numbers or abbreviations, go character by character.

OK vs. NG at a glance:

• OK: "Could you hold for just a moment?"

NG: "Wait a second."

• OK: "I'm sorry — could you give me your name one more time?"

NG: "What did you say?"

• OK: "Let me confirm — that's [X], correct?"

NG: "I think it was [X], right?"

• OK: "Let me check with the person responsible and connect you."

NG: "I think they're in, so I'll switch you over."

• OK: "I'm sorry, they've stepped away. Shall I have them return your call?"

NG: "They're not in."

Before transferring, confirm the name of the person you're connecting to and repeat it back before putting the caller on hold. "That's for Yamada in Sales, is that right? One moment, please." Decide at this point whether you can handle the matter yourself or need to transfer.

Closing the Call

Once the matter has been handled or transferred, wrap up with a brief acknowledgment: "Understood" or "Certainly," then close the call. Standard closing phrases: "Thank you for calling today" and "Goodbye." Ending without any closing phrase after a detailed conversation leaves an abrupt impression.

If, after transferring, the person turns out to be unavailable, guide the caller with: apology first, then the absence, then a next step. "I'm sorry, [Name] has stepped away. Shall I have them return your call once they're back?" This gives the caller a clear path forward.

The phone call runs through to the moment you hang up. Let the caller hang up first, then place the phone down gently. The conversation can be perfectly handled, but a sharp hang-up sound at the end sticks in memory. Incoming calls follow a consistent pattern: introduce yourself, confirm, summarize, repeat back, and hang up cleanly. Keep that pattern intact and even a beginner can deliver reliable results.

How to Make Calls | Preparation, Timing, and Structure

Checklist Before You Dial

Making a call puts the other person at a slight disadvantage — they're receiving your call without preparation, so the preparation gap shows immediately in the quality of the conversation. Don't just organize the matter in your head — jot down a short note before dialing. The three things to nail down: what this is about, what you're asking for, and how you want the call to end.

Write down not just the purpose and goal but any specific information you'll need to reference: project name, order number, date options, quantities, deadlines. If you call about a delivery schedule without the order number, or call to discuss a quote without the quote in front of you, the conversation stalls. Know the contact's name, department, and direct extension. Prepare a message or alternative in case they're unavailable — this avoids ending with just a callback request and reduces burden on the other party.

A practical pre-call checklist:

• Can you state the purpose in one sentence?
• Is the goal of the call clear?
• Do you know the conclusion you want to reach?
• Do you have the case name, order number, dates, and other specifics in front of you?
• Do you have the contact's name, department, and extension?
• Have you prepared a message and alternative in case they're unavailable?

With this prep in place, the call runs noticeably more smoothly. Training exercises show that people who write out "conclusion, supporting reason, question to confirm" in three lines before calling produce tighter, more purposeful calls.

Times to Avoid and Timing Consideration

Timing matters as much as what you say. Even a perfectly relevant call leaves a bad impression if it lands at the wrong time. Times generally best avoided: right at the start of business, during the lunch hour, near the end of the day, and Monday mornings. The start of the day tends to be heavy with internal updates and email catch-up; lunch often means empty desks; end of day brings deadline pressure; Monday morning is filled with week-start planning and meetings.

Also easy to overlook: the other party's busy period by function. Accounting is overwhelmed at month-end; recruiting is slammed during hiring season; sales teams are heads-down at quarter-end. This awareness separates rote politeness from genuine consideration.

Once connected, before launching into your purpose, check whether the timing is convenient: "Do you have two or three minutes?" This gives the other person a chance to say whether now works or whether they'd prefer a callback. "Got a minute?" is vaguer and can feel presumptuous in a business context.

OK vs. NG:

• OK: "Do you have two or three minutes right now?"

NG: "Got a minute?"

• OK: "I'll get straight to the point."

NG: "Uh, I had something to, um, ask about..."

Short calls in particular are defined by that opening consideration. Avoiding the wrong time, checking convenience when connected — these two steps alone prevent most ill-timed call impressions.

Structure and Leading with the Conclusion

On outbound calls, getting the sequence wrong leaves the other person listening without knowing where the conversation is going. The basic structure: greeting, your company and name, confirm who you're reaching, check timing, state your conclusion first, add details, indicate how long it will take.

In practice, it sounds like: "Good afternoon, this is [Name] from [Company]. Is [Contact Name] from [Department] available?" Then once connected: "Thank you for taking my call. Do you have two or three minutes?" Then: "I'll get right to it — I'm calling about next week's meeting schedule." From here, the other person knows who's calling, why, and what they need.

Follow with specifics: "I'm considering [Date A] or [Date B]. The reason I'm calling today is that we need to confirm with the other party before the end of this week, so I wanted to get your thoughts." When the reason follows the conclusion, the whole exchange is more focused. Starting with context and building to the conclusion loses people along the way.

Indicating call length also helps: "Just one quick thing" or "This should take two or three minutes" allows the other person to settle in. Starting with no time indication makes them brace for a long call. On outbound calls, the most respectful approach is to make it easy for the other person to participate — that means giving them structure, not just conveying your needs.

Wrapping Up Outbound Calls

The ending of a call is remembered as much as the content. Once the matter is settled, close in order: thank you, confirm the next action and deadline, goodbye. For example: "Thank you for your time. I'll send the estimate by tomorrow morning. Looking forward to working with you."

Avoid vague closings: "Talk later" or "Apologies for the rush" can land as casual in a business context. The standard closing is "Thank you, goodbye." If you're waiting for a callback, close with "I'll be looking forward to your call — thank you, goodbye" so the next step is clear.

As with incoming calls, let the other party hang up first. If you cut off while they're still adding a final thought, it can feel abrupt. Hang up gently.

Minimum English Phrases

For outbound calls in English, the structure is the same: identify yourself, confirm who you're reaching, check timing, state your purpose briefly. A useful opener: "This is [Name] from [Company]. May I speak to [Name]?" It puts your company and name first and clarifies who you need.

Once connected: "Do you have two or three minutes?" is a close equivalent to asking whether now is convenient. To open the matter: "I'm calling about the meeting schedule." One sentence, up front — no long preamble.

What trips people up in English phone calls is usually not vocabulary — it's not having a set opening. Knowing your company name, your name, the contact's name, and one sentence about your purpose is enough for most business calls.

How to Transfer Calls | Connecting to Staff and Handling Absences

Transferring When the Person Is Available

The first step in any transfer: confirm exactly who the call is for. Transferring based on an assumed name leads to wrong connections. Repeat the full name: "That's for Taro Yamada in Sales, right? One moment, please." This gives the caller confirmation and prevents any mix-up on the receiving end.

Pay attention to how you refer to your own colleagues when talking to outside callers. In Japanese business etiquette, you don't use honorific titles for your own coworkers when speaking to outside parties. "I'll connect you to Yamada" rather than "I'll connect you to Mr. Yamada" — referring to your own colleagues without titles when speaking externally is standard. This is one of the most common stumbling points for new employees, but the logic is clear: show respect to the outside party, speak humbly about your own side.

When the person is available, say something brief before making the connection: "Thank you for waiting. I'll connect you to Yamada now." Without that, the caller can't tell whether the line switched, whether they're on hold, or whether the call dropped.

Hold: How to Put Someone on Hold and Give Updates

Hold is less about the mechanics and more about the sequence. The right order: "Could you hold for just a moment?" (get agreement), then press hold, then check internally. Pressing hold without saying anything first makes the caller feel abandoned.

The biggest practical difference between good and average hold handling is the mid-hold update. Past about 30 seconds, caller frustration rises sharply. But even the same wait time feels shorter when you return briefly to say "I'm still confirming — just another moment, please." The best transfer handlers don't just make callers wait — they tell callers why they're waiting.

Having an internal directory or a way to check who's available helps reduce hold time. If the check is going to take longer, return to the line rather than leaving the hold running indefinitely. "I'm still working on this" or "I'll have an answer shortly" keeps the caller anchored.

Conveying Absences: Out, In a Meeting, On Leave

When someone is unavailable, delivering only the bare fact sounds cold. The reliable structure: apology, reason for absence, next step.

"I'm sorry, Yamada has stepped away from their desk."

Not "They're not here."

Absence reasons: "stepped away," "out of the office," "in a meeting," "on leave today" — brief and sufficient. There's no need to share where they went or what meeting they're in. The caller doesn't need the details; they need to know whether they can be connected now and what happens next.

If you know the return time, add it: "Yamada is currently out of the office and is expected back around 4pm." "Currently in a meeting — available after 2:30pm." This gives the caller something concrete to work with. Without it, "They're out" just leaves the caller hanging.

For absences due to leave: "I'm sorry, Yamada is out on leave today. If it's urgent, another team member can take the general details for you." This is more useful than "They're on leave" alone, which tells the caller nothing about what to do next.

Callback Offers and Making Commitments

When someone is unavailable, don't just take a message — arrange the next step. The standard offer: "Once they return, shall I have them give you a call back?"

If the caller says yes, confirm all the specifics before ending the call: callback number, the caller's name, the best time to reach them, and the level of urgency. "And the number is 03-xxxx-xxxx? That's for Ms. Suzuki, after 3pm is best, and it's not urgent — I have all of that." Skipping the repeat-back here is where wrong numbers, wrong names, and wrong times appear.

A callback commitment should have a specific time attached: "Yamada is expected back by 5pm, so expect a call by 5:30." "I'll be back by end of day — you should hear from me by 5" is more useful than "as soon as I'm back." The more specific the commitment, the more the caller trusts the follow-through.

If the person won't be able to return the call that day, say so clearly: "Yamada is away all day today — they'll reach you tomorrow morning." Or: "If this is urgent, I can take the general details and have someone else assist you." The quality of a transfer is defined by what happens after the connection fails.

OK / NG Comparison

What all the OK examples have in common: they give the caller enough to know what happens next. People who struggle with transfers usually have a clarity problem, not a politeness problem. Repeat the name, say something before hold, give absence with return time. These three things, consistently applied, make transfers reliable.

Ready-to-Use Phone Phrases | By Scenario

Standard phrases are easiest to use in the field when learned by scenario as complete units. For new employees especially, trying to assemble honorific language on the fly while also managing the content of the call leads to stumbles. A short reference on the desk — something you can read directly — does more for composure than trying to recall everything from memory. The goal isn't perfect elegance; it's being polite, complete, and brief every time.

Incoming Calls: Opening and Identification

Your first words tell the caller that this is a professional, ready organization. Fix your opening phrase in place — company, department, name, in that order — and deliver it consistently.

After your identification, a natural follow-up to invite the caller to introduce themselves:

When asking someone to repeat themselves, lead with apology or consideration, and target what you need confirmed:

Repeating back applies to names, company names, matters, and contact numbers — any of them. A single confirmation phrase reduces transfer and message errors significantly.

Closing phrases, ready for immediate use:

Absences, Callbacks, and Messages

When the person is unavailable, the reliable sequence is apology, absence reason, next offer. Rehearsing OK vs. NG makes the better phrasing automatic.

For callback offers, give the caller enough to make a decision:

Taking a message clearly:

Ready-to-use full phrases:

"I'm sorry, Yamada is currently out of the office. They're expected back around 4pm — shall I have them call you back then?"

"I'm sorry, they're in back-to-back meetings today. Would you like to leave a message?"

"Understood. I'll let Yamada know that Ms. Sato from [Company] called regarding the estimate."

When You Can't Hear Clearly

When the line is unclear, don't guess — guessing propagates errors through every subsequent step. A specific, polite request targets exactly what you need to confirm.

For poor signal or line quality:

For noisy surroundings:

For foreign names or unfamiliar names, getting the spelling in place:

For numbers and dates:

Confirming the Contact and Transferring

A smooth transfer starts with a brief confirmation of who the call is for, before you put the caller on hold. Directly saying "Who do you want?" sounds blunt — frame it with a little consideration:

Once confirmed, repeat back before checking availability:

A brief word before the transfer prevents the caller from wondering whether the call dropped:

If confirming takes longer than expected, return to update the caller:

"I'm still confirming their availability — just another moment, please."

"I've confirmed Yamada is available — connecting you now."

Outbound Calls: Opening and Closing

For outbound calls, having the conclusion ready before you dial is even more important than for incoming calls. The other person is receiving your call cold — if you start with context before stating the purpose, they spend the first minute not knowing where this is going.

Opening phrases, from first word to introducing the topic:

Checking timing before launching in:

Leading with the conclusion:

Closing with a clear next step:

If the person is unavailable:

"Understood. In that case, I'll try again on my end."

"I understand. Could you let me know what time works best for a callback?"

Minimum English Phrases

For English calls, fluency matters less than not losing the thread. If you can handle hold, transfer, and asking someone to repeat, you can manage most situations. A small set of reliable phrases works better than trying to improvise full English in real time.

For incoming calls:

For unclear calls:

For taking messages:

For outbound calls:

What matters most on an English business call is having the first phrase ready and keeping the content concise. Starting in English with your company name, your name, and a one-sentence purpose is enough to handle most situations professionally — even without advanced conversation fluency.