Customer service representative interview questions
Hire the customer service representative who listens before typing, gets the address and the problem right, stays calm with upset callers and books the job without pushing. These questions, two role-play calls and the reference checks test each of those, so you aren't hiring on a pleasant phone manner alone.
What this hire must get done
Write the scorecard before you interview, then hire against it. Set the bracketed targets from your own numbers.
MissionTurn the calls your company pays for into correctly booked jobs, and leave every caller, upset ones included, glad they called.
- Books calls alone in [your scheduling software] within [two weeks], using your scripts for fees and safety calls.
- Books [your target] of service calls by month [three], without discounts outside [your price rules].
- Fewer than [your target] bookings a month need a callback to fix a wrong address, phone number or job type.
- Answers [your target] of calls live during [your phone hours], and returns voicemails and web requests within [your response standard].
- Gives every upset caller a plan and a callback time on the first call, and closes complaints within [time frame].
What to tell candidates before the interview
Say the hard parts plainly. People who wouldn't stay drop out early, and the ones who stay knew what they signed up for.
- Say plainly that the phone is the job: most of the shift on a headset, back-to-back calls in [your busy season], and some callers who are upset before you say hello.
- Tell them you measure booked calls, not just answered ones, and how [any booking bonus or plan sales] work, so people who want a pure service desk can say so now.
- Name the hours: [your office hours], plus [evening, weekend or storm coverage, if any], and how much notice they get when shifts run long.
- Tell them how you'll review their work, such as [listening to calls or checking bookings] each week, so feedback doesn't come as a surprise.
How to run the interview
- Same questions, same order. Ask every candidate the questions below and the same follow-ups. It is the only way to compare people fairly.
- Two interviewers. An owner or manager and someone who does the work. Take notes on what the candidate says, not on how you feel about them.
- Score right after each answer. 5 sounds like the strong answer, 3 like the mixed one, 1 like the weak one. Use 2 and 4 for answers in between.
- Rate alone, then compare. Compare candidates question by question, and talk only after everyone has scored. Big gaps are worth a conversation.
Customer service representative interview questions
10 questions, each tied to the scorecard, with follow-ups and what a 5, 3 and 1 answer sound like.
A caller rattles off an address and phone number fast on a bad cell connection. Walk me through how you make sure both are right before you hang up.
Many booking errors start with a misheard street or a swapped digit, and the technician pays for it at the curb.
Follow-ups
- How do you spell a street name back so the caller catches a mistake?
- What do you do when the software suggests an address that's close but not the same?
- What do you do if the caller is in a hurry and won't stay for a read-back?
- 5Strong
- Slows the caller down, spells the street back with words like "B as in boy", repeats numbers in small groups, checks the address against the map or software, asks for a unit, gate code or landmark, and reads the whole booking back at the end.
- 3Mixed
- Repeats the address and number back once, but doesn't spell anything or check the map, so a near miss like Maple Court for Maple Drive still gets through.
- 1Weak
- Types what they heard and moves on, or trusts caller ID for the callback number.
Tell me about a time a caller described one problem, but asking a few more questions showed they needed something else.
Callers name a symptom, not a fix. The CSR who asks the next question books the right job, the right person and the right amount of time.
Follow-ups
- What did the caller say first, as close to word for word as you can?
- Which question changed the picture?
- What did you write in the notes for the person who went out?
- 5Strong
- Gives a specific call, the question that uncovered the real need, how it changed the booking (job type, time slot or who went), and what the notes said. Knows how the visit went.
- 3Mixed
- Has a real example, but the caller volunteered the real problem. The candidate wrote it down well but didn't draw it out.
- 1Weak
- Books whatever the caller asks for and sees extra questions as slowing the call down.
A caller asks what you charge just to come out. Before you can answer, they say another company quoted less. Walk me through the rest of the call.
Price shoppers book when they hear what they get and a clear next step. A dodge or a hard push sends them to the next number on their list.
Follow-ups
- What do you say about the other company's price?
- How do you ask for the booking, in your own words?
- What do you do if they still say no?
- 5Strong
- Asks about the problem first, then gives your set fee plainly and what it buys, never knocks the other company, offers two specific times, and if they decline, thanks them and offers to text the details.
- 3Mixed
- Gives the fee honestly and politely but stops there. Never asks for the booking, so the caller says they'll think about it.
- 1Weak
- Dodges the price, offers a discount they can't approve, or talks down the other company.
Tell me about a caller you didn't book, or a customer you lost on the phone, that you still think about. What would you say differently now?
A CSR who studies lost calls gets better every month. One who blames the caller stays where they are.
Follow-ups
- At what moment did the call turn?
- How do you know why they didn't book?
- What do you do now on calls like that?
- 5Strong
- Names a specific call and the moment it slipped, owns their part without blaming the caller or the price, and describes a change they made and how it has worked since.
- 3Mixed
- Remembers a lost call and has a fair guess why, but the fix is general, like "be friendlier".
- 1Weak
- Says every caller they lose was only shopping on price, or can't think of one.
A customer calls the day after a repair. The same problem is back, they took another day off work, and they want someone out this afternoon. The schedule is full. What do you do?
Repeat problems are when customers decide whether to give you another chance. The CSR has to calm them without promising a slot that doesn't exist.
Follow-ups
- What do you say first?
- Who do you bring in, and what do you tell them?
- What do you promise the customer, and what don't you promise?
- 5Strong
- Apologizes, gets what's happening now and checks it isn't a safety issue, flags it as a callback under your policy, asks dispatch or the manager for the first real opening, gives the customer a specific time and who's coming, and calls back if anything changes.
- 3Mixed
- Stays kind and flags it as a return visit, but books the first open slot days out without asking dispatch whether anything sooner can be made.
- 1Weak
- Promises this afternoon without checking, or books it with a new service fee and moves on.
Tell me about a time a customer was angry at you for something you didn't cause. What did you say first, and how did the call end?
CSRs take the heat for late crews, missing parts and other people's mistakes. You need someone who doesn't take it personally or pass the blame.
Follow-ups
- Under the yelling, what was the customer actually upset about?
- What did you do after you hung up?
- How did you know whether the customer was satisfied?
- 5Strong
- Picks a real call. Let them finish, said sorry for what happened without blaming a coworker, checked the schedule or the field for facts, gave a specific next step and time, and called back when promised. Knows how it ended, such as a kept booking or a calmer follow-up.
- 3Mixed
- Stayed polite and the caller hung up calmer, but the candidate passed it to someone else with no next step or callback time of their own.
- 1Weak
- Blames the technician or the customer, says they matched the caller's tone, or left them on hold until they gave up.
Here are four calls: a refund request, a caller who says your crew damaged their floor, a caller asking for a different technician, and a rude caller who still wants to book. Which do you handle yourself, which go to a manager, and why?
Sending everything up buries the manager; sending nothing up makes promises the company can't keep. This shows where the candidate draws the line.
Follow-ups
- When you hand off a call, what do you tell the manager so the customer doesn't have to repeat it?
- What do you tell the customer while they wait?
- What would you never say on the damage call?
- 5Strong
- Books the rude caller and handles the technician request by your policy, with a note. Sends the refund and the damage claim to a manager the same day with a written summary, gives each customer a callback time, and doesn't guess at fault or promise payment.
- 3Mixed
- Sorts the calls sensibly but hands them off cold, with no summary or callback time, or sends all four up to be safe.
- 1Weak
- Promises the refund or the repair to calm the caller, or argues about whether the crew did the damage.
A caller booking a routine visit mentions, almost in passing, that the house has smelled like gas since last night. What do you do?
Gas calls don't come often, and nobody should make up the steps on the spot. You want someone who catches the aside and follows your written steps exactly.
Follow-ups
- What exactly do you tell the caller to do, and in what order?
- What happens to the routine visit they called about?
- Who at the company do you tell, and when?
- 5Strong
- Stops the booking. Tells them to hang up and leave now, without touching light switches, lighting anything or using a phone inside, and to call the gas utility's emergency line or 911 from outside. Doesn't offer a technician as the fix. Logs it and tells the manager.
- 3Mixed
- Gets them out of the house and calling the utility, but in their own words instead of your script, and doesn't log it or tell anyone, so nobody follows up about the visit.
- 1Weak
- Finishes booking the routine visit and puts the gas smell in the notes, or offers to send a technician over to check it.
You're the only one on the phones. You're halfway through a booking, two lines are ringing, and a web request just came in marked urgent. What do you do?
One CSR covering the phones while booking is normal in a small office. You need someone who keeps every caller and finishes every booking.
Follow-ups
- What do you say to the caller you're with?
- What do you say when you pick up a ringing line?
- When do you tell your manager the desk needs help?
- 5Strong
- Asks the current caller for a short hold or wraps up fast, answers each new line by asking if it's an emergency before a brief hold or a set callback, saves the half-done booking, then works the web request and voicemails by urgency. Tells the manager if this keeps happening.
- 3Mixed
- Stays polite and loses nothing, but lets lines roll to voicemail without checking for emergencies, or leaves the web request for the end of the day.
- 1Weak
- Rushes the current caller off the phone, or lets the other lines ring.
Walk me through a customer system you used every day, like a scheduling tool or CRM. How did you keep the records clean when the phones were busy?
Duplicate customers, old phone numbers and blank notes slow down every later call. This shows whether the candidate treats the records as part of the job.
Follow-ups
- What did you do when you found a duplicate or out-of-date record?
- Tell me about a mistake you made in a record and how you caught it.
- How did you learn the last new system you had to use?
- 5Strong
- Names the system and specific habits: searches before creating a customer, confirms the phone and address on every call, writes notes in a set order, merges or flags duplicates. Owns a real mistake and the habit that came from it.
- 3Mixed
- Used the system well enough but cleans up records only when asked, or can't recall catching an error.
- 1Weak
- Says notes can wait until the end of the day, or can't describe the system they used.
Work exercise: two role-play calls
Write two short made-up scripts. Call one: a new customer books a repair and mentions a second problem or an older system you also service. Call two: a customer whose technician is [an hour] late, with no call from the office. Plant easy-to-miss details: a street name that sounds like another, a gate code, a callback number. Play each caller while the candidate books in your software's training mode or on a paper form, [20] minutes total. Then compare the booking with your script.
What to look for
- Listening: lets the caller finish, asks about the problem before reaching for the calendar, and plays back what they heard.
- Accuracy: the address, phone number, gate code and problem on the booking match your script, with nothing you'd have to call back about.
- Booking: offers a specific time on call one, mentions the extra service once, tied to what the caller said, and takes no for an answer.
- Tone with the late customer: apologizes once, finds out or promises to find out where the technician is, gives a time for the next update, and doesn't blame the technician.
- Ends each call with a read-back and a clear next step.
Use made-up materials, never real customer work, and keep it to the time shown. Follow your own safety rules for anything hands-on.
Reference check questions
Tell finalists you'll call a former manager, and get their permission first. Ask about what they did, not whether they were nice.
- When you checked their bookings, how often did something need fixing, like an address, a phone number or the job type?
- If you tracked booking rate or missed calls, how did theirs compare with others working the same phones and hours?
- Which calls did they bring to you, and which did they handle alone? Did you agree with where they drew the line?
- Tell me about an upset customer they handled that you heard about afterward. Would you put them back on your phones?
Questions to skip, and what to ask instead
Ask only what the job needs. Questions that touch age, health, family or pay history can break federal, state or local law, even when you mean well.
SkipWhere's that accent from?
AskJudge clarity the way callers would: in the role-play, did the caller understand them, and did they understand the caller? EEOC guidance says an accent can count only if it materially interferes with doing the job.
SkipWho watches your kids if a storm keeps the phones busy late?
AskIn storms and [your busy season], shifts can run until [time]. How would that work for you?
SkipAny health problems that would make sitting at a desk all day hard?
AskTell every candidate the same thing: this job means about [eight] hours a day at a desk on a headset. Can you do that, with or without reasonable accommodation?
Common mistakes when hiring a customer service representative
Grading the role-play by how it sounded
A call can feel great and still leave a wrong address and no arrival window on the booking. Score the role-play from the booking and your script side by side, not from memory of the conversation.
Hiring for speed instead of bookings
Some call centers rate people on short calls. In your office, a short call that doesn't book is a lead you paid for and lost. Ask what they were measured on before, and watch whether they ask for the booking.
Hiring in the rush
The phones are busiest when you most need help, so it's tempting to hire whoever can start Monday. Run the two calls anyway. They take twenty minutes and show you who would drop calls in a storm.
Customer service representative interview FAQ
What are good customer service interview questions for a home service company?
Test the calls that cost you money: an address taken on a bad line, a price shopper with a lower quote, a repeat problem when the schedule is full, and a gas smell mentioned in passing. Then build more from your own phones: pull a week of call notes, pick the calls that went badly, and turn each into a situational question.
Should I give customer service candidates a typing test?
A typing-speed test tells you less than watching them type while they listen, which is the real job, so use the role-play and compare the booking with your script. Whatever test you use, EEOC guidance says it should be tied to the job, and applicants with disabilities can ask for an accommodation in how it's given.
Can I require a CSR to speak Spanish or another language?
Yes, if the job truly needs it, for example because many of your callers speak that language. EEOC guidance says a fluency requirement, in English or any other language, is lawful only when it's needed to do the job well. Test it in the role-play, and ask every candidate the same way.
Should I hire a CSR with sales experience?
If booking rate counts or the CSR offers maintenance plans, sales experience helps, as long as they ask for the booking without pushing. If the desk is mostly billing and scheduling, weigh calm and accuracy more. Decide which before you post the job, so you score candidates against the right thing.
Sources
- O*NET OnLine: Customer Service Representatives (43-4051.00)
- EEOC: Employment tests and selection procedures
- EEOC: Enforcement guidance on national origin discrimination
- EEOC: Pre-employment disability-related questions and medical exams
- PHMSA: Recognizing and responding to natural gas emergencies
- U.S. Office of Personnel Management: Structured interviews
Start Hiring Now.
Tell us who you need to hire. Compare plans, then work with HireBus to set up your first role.

Their process and custom assessments have relieved us of so much stress.Aaron Luthi, ACE Pressure Washing
Plan details, setup costs, and advertising spend · See pricing

