The Disconnection at the Front Counter
You are on the front counter of an electricity retailer at 4:52 pm on a Friday; the office closes at 5:00. A customer arrives with a phone screenshot showing a payment reference and says his power was disconnected at 9:00 that morning even though he paid online three days earlier. He is speaking loudly, and four people are waiting; your only colleague has gone on lunch and will not return until 5:15. The billing system becomes read-only at 5:00 for month-end processing, so no new work orders can be raised after that. Reconnection requires a field work order, and the field team's next available slot is 8:00 tomorrow. Policy allows a payment arrangement but not confirmation of a payment without matching a receipt to the account. The customer mentions a toddler and a medical fridge.
1. What would you do in the first ten minutes?
Read the worked answer
Acknowledge the customer immediately and lower the temperature before solving the transaction. Say his name, confirm you have heard the key facts, and move him to the side of the counter or a nearby room if one is free, so the queue is not an audience. Offer a seat and water. Do not argue about whether he paid; the immediate issue is that he has no power and a medical fridge.
Then triage in this order:
- Check the account in the billing system before 5:00. Look for the payment, any failed transaction, the disconnection order and the account status. Ask for the account number or address, not just the screenshot, and note the reference number.
- Treat the medical fridge and toddler as a vulnerability signal. Ask whether any medication requires refrigeration and whether he has a safe alternative tonight. Escalate to a supervisor or the on-call welfare process immediately; do not wait until the payment question is resolved.
- Manage the queue. Apologise to waiting customers, give a realistic wait time, and ask whether anyone has a quick drop-off. Call your colleague back early if possible.
- Record everything with times, what he said, what you checked and who you called.
The first ten minutes decide whether this becomes a complaint or a resolved case. Speed on the welfare check matters more than winning the payment argument.
2. What can you promise about payment and reconnection, and what must you not promise?
Read the worked answer
You can promise actions you control: that you will check the account before the system closes, log the payment reference, request priority reconnection for the 8:00 field slot, give him a reference number, and call him before 6:00 pm with the result. You can explain the payment arrangement option if the payment genuinely has not landed.
You must not promise same-night reconnection unless the field team confirms it, because the work order system is read-only after 5:00 and the next slot is 8:00. Do not confirm that his payment was received until the receipt matches the account - a screenshot with a reference number is evidence to investigate, not proof of payment. Do not say 'you should have paid earlier' or 'the system won't let me' as a closing statement; both shift blame and escalate.
Be explicit about the uncertainty: 'I can see a reference, but I cannot yet match it to your account. I will log it now and call you by 6:00 with either confirmation or the exact next step.' If the payment is matched, say what will happen to any reconnection fee or arrangement. If it is not, explain the arrangement process and the earliest reconnection time without overstating your authority.
3. What would you document and hand over at the end of the day?
Read the worked answer
Document the arrival time, the customer's account and contact details, the disconnection date, the payment reference and the source of the screenshot, the vulnerability disclosure (toddler, medical fridge), the account checks performed before 5:00, the reconnection request and its reference, what was promised and by when, and any supervisor or welfare escalation. Note the queue situation only if it affected service, not as an excuse.
At handover, give the supervisor a short case note: what is unresolved, the 8:00 field slot, the callback deadline and who owns it. If your shift ends before 6:00, confirm that someone else will make the call, or make it yourself before leaving. A promise of a callback that nobody keeps turns a service failure into a complaint.
Also flag the root cause for review: why a payment made three days earlier did not prevent disconnection, and whether the vulnerability flag should have blocked it. That is a process issue, not a counter issue, and it should reach the billing or customer-care team. Close with a brief note to the customer's record so the next agent does not restart the conversation.