Handling Calls in Another Language at the Front Desk

Why this matters

A caller who does not speak English usually gets one of three things at a small shop: a confused "sorry?", a hold that ends when they give up, or a voicemail nobody can understand and nobody returns. Each one is a booked job lost, and many of these callers are exactly the customers who stay loyal to the one shop that answered them properly. A front desk does not need to be multilingual to handle these calls. It needs a route for each language it hears, a script for the first twenty seconds, callback promises it keeps, and a record of what language each customer wants.

The customer conversation itself, once you have a shared language or an interpreter, is covered elsewhere (see related: Customer Communication with Non-English Speakers). This is the front-desk plumbing that gets you there.

Step 1: Count the calls for one month

Before building anything, have everyone who answers the phone log every call in a language other than English: date, time, language (or "unknown"), and what happened (handled, transferred, voicemail, lost). Unknown languages get logged too.

Why first: you will design routing around the languages you hear and the hours you hear them. Most shops guess wrong in both directions: overestimating one language and missing a smaller second one entirely. What breaks if skipped: you add a Spanish menu option and nobody notices the Vietnamese-speaking callers hanging up every week.

Step 2: Decide a route for each language

From the count, sort languages into three routes:

• In-house: a language someone on staff speaks well enough for booking and basic questions, during the hours they work.
• Interpreter line: every other language, plus your in-house languages outside that person's hours or when they are busy. A phone interpreter service connects an interpreter into the call within a minute or two in most common languages (see related: Using a Phone Interpreter Service).
• Scheduled callback: when neither is available right now, a specific callback time, kept.

Why: every call should have a defined path before it rings. What breaks if skipped: each call depends on who picked up, and the bilingual coordinator becomes the only route, including on her day off.

Step 3: Add a phone-menu option only for a language you can staff

A menu option ("Para espanol, oprima dos") is worth adding for a language that is a meaningful share of your calls, and only if pressing it reaches a person who speaks it during business hours, or a voicemail in that language that is returned on a stated schedule. Record the after-hours message in that language too, and make sure it carries the emergency instruction: if you smell gas, leave the house now, do not touch switches or use the phone inside, and call the gas utility or 911 from outside. Have the recording checked by a second fluent speaker, the same way a translated document is checked.

Why: a menu option is a promise. What breaks if skipped: callers press 2, reach a voicemail box nobody checks, and conclude correctly that the option was decoration. A gas emergency caller who reaches an English-only after-hours message may not understand the one instruction that matters.

Step 4: Give every phone person a twenty-second script

Everyone who answers the phone, including the owner and whoever covers lunch, needs the same short routine for a call they cannot understand: stay calm, identify the language, ask the caller to hold, and connect the right route. A laminated card by each phone with the shop's interpreter-line number, account code and the names of common languages written phonetically is enough. Here is how it sounds with an English-only representative and a Vietnamese-speaking caller:

OFFICE: Thanks for calling, this is Kim.
CALLER: (in Vietnamese) ... water heater ...
OFFICE: One moment. Vietnamese? Vietnamese?
CALLER: Yes. Vietnamese.
OFFICE: Okay. Please hold. Interpreter. Hold, okay?
        [dials interpreter line, account code,
         asks for Vietnamese, joins caller in]
INTERP: Interpreter 4471, Vietnamese.
OFFICE: Thank you. You are with a plumbing company.
        Please ask her name, address and the problem.
INTERP: (relays) Her name is Lan Tran. The water
        heater is leaking on the floor.
OFFICE: Ask her: is the water near anything
        electric, and can she turn off the water
        at the heater?

Kim speaks to the caller through the interpreter in the first person, in short sentences, and asks about water near electrical equipment before scheduling anything. If the answer is yes, the instruction relayed is to stay out of the water and away from the heater and any outlet or cord near it, and to wait for the tech rather than reach for a valve standing in it. Speaking through an interpreter so nothing is lost has its own card (see related: Speaking Through an Interpreter So Nothing Gets Lost).

Why scripted: the first twenty seconds decide whether the caller stays on the line. What breaks if skipped: an untrained person says "no Spanish, sorry" and hangs up, or shouts English more slowly, which helps no one.

Step 5: Make callback promises specific, and keep them

