On this page
Ask a customer service rep or dispatcher to describe how they handle real calls: an urgent problem, an upset customer, two jobs that want the same truck, a mistake they made. Listen for a specific example, a calm order of steps and honesty about errors. Keep every question tied to the job and test the skills with a short phone role-play.
Key takeaways
- Ask about situations from your own office, such as a no-heat call, a late tech or a customer asking for a price you cannot give.
- A strong answer names the steps in order and the information captured. A weak one stays general.
- Run a short phone role-play and a scheduling exercise with every finalist, with the same scenario for each.
- Keep every question job-related. Federal law bars discrimination on protected characteristics, and state rules can go further.
- Check references on reliability, accuracy and how the person treated upset customers.
The person who answers your phone and builds your schedule decides how many of your calls turn into booked jobs, and how many customers stay angry after a late truck. The 16 questions below are written for a customer service rep, office coordinator or dispatcher at a service company with a crew in the field. Each one shows what to ask, why it matters in this seat, what a strong answer sounds like and what should worry you. Use a short, fixed list so every finalist answers the same questions, take notes during the interview, and score them afterward. Once the person is hired, onboarding and a first-week checklist keep the early weeks organized, and a CRM built around your own call and dispatch steps makes the training faster.
The EEOC says pre-employment information should be limited to what is essential to decide whether a person is qualified for the job, that inquiries which may reveal a protected trait should generally be avoided, and that employers are explicitly prohibited from asking about disability before making an offer. Do not ask about age, family plans, children, health, religion, national origin or similar topics, and do not ask for a photo. State and local laws may add limits. This is general information, not legal advice, so have a qualified employment attorney review your process.
1. Walk me through the first minute of a call
Ask: "A new customer calls with a leak coming through the ceiling. What do you say and ask in the first minute?"
Why it matters: the greeting and the first questions set the tone and decide whether an urgent job reaches a tech.
Strong answer: greets by company name, asks for a callback number early, finds out whether there is active damage or danger, gets the address, and tells the caller what happens next. Red flag: starts with a long list of form fields while the caller is still describing the emergency.
2. Tell me about an upset customer you calmed down
Ask: "Describe a time a customer was angry on the phone. What did you say, and how did it end?"
Why it matters: you will not get through a season without a missed window or a billing question. You want someone who gets the facts before reacting.
Strong answer: a specific story where the person listened first, repeated the problem back, said what they could do and followed up. Red flag: blames the customer, or the story has no ending.
3. A caller wants a price you cannot give
Ask: "A caller says, 'Just give me a number.' The job needs a site visit. What do you say?"
Why it matters: a rep who stonewalls loses the lead, and one who guesses creates a quote you will have to honor.
Strong answer: explains why a visit is needed, shares whatever the company allows (a diagnostic fee, a typical visit window), and offers to book it. Red flag: invents a number to end the call.
4. Two jobs want the same tech at 2 PM
Ask: "One is a routine tune-up. One is a no-heat call with a baby in the house. How do you decide, and what do you tell each customer?"
Why it matters: dispatch is triage. You want someone who makes the call, then protects the displaced customer.
Strong answer: asks what your priority rules are, moves the routine job with a fresh window and a call before the old one starts. Red flag: bumps the customer by text with no explanation, or can't explain the choice.
5. What do you capture on every new call?
Ask: "List what you write down on a new job call before you hang up."
Why it matters: bad data costs a second trip. Missing gate codes, wrong unit numbers and no callback number are all avoidable.
Strong answer: name, mobile number, service address, the problem in the customer's words, access details, who will be home, and how they found you. Red flag: relies on memory or says "I'll figure it out later."
6. A tech calls in sick at 6:45 AM
Ask: "Your first tech is out and the day is full. Walk me through the next hour."
Why it matters: morning disruptions are routine in field work, and the first calls decide how many customers hear about a delay.
Strong answer: pulls the day's list, sorts by urgency and appointment type, checks who can absorb jobs, tells the owner, and calls affected customers before their window opens. Red flag: waits for the customers to call in.
7. Describe a scheduling or data-entry mistake you made
Ask: "Tell me about an error you caused at work. What happened and what did you change?"
Why it matters: everyone double-books once. What you are listening for is whether they notice, say so and fix the process.
Strong answer: owns the mistake, explains the repair for the customer, and describes a check they added. Red flag: claims no mistakes, or blames a coworker or the software.
8. What phone, calendar and software tools have you used?
Ask: "Which scheduling, CRM or texting tools have you used, and what did you do in them every day?"
Why it matters: a rep who has used any job system learns yours faster. Ask for tasks, not buzzwords.
Strong answer: names the tool, describes the tasks (creating a job, assigning a tech, sending a reminder), and mentions something they disliked and worked around. Red flag: lists products but can't describe a daily task.
9. Run a three-minute phone role-play
Do: you play a caller with a real problem from your business, with two details held back that a good rep will ask for. Use the same script for every finalist and score on a short sheet: greeting, questions asked, tone, accuracy of the notes, next step offered.
Why it matters: a role-play tests the job itself. It measures what the person will do every day, so it stays job-related, and every finalist should get the same one. Red flag: talks over the caller or ends the call without confirming the appointment.
10. Give them a one-page scheduling exercise
Do: hand over a sample day with four techs, eight jobs of different lengths, one emergency and one cancellation. Ask the candidate to build the board and explain two choices. Fifteen minutes is enough.
Why it matters: you see how they handle drive time, appointment windows and conflicting constraints. Strong answer: groups nearby jobs, leaves slack, flags the one that doesn't fit and asks a clarifying question. Red flag: packs the day so tightly one delay breaks it.
11. The tech is running an hour late. Now what?
Ask: "A customer's window ends in 20 minutes and the tech is stuck. What do you do?"
Why it matters: a call or text before the window ends helps keep customers on your side.
Strong answer: contacts the tech for a real arrival time, contacts the customer first, offers a choice (wait or reschedule) and logs the delay. Red flag: says nothing and hopes the tech arrives.
12. A customer demands a discount you cannot approve
Ask: "Someone wants money off the bill and your policy doesn't allow it. What do you say?"
Why it matters: the rep must hold a boundary without making the customer feel brushed off.
Strong answer: explains what they can do, brings in the owner or a manager, and writes down the complaint. Red flag: promises a credit on the spot to end the call.
13. The phone rings while you're on another call
Ask: "You have one customer on the line and two more lines lighting up. How do you handle it?"
Why it matters: a busy morning is the whole job. A missed call can end up with the next company the caller tries.
Strong answer: asks the caller to hold, finishes the thought, picks up with a clear script, uses voicemail and callback rules, and logs missed numbers. Red flag: ignores the line or hangs up on the current caller. See phone answering tips for the routine you want them to follow.
14. A customer replies STOP to a text
Ask: "What do you do when a customer texts the word STOP?"
Why it matters: the rep may send reminders and updates. Consent and opt-out rules for texts are covered in our TCPA guide, and honoring a STOP request is a baseline.
Strong answer: stops the texts, records the opt-out in the system and uses another channel for urgent job notices that the customer has agreed to. Red flag: thinks a one-off reminder is fine.
15. A customer says "Don't record this call"
Ask: "If your company records calls and a caller asks you to stop, what do you do?"
Why it matters: call-recording consent laws vary by state, so the rep should follow your written rule. Read can you record business calls and set that rule before the interview.
Strong answer: follows the stated policy, knows who to ask when the case is unusual, and never improvises a legal answer. Red flag: shrugs it off.
16. A customer complains about a tech's behavior
Ask: "A caller says your tech was rude. What do you say and what do you do afterward?"
Why it matters: the rep is the owner's early warning. Complaints that reach the right person fast stay small.
Strong answer: listens, takes down the details, thanks the customer, promises a follow-up from a named person and passes it to the owner the same day. Red flag: defends the tech on the spot, or hears the story and does nothing.
What should you check with references?
Call two former supervisors and ask about the same things you tested: attendance, accuracy, how the person handled upset customers, and whether they would rehire them. Keep the questions about work performance. Tell the candidate you will call, and keep what you learn in the hiring file for the period your state requires.
Where to start
- Pick six questions. Use 1, 4, 5, 7, 11 and 12, and ask the same six in the same order for every finalist.
- Add the role-play and the scheduling exercise. Items 9 and 10 show the real work in under half an hour.
- Write the red flags on the score sheet. Score right after each interview, before you compare people from memory.
Frequently asked questions
How many interview rounds does a customer service or dispatch hire need?
Two is usually enough for a small company: a phone or in-person interview with the standard questions, then a second meeting with the role-play and scheduling exercise. Keep the process the same for every finalist.
Should I ask about availability and schedule?
Yes, if the job has set hours, on-call rotations or weekend coverage. State the real schedule and ask whether the candidate can meet it. Ask every candidate the same way and keep it about the schedule.
Can I use a paid trial day?
Check with an employment attorney or your state labor agency first. Rules on unpaid work and trial shifts vary, and a short role-play during the interview gets you most of the signal.
What if a candidate raises their own family or health situation?
Do not follow up on it. Redirect to the job requirements and the schedule, and write down only what is job-related.
General information for service-business owners, not legal, tax or financial advice. Rules vary by state; check with a qualified professional for your situation.