Answering the Phone in a Language Your Staff Don't Speak

A woman calls your shop at 11:40 on a Saturday. She starts in Cantonese. Whoever picked up says "sorry, English?" There's a pause, two or three seconds of someone deciding whether to try, and then the line goes dead. Nobody writes that down. It never shows up as a lost sale. It just shows up later as a slow month you can't explain.

In the GTA this happens more than owners think. Scarborough, Markham, Richmond Hill, Brampton, Mississauga, parts of North York and the west end — plenty of people run their daily lives in Cantonese, Mandarin, Punjabi, Tamil, Tagalog, Farsi, Portuguese, Italian, Korean, Spanish, or Urdu. Most of them speak English fine. That's not the point. The point is which language they'd rather order a $90 catering tray in, or explain a brake noise in, or book their mother's appointment in. Given a choice between a tense call and the other restaurant down the street, some of them pick the other restaurant.

First find out if you actually have this problem

Don't guess from the neighbourhood. Guess from your own phone.

Pull your call log for the last two weeks. You're looking for calls under about fifteen seconds that weren't wrong numbers. A fifteen-second call is almost never a completed order. It's a hello, a misfire, and a hang-up. If you've got a handful of those a week, open a couple of them up by calling back — in a quiet moment, not the rush — and just ask what they were looking for.

Then ask your staff. Not "do we get calls in other languages," which gets you a shrug, but "when was the last time someone called and you couldn't understand each other?" People remember those calls because they feel bad about them. You'll usually get a specific answer and usually one specific language.

That's the whole audit. One language, or two at most, will account for nearly all of it. You are not solving multilingual service. You are solving Cantonese on weekends, or Punjabi on weekday mornings. That's a much smaller problem.

Option one: a bilingual person on shift

The obvious fix, and the best one when it works. Someone on the floor speaks the language, and the phone gets handed to them.

What it costs is not usually money — you're probably already paying someone who speaks a second language and never thought to use it. What it costs is scheduling and attention. If only one person on your team speaks Mandarin, you now have a phone problem shaped like a shift problem: it's covered Tuesday through Saturday and uncovered on Sunday. And when that person is the one who speaks the language and the one running the line, every one of those calls pulls them off their actual job. If you're already thinking about how shifts line up against your busy hours, that's the same decision you're making in your staff schedule.

The other cost is fragility. One person. When they quit, your second language quits with them. If you go this route, make it deliberate: put it in the schedule on purpose, tell the rest of the team "pass it to Mei, don't apologize and hang up," and know that you're one resignation away from square one.

Option two: a recorded greeting in two languages

Cheap, fast, and only half a solution. "Press 2 for Mandarin" costs you one recording session and maybe an hour of setup.

The trap: the caller presses 2 and then lands on a human who doesn't speak Mandarin. You've now made it worse. You promised service in their language, raised their expectation, and then handed them the same dead end with an extra thirty seconds of menu in front of it. That's more insulting than the honest "sorry, English?"

A recorded menu is worth doing in exactly one case: when the thing behind the button is also in that language and doesn't need a conversation. Hours. Address. A recorded note that online ordering is available in Chinese on your site. Information you can read out, that doesn't require the caller to answer a question. The moment the caller needs to say something back, a recording can't help.

Option three: send them somewhere that isn't the phone

An ordering page or booking page in a second language solves more than people expect. Reading a menu in your own language is comfortable and requires nobody to be good at anything in the moment. No accent to parse, no rush noise, no waiting.

This is cheaper than it sounds for a short page — a menu, a booking form, a service list — and it's permanent. It doesn't call in sick. The real cost is maintenance: every price change, every new item, now has two places to live. If your menu moves a lot, agree up front on who updates the second version and when, or the translated page quietly rots and starts quoting last year's prices.

It also won't catch the older caller who was never going to use a website. For that person, the phone is the only door.

Option four: an AI phone agent that answers in both

This is the newer option and it deserves an honest description rather than a pitch. A phone agent picks up every call, including the ones at 11:40 on a Saturday, and can carry a whole conversation in a second language — take the order, take the booking, read back the address, text a confirmation.

Where it genuinely wins: coverage. It's bilingual at 2pm and at 9pm and on the day your Mandarin-speaking server is on vacation. It never gets flustered in a rush. And it doesn't pull anyone off the floor, which is the same reason it's worth considering for the dinner rush in general.

Where it's awkward, and you should plan for it: regional differences are real, and a caller speaking a dialect or a heavy regional accent can confuse it the same way it might confuse a person from a different region. Names and street names are the hard part in any language. And some callers simply don't want to talk to a machine — so the handoff rule matters more than the technology. Decide now what happens when the agent can't follow: it should offer to ring the shop, or take a name and number for a callback, not loop the caller through the same question three times.

Cost is a monthly fee rather than a wage, which is why it tends to make sense for the business where the second language is a steady trickle rather than a flood — not enough calls to justify hiring for it, too many to keep losing. If you want to see how this fits alongside ordering and booking, our services page lays out what we actually build.

What to do this week

Pick the language. One. The one your staff mentioned.

Write down the five things those callers call about. For a restaurant it's usually: are you open, do you deliver here, what's in this dish, I want to order, where's my order. For a clinic or a shop it's: are you open, do you take walk-ins, how much, can I book, where are you.

Now decide, for each of those five, what the caller should get — a person, a recording, a web page, or an agent. You'll find the first two or three are fine as recorded information and the last two are the ones that need a real back-and-forth. That tells you how much machinery you actually need, which is usually less than you feared.

Last thing: make sure nothing in this chain ends in voicemail. A caller who already feels uncertain about the language will not leave a message. That's the quietest version of the problem we've written about before — voicemail is where your sales go to die — and it's twice as true when the caller is already half-expecting the call not to go well.