When a call cannot be handled now, promise a specific window, write it as a task assigned to a named person, and keep it. A sound default: during business hours, a callback within 2 business hours; for after-hours voicemail, by 10 a.m. the next business day. Tune it to your staffing, but commit to a number and say it to the caller, in their language if the menu message carries it.

Why: a vague "someone will call you" is heard, correctly, as "no one will call you." What breaks if skipped: callbacks to non-English voicemails are the first thing dropped on a busy day, because they are the hardest ones to make, and the customer books with whoever called back first.

Step 6: Record the language preference and follow it through

Add a preferred-language field to the customer record, filled on the first call, with two parts if they differ: the language they speak and the language they read. Then use it: dispatch notes the language so a bilingual tech can be sent where possible; appointment reminders and texts go out in that language, checked rather than machine-translated blind (see related: Machine Translation on the Job: Where It Breaks); and the office knows before the next call who to route it to.

If a sale is negotiated in that language, the paperwork may have to follow it too, depending on your state and the contract type (see related: Contracts in the Language the Deal Was Made In).

What breaks if skipped: every call starts from zero, the customer explains again, and the tech arrives without anyone on the crew who can talk to them.

Step 7: Review the log monthly

Keep the language log running after the first month. Once a month, look at three numbers per language: calls received, calls handled live, and callbacks made inside the promised window. When a language crosses a meaningful share of calls, consider a menu option or a bilingual hire (see related: Hiring Bilingual Office Staff: What to Test). When callbacks slip, find out who owns them.

Worked example: a shop that was losing a tenth of its Spanish calls

A plumbing and drain shop takes about 600 inbound calls a month. One bilingual coordinator, Elena, works 8 to 5 on weekdays.

Step 1, the count. The first month's log shows 60 calls in other languages: 54 in Spanish, 3 in Vietnamese, 2 in Portuguese and 1 the representative could not identify. Of the 54 Spanish calls, 41 came in while Elena was working and 13 came in before 8, after 5 or on Saturday. All 41 were handled. Of the 13, 7 left voicemails that were returned the next day or later, and 6 hung up without leaving one. All 6 of the other-language calls were lost: the representatives could not tell what the callers needed.

So the shop lost 6 of its 54 Spanish calls (about 11 percent, roughly a tenth) and all 6 of its other-language calls, 12 of 60 non-English calls in all, and most of the returned Spanish voicemails reached customers a day or more after they called.

Steps 2 to 6, the changes. Spanish becomes the in-house route during Elena's hours and the interpreter line outside them, during open hours. The menu gets a Spanish option with a Spanish after-hours message carrying the gas emergency instruction and the next-morning callback promise. Every phone person gets the card, and Kim, who covers Saturdays, practices the script twice on a test call to the interpreter line. Callbacks are logged as tasks with a 2-business-hour window. The customer record gets a preferred-language field.

Step 7, the next month. The log shows 63 non-English calls: 56 Spanish, 4 Vietnamese, 2 Portuguese, 1 Russian. Of the 56 Spanish calls, 42 were handled by Elena, 8 through the interpreter line on Saturday or when Elena was on another call, and 6 went to the Spanish voicemail after hours; all 6 were returned by 10 a.m. the next business day. All 7 other-language calls went through the interpreter line. Callbacks inside the promised window: 6 of 6. Lost non-English calls: 0 of 63.

What it changed, in like-for-like terms. The first month lost 12 of 60 non-English calls; the second lost none of 63. The shop cannot attribute every booking to the change, but the lost calls were the measurable part, and they went to zero within a month.

What changes the answer. If a single language is a large share of your calls, as Spanish is for some shops in border and big-city markets, a second bilingual hire may serve customers better than an interpreter line does for anything beyond booking, because the interpreter cannot answer questions about your services. If you hear a language only once or twice a year, a menu option is wasted; the interpreter line and a card by the phone are the whole system.

How to verify you got this right

Call your own shop from an outside phone after hours and press the menu option for each language. Then, during business hours, have someone call in speaking a language nobody on staff speaks, by arrangement and with the interpreter-line charge expected, and watch what your newest phone person does in the first twenty seconds.

References

• See related: Using a Phone Interpreter Service
• See related: Speaking Through an Interpreter So Nothing Gets Lost
• See related: Customer Communication with Non-English Speakers Reference
• See related: Hiring Bilingual Office Staff: What to Test
• See related: Serving Customers in a Language Nobody on Staff Speaks