Explain a Service Complaint in an Inter­view

A customer complained, you took part in the response, and now an interview asks you to explain it. The difficult part is not finding a dramatic ending. It is separating what the customer reported, what you checked, what you were authorised to do and what happened after your involvement.

This guide helps you prepare one account of a past service complaint. It is not a complaint-handling procedure, legal advice or a script for a live customer situation. For a wider set of role questions, use the customer service interview guide.

Choose an example you can discuss safely

Choose a real event you remember well enough to explain without private records. An ordinary complaint about an unclear collection message may be more usable than a serious incident you cannot discuss. Do not bring customer messages, account details or internal screenshots into an interview or practice tool without permission for that specific sharing.

If the complaint involved harassment, discrimination, safety or a legal claim, this guide cannot advise on it; choose a different example for this exercise.

Describe people by their role where possible. Removing a name does not establish permission to discuss the event. If you cannot describe the event without disclosing confidential or personal information, choose another example or explain the limit.

If you have never handled a complaint, say so and ask whether a study or volunteering example would answer the question. If it would, identify it clearly as such. Do not turn a hypothetical answer into a claim about paid work.

Separate the report from your own checks

Make short notes under three prompts:

• What did the person say had happened?
• What did you personally establish, and how?
• What remained uncertain when your part ended?

In an invented example, “The customer said the collection email was unclear” and “the email was wrong” are different claims. Use the second only if you actually established it and can explain that check safely. Avoid guessing motives or describing the person as unreasonable to make yourself look better.

Keep the initial issue separate from later discoveries. Otherwise your answer may imply that you knew the cause before you investigated it. You do not need to recreate every exchange; include only the facts needed to understand your contribution.

Name the boundary of your authority

Explain what you could decide, what required someone else's decision and what you passed on. Checking information, explaining an available next step and asking a supervisor to decide are distinct actions. Do not claim that you approved an exception, refund or remedy if you only requested it.

Describe the rules that applied in that actual role without presenting them as universal service rules. An interview answer should not suggest that ignoring policy is proof of initiative. Equally, do not invent a policy to justify what happened.

If the issue passed to a colleague, say what information you supplied and what you knew afterwards. Escalation is part of the account, not evidence by itself that the complaint was resolved.

Build an answer with an honest endpoint

Fictional illustration, not a real customer story or a procedure to copy:

“At a community craft event, a visitor said our collection message did not say which table to use. My role was to staff the information desk; I could check the event's public collection list but could not change collection arrangements. I checked the displayed table names and showed the visitor the listed table. They also wanted the organisers to change the message. I passed that request to the event coordinator and explained that the coordinator would need to decide. I saw the visitor reach the collection table, but I did not hear the coordinator's later decision.”

The example distinguishes a reported problem, a limited check, a permitted action and an unknown later result. It does not claim that the visitor was satisfied or that the message was changed. Your own answer needs your own facts, not this event with the names replaced.

Check the outcome you are claiming

The National Careers Service STAR guidance separates your action from the result and what you learned. Use that distinction to check whether your ending goes beyond your evidence.

“I submitted the request” describes your action. “The coordinator changed the message” describes a later decision. “Complaints stopped” would require evidence you may not have. Keep a partial, unresolved or unknown outcome visible rather than adding a successful ending.

Prepare to explain what you would reconsider, if anything, without inventing a lesson. You may conclude that your account lacks information, rather than claiming that your approach prevented future complaints.

Rehearse the follow-up questions

Ask a practice partner to question one boundary with invented practice questions such as: “What could you decide?”, “What did you check yourself?” or “How did you know the matter was closed?” If your answer cannot support “closed”, change that word.

Practice with non-sensitive notes. Agree before recording or sharing a practice session. Do not use a tool to generate answers during an actual interview or assessment without the organiser's explicit permission.

This guide is published by Muqabala. You can use Muqabala's practice page as a starting point for independent preparation. The aim is a clear account of your real contribution, including where your authority and knowledge ended.