You are the senior engineer on this account. You diagnosed the fault, you designed the fix, you know this client's system better than anyone alive. And two minutes into the call, Mr Whitmore clears his throat: 'No offence — but is there someone English I could deal with?' Every professional working in a second language meets this moment eventually. Here's how to own it.
The Scene 🎬
The question stings precisely because you've done everything right — and it mistakes the accent for the expertise.
Let's be honest about what's happening, because the lesson only works honestly. Sometimes "someone English" is prejudice in a blazer. But often — more often — it's something more ordinary: a stressed customer who half-missed two sentences, on a bad phone line, with money on the line, reaching for the version of confidence he grew up with. He doesn't actually need a native speaker. He needs to feel understood and safe — and those are things you can deliver in the next ninety seconds, because they were never about the accent.
The three traps, in order of temptation. Fold — handing the call to a native colleague who knows nothing about this client's system, which punishes the customer with worse service and teaches your company your expertise is optional. Fight — turning it into a confrontation about prejudice, which may be deserved but loses the account and, worse, your standing as the calm one. Or crumble — apologising for your English in a voice that suddenly does wobble, confirming exactly the doubt he voiced.
The fourth way: treat it as a communication complaint, not an identity verdict. Take the useful grain — maybe you were fast, maybe the jargon was thick — fix THAT visibly, and re-anchor the conversation to the thing he actually needs: the person who knows his file. Which is you. It was always you.
Where's the line between a customer struggling to understand and a customer who's decided not to? How can you tell from inside the call?
"They asked for a native speaker" — who loses most if that request is granted: you, the client, or the colleague who inherits a file they don't know?
YouSenior engineer, eleven years' experience, this client's system in your head — and an accent from Porto that has never once misdiagnosed a fault.
Mr WhitmoreThe client. Production line down, money burning, patience gone. Not a monster — a frightened man reaching for a familiar-sounding lifeline.
First: read the conversation and watch what You's voice does after the sting: it slows down and gets MORE authoritative, not less. Then find the sentence that turns the whole call — it's about the file, not the accent.
The Conversation 💬
The support line, 8:20am. Whitmore's production line has been down since six. You've just explained the diagnosis — quickly, because it's urgent.
Mr WhitmoreRight, stop — stop. Look, no offence, none at all — but is there someone English I could deal with? This is costing me four grand an hour and I can't be doing with… I just need to understand what's happening. Someone English. Please.
You*a beat — then slower, level* None taken, Mr Whitmore — and you're dealing with the right person. I'm the senior engineer on your account: I installed your line's control system in 2021, and I'm the one who diagnosed this fault twenty minutes ago. What I can hear is that I went too fast just now. That one's mine — let me fix it.
Mr WhitmoreI just — four grand an hour, and half of what you said was jargon soup. I need to KNOW what's happening. In plain words.
YouThen plain words, slowly, and stop me the moment anything's unclear. The short version: a sensor on your main line is sending false readings, so the system shuts itself down to be safe. The machine is healthy — it's the sensor lying to it. We swap the sensor, the line runs. Two hours once our engineer's on site.
Mr Whitmore…The sensor's lying to it. Right. See, THAT I understood. Why didn't you say that the first time?
YouBecause at 8am with your line down, I made the classic engineer's mistake — I gave you the technical version at technical speed. If I'd been unclear in any language, that would still have been the wrong call. The accent's from Porto, Mr Whitmore, but the rushing was pure engineer.
Mr Whitmore*a grudging almost-laugh* …Fair enough. But look — for something this expensive, wouldn't it be simpler if I dealt with someone… you know. Where nothing gets lost in translation. Simpler for both of us.
YouLet me tell you what "simpler" actually looks like, and then you choose — genuinely, your call. I can transfer you to my colleague Dave. Lovely accent, Kent, very clear. Dave has never seen your system. He'd start from the file — MY file — reading MY notes, ringing me every ten minutes with your line still down. Or you keep the person who knows which sensor, which cabinet, which bolt — and I promise you plain words at human speed for as long as this takes. You need the person who knows your file, Mr Whitmore — not just a different accent.
Mr Whitmore*a long pause* …Which cabinet IS it?
YouCabinet four, second row, the sensor with the orange tag — your maintenance lad Karl replaced its neighbour in March, he'll know exactly where. And here's what happens next, step by step: our engineer Tomás is leaving now, on site by ten. He swaps the sensor. I stay on this line with you until your line restarts — you'll hear it from me, not from a status page.
Mr WhitmoreKarl. The orange tag. You DO know the file. …Look, about the "someone English" thing—
YouYou had a line down and a stranger's voice talking fast — I've heard far worse before breakfast, and from people whose lines were running. It's forgotten. What I'd ask instead is this: judge me on the next two hours. If anything I say is unclear — anything — say "again, slower", and you'll get it again, slower, without a sigh. Ask me anything technical, any depth. That's where you'll hear what my English is actually for.
Mr WhitmoreAgain-slower. Right. …One question then, straight answer: when the line restarts, how do I know the fault won't just come back? Don't simplify it — I ran machines for thirty years before I ran this place. Give me the real version.
YouThe real version, then: the replacement sensor has a different failure mode — it fails loud, not quiet. If it ever goes, your panel screams instead of whispering wrong numbers, and the line stops in a safe state instead of running blind. Plus I'm setting your system to send me its readings for a fortnight — if anything drifts, I call you before your line even notices. Thirty years of machines, you'll appreciate this: we're not just fixing the fault, we're fixing how it fails.
Mr WhitmoreFails loud, not quiet. *pause* That's the best sentence anyone's said to me all morning. Right — Tomás, ten o'clock, cabinet four. And… you'll stay on the line. You, specifically. I'm asking for you specifically now, you understand. That's — well. That's the apology, engineer. Take it.
YouTaken, Mr Whitmore. Now let's get your four grand an hour back — Karl should head to cabinet four, and I'll walk him to the orange tag myself.
From memory — don't scroll back up.
What does You take from the complaint, and what does You refuse to take? Find the exact split.
How is the "Dave option" made real — and what does it reveal about what the client actually needs?
What proves the expertise in the end — list the three file-details and the technical answer that close the argument.
1. Taken: the communication grain — "I went too fast just now. That one's mine — let me fix it." Refused: the identity verdict — the accent is never apologised for, the transfer is never folded into, and the voice gets slower and MORE authoritative, not less. "The accent's from Porto, but the rushing was pure engineer."
2. Dave is described honestly: lovely Kent accent, never seen the system, would work from YOUR file, ringing you every ten minutes with the line still down. Framed as a genuine choice — "your call" — it exposes the real need: not vowels, but the person who knows which sensor, which cabinet, which bolt.
3. Cabinet four, second row, the orange tag; Karl the maintenance lad who replaced its neighbour in March; Tomás on site by ten. And the closer: the fails-loud-not-quiet answer, delivered at full technical depth on request — "that's where you'll hear what my English is actually for."
Useful Phrases 🧰
Ten phrases for the moment your English is questioned instead of your work — clients, patients, customers, in-laws. Say each out loud BEFORE you reveal it.
Say it like you mean it. One physical rule governs everything: when the sting lands, SLOW DOWN. The panicked instinct is to speed up and prove fluency; speed is what created the doubt. Slow, level, and precise is what authority sounds like in every language — and it's the one register no one ever asks to be transferred away from.
🛡️ Absorbing the sting
Phrase 1
The job: the first response — the one that decides everything. Which version?
A. "Oh — I'm sorry, yes, my English — let me find my colleague, one moment—"
B. "None taken — and you're dealing with the right person. I'm the senior engineer on your account."
C. "That's actually quite offensive. My English is certified C2, for your information."
B — "None taken — and you're dealing with the right person." A folds — and hands a down-line customer to someone who's never seen his system, confirming the doubt AND worsening his service. C wins a point and loses the room; certificates convince nobody at 8am with a line down. B does the three essential things in one breath: absorbs the sting without absorbing the verdict ("none taken"), states the fact that reframes everything ("the right person"), and attaches the credentials that matter — not language credentials, ACCOUNT credentials: installed it in 2021, diagnosed it twenty minutes ago.
Take it anywhere: "You're dealing with the right person — I'm the ___ on your ___." The calm re-anchoring, for every questioned expert.
Phrase 2
The job: taking the true grain — and only the grain. Complete it:
"What I can hear is that I went too ___ just now. That one's ___ — let me fix it."
"I went too fast just now. That one's mine — let me fix it." Inside most "someone English" complaints hides one legitimate grain: you were fast, the jargon was thick, the line was bad. Finding it and owning it — precisely, like Dana owned the phone — does two things: it gives the customer's frustration somewhere real to land, and it converts the complaint from who-you-are (unfixable, and not broken) to what-just-happened (fixable in the next sentence). You'll notice what You does NOT own: the accent. The accent was never the problem.
Take it anywhere: "What I can hear is ___ — that one's mine." Extract the true grain from every stinging complaint; leave the rest.
Phrase 3
The job: the plain version, with a standing invitation. Complete it:
"Plain words, slowly — and ___ me the moment anything's unclear."
"Plain words, slowly — and stop me the moment anything's unclear." Then deliver: "a sensor is sending false readings, so the system shuts down to be safe. The machine is healthy — the sensor is lying to it." Notice what that sentence is: world-class technical communication — metaphor, structure, no jargon — the thing native speakers routinely fail at. "Stop me the moment" converts understanding from a test he might fail into a service you're providing. His reaction is the proof: "THAT I understood."
Take it anywhere: "Plain words, slowly — stop me when anything's unclear." The offer that outperforms any accent.
Phrase 4
The job: separating the accent from the error — with a smile in it. Complete it:
"The accent's from Porto — but the ___ was pure engineer."
"The accent's from Porto, but the rushing was pure engineer." The line that names the elephant and puts it to work: yes, there's an accent; no, it wasn't the problem — engineers of every nationality rush technical explanations at stressed clients. It's said with enough lightness to invite the almost-laugh, and it quietly educates: the thing you struggled with, Mr Whitmore, is a profession-wide disease, not a Porto one. Own your origin without apologising for it; blame the actual culprit.
Take it anywhere: "The accent's from ___, but the ___ was pure ___." Claim the origin, indict the real error.
⚖️ The choice, made real
Phrase 5
The job: the transfer option, described honestly. Put the pieces in order:
He'd start from MY file, reading MY notes,Dave has never seen your system.with your line still down.ringing me every ten minutes
"Dave has never seen your system. He'd start from my file, reading my notes, ringing me every ten minutes — with your line still down." Don't refuse the transfer — DESCRIBE it, accurately, and let the description do the refusing. Dave is real, his Kent vowels are lovely, and routing a live fault through a stranger reading your notes is objectively worse service; the customer just hasn't thought it through, because he's thinking about comfort, not logistics. Walk him through the logistics and finish with "your call — genuinely." Choices freely made stick; refusals get resented.
Take it anywhere: "Here's what that would actually look like — then it's your call." Make the alternative concrete and let reality argue for you.
Phrase 6
The job: the sentence the whole lesson exists for. Complete it:
"You need the person who knows your ___ — not just a different ___."
"You need the person who knows your file — not just a different accent." The re-anchoring, compressed to one line: what the situation requires versus what the discomfort is asking for. File beats vowels — at 8am, at four grand an hour, every single time, and deep down the customer knows it; the sentence just puts the knowledge where he can see it. Note the pause that follows, and what comes out of it: "…which cabinet IS it?" — the sound of a man quietly re-hiring you.
Take it anywhere: "You need the person who knows the ___ — not just a different ___." File over accent, case over passport — the expertise-versus-comfort reframe.
Phrase 7
The job: proof by file — the details no stranger could have. Complete it:
"Cabinet four, second row, the sensor with the ___ tag — your maintenance lad ___ will know exactly where."
"Cabinet four, the orange tag — Karl will know exactly where." Claims of expertise are audible; DEMONSTRATED expertise is undeniable. The cabinet, the row, the tag colour, the name of his own maintenance man and what Karl did in March — four details in one breath, none of which Dave-from-Kent could produce, all of which say: your operation lives in my head. "You DO know the file" is the argument ending, out loud. When your competence is doubted, don't describe it — display a piece of it, immediately, concretely.
Take it anywhere: lead with the detail only the real expert holds. The file IS the argument.
🤝 Closing it — and setting the terms
Phrase 8
The job: receiving the half-apology without milking or dodging it. Complete it:
"I've heard far worse before ___ — it's forgotten. What I'd ask instead is: judge me on the next two ___."
"I've heard far worse before breakfast — it's forgotten. Judge me on the next two hours." When "about the someone-English thing…" arrives, two traps open: extracting a full grovel (satisfying for ten seconds, resented for years) or waving it away so completely the lesson evaporates. This threads them: generous ("forgotten"), honest about the scale ("far worse, from people whose lines were running" — a quiet education in what you absorb weekly), and then the pivot to the only tribunal that matters: the next two hours of work. Let the work collect the apology.
Take it anywhere: "It's forgotten — judge me on the next ___." Grace plus a performance window: the professional's response to every retracted insult.
Phrase 9
The job: installing the mechanism that prevents the next one. Complete it:
"If anything I say is unclear — anything — say '___, ___', and you'll get it again, slower, without a sigh."
"Say 'again, slower' — and you'll get it again, slower, without a sigh." The standing arrangement that fixes the root cause: customers escalate to "someone English" when they've half-missed things repeatedly and feel embarrassed asking again — the request for a native speaker is often a request for permission to not understand. Grant the permission directly: a two-word protocol, no shame attached, "without a sigh" guaranteed. Whitmore uses it as a noun within a minute — "again-slower, right" — which is the sound of the mechanism installing.
Take it anywhere: "Say 'again, slower' — no sigh, ever." Install it with every client, patient, and in-law; it retires the transfer request permanently.
Phrase 10
The job: the depth invitation — where your English stops defending and starts winning. Say it out loud, then write it.
e.g. "Ask me anything technical, any depth — that's where you'll hear what my English is actually for." The endgame reversal: instead of your English being the thing on trial, invite the hardest questions and let precision testify. The fails-loud-not-quiet answer is the exhibit — full technical depth, delivered in language a thirty-year machine man calls "the best sentence anyone's said to me all morning." Your English was never for small talk. It's for exactly this: carrying deep expertise across to the person who needs it. Invite the depth. Depth is your home ground.
Take it anywhere: "Ask me anything, any depth — that's what my English is for." The invitation that turns the trial into a demonstration.
🔑 Make them yours
These ten are for every professional whose accent arrives before their credentials. Say each answer out loud before you type it.
"You're dealing with the right person — I'm the ___ on your ___." — build your own re-anchoring sentence, credentials attached.
"The accent's from ___, but the ___ was pure ___." — build yours, with the smile in it.
"That's where you'll hear what my English is actually for." — what's YOUR home ground — the depth where your English outperforms any native small-talker?
Quick test: the ninety seconds, out loud, SLOWER than feels natural — none taken, right person → too fast, that one's mine → plain words, stop me → Porto accent, engineer's rushing → what Dave actually looks like → the file, not the accent → cabinet four, orange tag, Karl → forgotten, judge me on two hours → again-slower, no sigh → any depth, that's what it's for. Ten sentences; one account kept, one client educated, zero dignity spent.
Your Turn 🎭
Now the line is down, the clock is running, and the question is coming. Two rounds — the expert, then the frightened client.
Round 1 — you are the expert 🔧
Your account, your diagnosis, your accent. Mr Whitmore speaks — you slow down and take charge. No looking back at the phrases.
Mr WhitmoreStop — stop. No offence, none at all — but is there someone English I could deal with? This is costing me four grand an hour and I just need to UNDERSTAND what's happening.
Mr WhitmoreHalf of what you said was jargon soup. Plain words. What is actually wrong with my line?
Mr Whitmore…THAT I understood. Why didn't you say it like that the first time?
Mr WhitmoreFair enough. But for something this expensive — wouldn't it be simpler with someone where nothing gets lost in translation? Simpler for both of us, surely.
Mr Whitmore*a long pause* …Which cabinet is it, then?
Mr WhitmoreYou DO know it. Look — about the "someone English" thing… And one real question: how do I know this fault won't just come back? Don't simplify. I ran machines for thirty years.
Round 2 — now YOU are Mr Whitmore 📉
Swap chairs. Your line is down, four grand an hour, and a voice you're straining to follow is talking fast about sensors. Feel where the "someone English" impulse actually comes from — and what dissolves it.
Engineer*rapid* —so the anomalous telemetry from the inductive proximity sensor is triggering the failsafe cascade, which is why you're seeing the shutdown loop on the PLC—
EngineerNone taken — and you're dealing with the right person. I installed this system in 2021 and diagnosed the fault twenty minutes ago. What I can hear is I went too fast — that one's mine. Plain words, slowly: a sensor is lying to your machine. The machine is healthy. We swap the sensor, you run.
EngineerI can transfer you to Dave — lovely Kent accent, never seen your system, working from my notes with your line still down. Or you keep the person who knows which cabinet and which bolt. Genuinely your call.
EngineerCabinet four, orange tag — your man Karl replaced its neighbour in March. And say "again, slower" any time — you'll get it again, slower, without a sigh. Ever.
⚡ The twist
The line restarts at 11:40. At 2pm your manager forwards you an email, cc'd to half the company. It's from Whitmore — glowing: "…resolved brilliantly. And a suggestion: your engineer handled my frankly rude request for 'someone English' with more grace than I deserved. You should train your whole support team on whatever that was."
Your manager adds one line: "Well? Want to run a session for the team on it? Half our engineers get this weekly and most of them just transfer the call."
Design the five-minute version: what do you tell a room of second-language engineers about that moment — the traps, the method, and the one sentence they should have ready? Teach it — you're the expert on this now too.
Before you close the tab…
Does the sting make you slower and steadier — never faster?
Can you take the true grain and refuse the identity verdict?
Is your re-anchoring sentence ready — credentials from the file, not the language?
Can you describe the transfer honestly and let logistics do the refusing?
Do you invite depth — the ground where your English wins?
The Echo 🕰️
In 1744, a fourteen-year-old German girl arrived in Russia with a trunk, a minor title, and no Russian at all. The court she entered never let her forget any of it: the accent, the foreignness, the whispers that a Prussian princess could never truly understand Russia. Sophie of Anhalt-Zerbst heard, in the silks of St Petersburg, every variation of "is there someone Russian we could deal with?"
Her answer took years and became legend. She learned Russian ferociously — studying by night, by an open window in winter, a habit that nearly killed her and won the court's first grudging respect. But here's the part that matters for the support line: she never lost the accent, and she stopped apologising for it. Instead she out-knew everyone — the law, the army, the church, the grain reports, the FILE of Russia — until the German girl with the accent was simply the person who understood the empire best. They stopped asking for someone Russian. They started asking for Catherine. History added "the Great".
You don't need an empire — just her sequence, which is exactly this lesson's: absorb the sting without absorbing the verdict, fix what's genuinely yours to fix, and then know the file so thoroughly that the accent becomes what it always was — the sound of the most competent person in the room, arriving from somewhere else.
Catherine kept the accent and conquered anyway. Does an accent ever stop mattering — or does the world just eventually stop being able to afford the objection?
"They started asking for Catherine." What would it take, in your field, for people to ask for you specifically — accent included?