“Tell me about a difficult customer you handled” is a behavioural question: the interviewer wants a real event from your past, told in enough detail to judge how you behave under pressure. The best answers do three things. They make the customer’s problem understandable, they show your specific actions (not “we” and not “I always”), and they end with a result that includes follow-through.
Below are four answers, each annotated. One is weak on purpose so you can see what to avoid. The others come from different settings, because what “difficult” means changes a lot between a shop floor, a hotel lobby, an IT helpdesk and a business account.
Why employers keep asking this
In many customer-facing jobs, difficult customers are a routine part of the work rather than an exception. O*NET, the US occupational database, reports that 42% of respondents in customer service representative roles deal with unpleasant, angry or discourteous people every day. Its task list for that occupation includes keeping records of complaints, checking that changes were made to resolve customers’ problems, and referring unresolved grievances to the right department.
Those three tasks are a useful checklist for your story: did you record it, did you check it was fixed, and did you escalate properly when it was beyond you?
Organisations also tend to treat complaints as information, not just as problems to close. ISO 10002, the international guideline on complaints handling, covers analysing complaints to improve product and service quality, alongside offering an open, effective and easy-to-use complaints process. An answer that ends with “and we changed how we did X” shows you understand that.
The structure every example below uses
All four examples follow STAR, which the UK National Careers Service describes as the situation, the task you were given, the action you took, and what happened as a result and what you learned. In practice, aim for roughly this balance:
- Situation and task: two or three sentences. Enough to explain why the customer was upset.
- Action: the longest part. What you said and did, in order.
- Result: what happened to the customer, and what changed afterwards.
Example 1: the weak answer
“I deal with difficult customers all the time. I always stay calm and listen to them. One time a customer was really rude about a delivery, so I apologised and sorted it out, and in the end they were happy. I think the key is just to be patient and not take it personally.”
What goes wrong:
- “All the time” and “always” describe a habit, not an event. The interviewer asked for a specific time.
- “Really rude” labels the customer without explaining the cause. Interviewers want to see that you understood why they were upset.
- “Sorted it out” hides the actions, which are the whole point of the question.
- “They were happy” is an unsupported claim. How do you know?
- The closing advice is generic and could come from anyone.
Example 2: retail, an error that was the shop’s fault
“I was working on the customer service desk at an electronics shop on a Saturday. A customer came back with a laptop we had set up for her. Her files had not been transferred from the old machine, as the receipt said they would be, and she needed them for work on Monday. She was raising her voice and other customers were watching.
“I asked if she’d like to sit at the side desk, which took the conversation out of the queue. I let her explain the whole thing before saying anything, then repeated it back: the transfer was paid for, it wasn’t done, and she needed the files by Monday. I said clearly that it was our mistake.
“I checked with the technical team. They couldn’t do it that day, but I could book the first slot on Sunday morning. I asked my supervisor if we could refund the transfer fee because of the extra trip, and he agreed. I wrote everything on the job sheet, including her deadline, and gave her my name and the direct number for the desk.
“On Sunday I checked the job had been completed before she arrived. She thanked the technician and later left a comment on our feedback form. I also told my supervisor the job sheet didn’t have a box to confirm data transfer had been done, and a checkbox was added to the form.”
Why it works:
- The situation explains why she was angry: a paid service wasn’t delivered, with a real deadline.
- Moving her away from the queue and repeating the problem back are concrete de-escalation actions, not adjectives like “calm”.
- The candidate admits fault without blaming the technicians.
- The refund needed approval, and the answer shows the candidate asked rather than overstepping.
- Checking the job was done before she arrived matches the “check changes were made” task. The form change shows the complaint led to an improvement.
Example 3: hotel front desk, a request you could not grant
“A guest arrived late at night expecting a sea-view room. His booking, made through a third-party site, was for a standard room, and we were fully booked. He was tired, had been travelling with two young children, and said he’d been promised the view.
“I didn’t argue about what the booking site had told him, because I couldn’t know. I showed him the booking details on screen so we were looking at the same information. I explained that I couldn’t move him that night because every room was occupied, and offered what I could: an upgrade to a sea-view room for the remaining two nights if one became free, which I checked with the duty manager first, and a cot and extra towels sent up immediately.
“I logged the request in the system with a note for the morning shift. The next morning a sea-view room did become available after a checkout, and the morning team moved them. Before my shift ended I’d also left a note for the reservations manager suggesting we flag third-party bookings that mention room views, so guests could be contacted before arrival.”
Why it works:
- It shows how to say no: honestly, with the reason, and with alternatives.
- The candidate checked authority before offering the upgrade.
- The handover note means the promise was kept even though the candidate was off shift, which shows awareness of how teams work across shifts.
- The suggestion at the end turns one complaint into a fix for future guests.
If you work in hospitality, put examples like this into your CV as short achievement lines; the hotel front desk resume builder shows the kind of detail that suits the role.
Example 4: B2B or IT support, a customer who was partly wrong
“I was on the IT service desk for a software company. A client’s operations manager emailed the director, copying me, saying our system had ‘lost’ a week of records and threatening to cancel the contract. He was frustrated because his team had to re-enter data.
“I called him within the hour rather than replying by email, because a long written exchange would have made things worse. I asked him to walk me through what his team saw. While we spoke, I checked the logs and found the records hadn’t been lost. They had been saved under a test account someone on his side had been using.
“I didn’t open with ‘it was your mistake’. I told him the data was safe, shared my screen to show him where it was, and offered to move the records into the live account that afternoon. Then I said that we should make it harder for this to happen, and suggested disabling the test login on their production site, which he agreed to.
“I wrote up a short summary for him and the director with what happened and what we changed, so nobody was left with the impression the system had lost data. The client renewed later that year, and our team added a warning banner to test accounts for all clients.”
Why it works:
- Switching from email to a call is a judgement call worth explaining.
- The candidate investigated before defending the product.
- Correcting a customer without humiliating them is a harder skill than apologising, and this shows it.
- The written summary protects the company’s reputation and closes the loop with the senior contact.
- The banner for all clients is the “analyse complaints to improve” step from ISO 10002 in action.
All of these examples are illustrative. Use your own events, even if they seem smaller.
Choosing your own example
| Good choice | Poor choice |
|---|---|
| A situation where you took several distinct actions | One where you simply passed the customer to a manager |
| A customer with an understandable reason to be upset | A story whose main point is how unreasonable the customer was |
| A clear outcome you can describe | One where you never found out what happened |
| Something that led to a small improvement | A story that ends with “and that’s just how it is there” |
| Recent, within the last two or three years | A story from many years ago when you have more recent ones |
If the honest answer was that you escalated, that can still work, as long as you explain what you did before escalating and how you handed over. Escalating properly is part of the job.
Follow-up questions to prepare for
- “What would you do differently?” Have a genuine answer, such as acting sooner or checking something earlier.
- “What if the customer had become abusive?” Say you would follow the employer’s policy, stay professional, and involve a supervisor or security where appropriate. Nobody expects you to absorb abuse.
- “How did you feel afterwards?” Honesty is fine. Mention how you reset before the next customer.
- “Tell me about one you didn’t resolve.” Have a second, shorter example where the outcome was mixed, and focus on what you learned.
Customer service experience is valued well beyond customer service jobs. If you’re applying for a front-line role, the customer service resume builder shows how to turn stories like these into CV bullet points.
Frequently asked questions
What if I’ve never had a difficult customer?
Use the closest equivalent: a demanding client on a freelance project, a frustrated member of the public while volunteering, or a difficult stakeholder at university. Say plainly that it wasn’t a paid customer role.
How long should my answer be?
About two minutes. Keep the background short and spend most of the time on your actions.
Should I admit the company was at fault?
Yes, if it was. Interviewers respect honesty, and owning a mistake is often what calms a customer down. Don’t blame named colleagues.
Is “the customer is always right” a good line to use?
Avoid it. Example 4 shows that sometimes the customer is wrong, and the skill is resolving the issue without making them feel foolish.
Sources
- 43-4051.00 Customer Service Representatives, O*NET OnLine
- ISO 10002:2018 Quality management: Customer satisfaction: Guidelines for complaints handling in organizations, International Organization for Standardization
- The STAR method, National Careers Service (UK)