How to Hire a Customer Service Rep Who Can Handle Real Complaints
You've had the interview. The candidate was warm, said all the right things about "loving to help people," and you liked them. Then they start the job, an actual furious customer calls, and they either freeze, over-apologize into a puddle, or get defensive right back. Now you're managing the fallout on top of everything else.
Customer service is one of those roles where the interview and the job barely resemble each other. A calm conversation with you, the hiring manager, tells you almost nothing about how someone behaves when a stranger is yelling at them about a refund. You have to build that moment into the process, because it won't show up on its own.
What the role actually requires
Strip away the job description language and a customer service hire needs four things:
- Patience under provocation — staying level when someone is rude, repeating themselves, or venting.
- Clarity in writing and speech — explaining a policy or a delay so it doesn't sound like an excuse.
- Judgment about when to bend the rules — knowing which complaints deserve a discount or exception and which don't.
- Stamina — doing this dozens of times a day without it visibly wearing them down by 3pm.
None of these are visible in a standard "tell me about yourself" interview. You have to go looking for them.
Give them an actual angry customer
The single most useful thing you can do is put a scripted complaint in front of them and watch what happens. Not a hypothetical — an actual message, read out loud or handed over on paper, and ask them to respond as if the candidate is speaking to a real customer right now.
Example script:
> "I've called three times about this order. Nobody has called me back. I paid for express shipping five days ago and it still hasn't arrived. I want a full refund AND the item sent overnight, for free. This is the worst service I've ever dealt with."
Ask the candidate to respond out loud, as if you're the customer. Then push back once — say something like "that's not good enough" — and watch what they do next. You're not scoring whether they solve the problem perfectly. You're watching:
- Do they get defensive, or do they stay with the customer's frustration for a second before responding?
- Do they promise something they can't actually deliver, just to end the tension?
- Do they explain why something happened, or just apologize on loop?
- Does their tone stay steady when you push back?
This takes four minutes and tells you more than twenty minutes of rapport-building small talk.
Ask about a time they said no
A good customer service hire isn't someone who gives customers everything they ask for. It's someone who can hold a boundary without sounding like a robot. Ask directly:
"Tell me about a time a customer asked for something you weren't allowed to give them. What did you say, exactly?"
Weak answers escalate to a manager immediately, or cave and give an unauthorized discount "just this once." Strong answers usually include a specific sentence they actually said — something like "I can't refund the shipping, but I can get this to you overnight at no charge" — because they're recalling a real moment, not inventing a philosophy on the spot.
Check how they write, not just how they talk
Most customer service now happens over chat and email, not phone. If the role involves any written support, give them a short written exercise: a real-sounding customer message, and ask them to reply as they would in the actual channel. Look for:
- Whether they open with acknowledgment or jump straight to policy.
- Whether the reply is scannable — short paragraphs, no wall of text.
- Whether they apologize once, meaningfully, instead of three times reflexively.
This is the closest thing to a work sample for this role, and it's the part interviewers skip most often because it feels less like "interviewing" and more like homework. Do it anyway — it's five minutes and it's the actual job.
Watch for the answer that's too smooth
Some candidates have done a lot of customer service interviews and have a polished answer for every scenario question. That's not disqualifying, but it means the scripted-complaint exercise above matters more, not less — a rehearsed answer to "tell me about a difficult customer" and an actual live reaction to a scripted complaint are different tests, and only one of them is hard to fake on the spot.
Reference checks worth doing
When you call a previous manager, skip "were they good with customers" — everyone says yes. Ask instead: "On a scale of calm to easily rattled, where did they sit when things got busy or someone was upset?" and "Did you ever have to pull them off a call or a chat because they were struggling with a customer?" The second question, in particular, tends to get an honest pause before the answer, and the pause tells you something.
Where a structured test helps
If you're hiring more than one or two customer service reps a year, building a consistent scripted-complaint exercise and scoring rubric by hand is worth doing once and reusing every time — it's the difference between comparing candidates on the same evidence and just comparing gut feelings. This is one of the few roles where a proctored situational-judgment test earns its keep, since it standardizes the "angry customer" scenario across every candidate instead of you improvising a slightly different one each time. Tools like AssessFit build this kind of scenario testing in alongside a percentile once enough candidates have gone through it, but a shared script and a simple 1–5 rubric on paper does most of the same job for free.
The honest limit here: no exercise fully replicates six months of real customers on a bad day. What you're buying with any of this is a reduction in surprise, not a guarantee. Someone can pass every scenario you throw at them and still burn out in month four. Build the 30-day check-in and the manager coaching around that assumption, not around the hope that the interview caught everything.
Test 5 candidates every month, free forever. No credit card.
Start free