Priya Chandrasekaran had already made up her mind by the second attempt. The recruiter on the other end of the line was pleasant enough, well-prepared even, but she’d mangled Priya’s first name twice in the opening thirty seconds and then just moved on. No apology, no second try. Priya answered the rest of the call politely and never replied to the follow-up email.
Nobody wrote “lost candidate over her name” in the ATS notes afterward. It got filed under “went cold,” when the real story is that the first ninety seconds of that call told her exactly how much attention she was about to get for the rest of the process.
Why a Mispronounced Name Costs You More Than Awkwardness
A name is often the first piece of a candidate’s identity a recruiter handles, and getting it visibly wrong reads as something bigger than a slip of the tongue. It reads as “I didn’t prepare for this specific person.” Candidates notice. Sourcing teams talk about response rates and ghosting like they’re mysterious, unpredictable forces, but a lot of that early drop-off has a much more boring explanation: the outreach felt generic, and the name was the first proof of it.
This shows up hardest with names outside a recruiter’s own cultural background, which, given how global sourcing has become, is most names on most days. A recruiter working a req that spans three continents is going to hit unfamiliar syllables constantly. Treating that as a minor inconvenience rather than a fixable skill gap is where the drop-off starts.
The Two-Second Fix Most Recruiters Skip
Most training decks cover objection handling, Boolean sourcing strings, and offer negotiation. Almost none of them cover the ten seconds before a call actually starts. Before dialing a name you haven’t said out loud yet, run it through a phonetic spelling generator and jot the sound-it-out version next to the candidate’s name in your notes. It takes less time than refreshing their LinkedIn one more time, and it changes how the first line of the call lands — you sound like someone who did their homework, not someone reading off a resume for the first time.
It’s a small habit, and that’s exactly why it works. Nobody expects a stranger to nail an unfamiliar name on the first try. What candidates actually notice is whether you tried, and whether you recovered gracefully if you didn’t. “Did I say that right?” asked genuinely, in the first minute, does more for rapport than most opening scripts.
Building It Into Prep, Not Just the Apology
There’s a difference between apologizing after botching a name and preparing so you don’t have to. The first is fine, but it’s damage control. The second is a habit that compounds — over a hundred calls a quarter, it adds up to a meaningfully different candidate experience, and candidate experience is one of the few levers a recruiter fully controls in a process where offer timelines and comp bands usually aren’t up to them.
Teams that scale this well tend to build it into the same workflow where they’re already pulling contact details and background before a call. If you’re already looking someone up to confirm a current role or grab a direct number, adding thirty seconds for pronunciation costs almost nothing extra.
What This Signals About the Whole Process
Candidates read small signals as proxies for big ones. How a recruiter handles a name in minute one becomes, fairly or not, a stand-in for how the company will handle them as an employee later — will they be seen accurately, or will they be another line item processed on autopilot? That inference happens fast, and it’s mostly out of your control once the call starts.
What is in your control is the ninety seconds before you dial. It’s a cheap habit with an outsized effect on response rates, and unlike most of what shapes a candidate’s first impression, it doesn’t need a policy change, a new tool budget, or sign-off from anyone above you. It just needs to become part of how you prep.