Tell me about yourself
Why they ask. It tests verbal clarity and relevance — the same skill you will use to open a call and set expectations in thirty seconds.
How to approach it. Give three beats: where you have worked and on which channels, what you are good at with one piece of evidence, and why this role next. Keep it under ninety seconds and finish on a clean stop rather than trailing off.
Support agent, subscription software, two years
I have spent two years on a five-person support team for a subscription billing product, handling around 40 tickets a day across email and live chat in Zendesk, plus phone cover on Fridays. Most of my volume is billing disputes and login problems, so I got quick at reading an account history before I reply rather than asking the customer to repeat themselves. Last year I rewrote our eight most-used macros because they were too formal and customers kept replying to ask what they meant; re-contacts on those topics dropped noticeably over the next quarter. I want to move to a role with more phone work and a product I can learn deeply, which is why this one interested me.
Mistake to avoid. Reciting your CV from school onwards. Fix: start at your most recent support role and work forward only.
Tell me about a time you dealt with an angry customer
Why they ask. This is the de-escalation and emotional control question. They want to hear what you said, in what order, and whether you stayed steady.
How to approach it. Pick a real incident with a resolution. Narrate the sequence: acknowledge, take ownership of the next step, state what you can do, confirm. Say how the customer sounded at the end, not just what you did.
Contact centre agent, home delivery retailer
A customer called on a Saturday about a kitchen appliance that had missed two delivery slots. He was shouting before I finished my greeting. I let him get the whole story out without interrupting, then repeated it back in one sentence so he knew I had it. I apologised for the two missed slots specifically rather than generally, told him I was not going to promise a third slot until I had checked the depot notes, and put him on a two-minute hold. The item was flagged damaged in transit. I booked a replacement for the Tuesday, raised the delivery-fee refund myself, and gave him my direct extension. He was calm by the end and rang back on Tuesday to say it had arrived.
Mistake to avoid. Describing the customer as unreasonable. Fix: describe the problem as unreasonable and keep your language about the customer neutral.
A customer asks for a refund your policy does not allow. What do you do?
Why they ask. It tests judgement within policy — whether you bend rules quietly, hide behind them, or handle the refusal cleanly and escalate when the case deserves it.
How to approach it. Show three steps: check whether an exception route genuinely exists, decide, then deliver the no with an alternative. Say what you would document.
Agent, e-commerce support, Gorgias queue
First I check the account, because about one time in five the request actually is covered — a warranty date, a goodwill credit note, a promotion the customer did not know about. If it genuinely is not, I say no once, plainly, and early in the reply, because burying it three paragraphs down makes people angrier. I explain the reason in one sentence, then offer what I can: an exchange, a partial credit, or a documented exception request to my team lead where the customer has been affected by our error. Last month I sent four exception requests and two were approved. I always note the refusal and the reason on the ticket so the next agent does not accidentally reverse it, and I tell the customer where the policy is written.
Mistake to avoid. Saying "I'll see what I can do" when you already know the answer is no. Fix: give the no first, then the alternatives.
How do you keep quality high when handle time is being measured?
Why they ask. It tests how you work with metrics, and whether targets push you into transferring or rushing customers off the line.
How to approach it. Show that you understand what handle time is for, name a habit that shortens calls without cutting corners, and be honest about the trade-off.
Phone agent, utilities contact centre
I treat handle time as a symptom rather than a target. The two things that actually shortened my calls were preparation and structure: I read the account and the last two contact notes while the greeting is playing, and I tell the customer at the start what the call will cover so we do not wander. That took my average down by roughly a minute without me hurrying anyone. Where I refuse to trade is the closing check — I always confirm the fix and the next date before I let the call end, because a 30-second confirmation is cheaper than a repeat call the next day. If a case genuinely needs fifteen minutes, I take fifteen minutes and flag it to my team lead so the number has context.
Mistake to avoid. Claiming metrics do not matter to you. Fix: name the metric you watch and the one habit that improved it.
Walk me through how you would troubleshoot an issue you have never seen
Why they ask. It tests troubleshooting method — whether you have a repeatable process or you guess and escalate immediately.
How to approach it. Give a numbered method: reproduce, narrow, check documentation and known issues, then escalate with evidence. Mention what you tell the customer while you work.
Technical support agent, SaaS product
I start by getting the facts I cannot guess: what they did, what they expected, what actually happened, browser or device, and when it started. Then I try to reproduce it on a test account, because a bug I can reproduce is worth five I cannot. Next I narrow it — is it this one user, this one account, or everyone on that plan? Then I search the knowledge base and our internal Slack channel for the same symptom, since roughly half of what looks new to me has been seen by someone else. If it is genuinely new, I escalate with the account ID, the steps, a screen recording and the timestamp so engineering does not have to ask. Meanwhile I tell the customer what I have ruled out and when I will next update them, even if I have no answer yet.
Mistake to avoid. Going silent while you investigate. Fix: promise an update time and send it even when there is no progress.
When do you escalate, and what does a good escalation look like?
Why they ask. It tests judgement and teamwork. Escalating everything wastes senior time; escalating nothing burns customers and breaks SLAs.
How to approach it. Name your triggers explicitly, then describe the format of a handover a colleague can pick up without calling you.
Senior agent, insurance claims support
I escalate on four triggers: it needs an authority I do not have, it involves a legal or safety issue, the customer has asked for a manager and I have already tried once to resolve it, or I have hit my own time limit on investigation — for me that is about twenty minutes of dead ends. A good escalation is a summary, not a forward. I write four lines: what the customer wants, what I have already tried, what I think should happen, and what has been promised and by when. I attach the reference numbers. My team lead used to spend the first five minutes of every escalation re-reading the thread; once three of us moved to that format she stopped having to.
Mistake to avoid. Escalating by transferring the customer with no context. Fix: brief the receiving person before you transfer, even in one sentence.
Rewrite this reply so it keeps the answer but changes the tone
Why they ask. It tests written clarity — the core skill for email and chat queues, and the one most often assessed with a live exercise.
How to approach it. Keep the decision the same. Lead with the answer, cut hedging and passive voice, add one line of acknowledgement and one clear next step. Read it aloud in your head to check it does not sound cold.
Email support agent, retail brand
The original said: "Unfortunately as per our terms your request cannot be processed as the returns window has expired." I would send: "Hi Sam — I'm sorry, I can't refund this one. Our returns window is 30 days and the order was delivered on 2 March, which puts it outside. What I can do is send a replacement part free of charge, or raise a repair under the manufacturer warranty, which runs for another eight months. Tell me which you'd prefer and I'll set it up today." Same decision, but the customer gets the answer in the first line, a reason with a date, two options and an action. I also dropped "as per our terms", because that phrase reads as a shrug.
Mistake to avoid. Adding warmth by adding length. Fix: cut a sentence for every one you add.
The queue is 40 deep and two agents have called in sick. What is your first move?
Why they ask. It tests prioritisation under pressure and whether you think about the queue as a whole rather than just the ticket in front of you.
How to approach it. Show triage logic, not heroics. Sort by impact and breach risk, communicate outward, and only then start working.
Team lead cover, chat and email support
My first move is not to answer a ticket — it is to sort the queue. I filter by SLA breach risk and by anything tagged outage, payment failure or vulnerable customer, because those cost the most if they sit. Then I scan for duplicates: on a bad morning ten of the forty are the same incident, and one status-page update plus a macro clears them in twenty minutes. I turn on the queue-delay auto-response so customers know we are behind and by roughly how much. Then I tell my manager the number and what I need — usually an hour of cover from someone off-phones. Once that is done I work top down. The day I first did this we cleared 40 down to 12 before lunch, mostly because 11 tickets turned out to be one payment-gateway fault.
Mistake to avoid. Working oldest-first out of fairness. Fix: sort by impact and breach risk, then by age within each band.
Tell me about feedback you received from a quality review
Why they ask. It tests coachability, which predicts how fast you will get to standard on their scorecard.
How to approach it. Pick real, slightly uncomfortable feedback. Say what it was, what you changed mechanically, and how you knew it worked.
Agent, telecoms support
My quality reviewer marked me down three months running for not setting expectations at the start of calls. I thought I was being efficient; the recordings showed customers interrupting me because they did not know how long the fix would take. She played two calls back to me, which was uncomfortable but fair. I wrote a six-word opener on a sticky note — name, what I'll check, how long — and used it on every call for a fortnight until it stuck. My next three reviews scored full marks on that line, and my transfers dropped because customers stopped asking for a manager mid-diagnosis. I now use the same opener on chat, as the first message.
Mistake to avoid. Choosing feedback that is secretly a compliment, like "I care too much". Fix: pick something you were genuinely marked down for.
Tell me about a mistake you made that affected a customer
Why they ask. It tests ownership and honesty — the behaviour that decides whether a small error becomes a complaint or a recovered relationship.
How to approach it. Choose a real error with a contained outcome. State it plainly in the first sentence, then the repair, then the change you made so it does not recur.
Support agent, B2B software
I closed a ticket as resolved without checking that the customer's second site had also been migrated. Two weeks later their office manager called because that site had been offline for a fortnight and nobody had picked it up. I did not try to spread the blame — I told her it was my miss, gave her a same-day fix window, and rang her back myself when it was done rather than emailing. Internally I asked my lead to add a two-line checklist to our migration macro so the agent has to confirm every site before closing. I also spent a week auditing the twelve migration tickets I had closed that month; one other had the same gap, and I caught it before the customer did.
Mistake to avoid. Picking a mistake that was really someone else's. Fix: use "I" for the error and "we" only for the fix.