The Duplicate Debit on a Third-Party Call
You are a voice agent on the inbound billing line of a state electricity distribution company's domestic call centre in Bhubaneswar, handling queries in Odia, Hindi and English. A caller says he is the consumer's son and claims that Rs 1,450 was debited twice from his father's account on 4 March for the same bill. The CRM shows one receipt (RCPT/2025/004417) and a zero balance. The registered mobile number belongs to the father, who is not on the call. Your verification script requires the last four digits of the consumer number plus an OTP to the registered mobile; the son knows the consumer number but cannot receive the OTP because the phone is with his father at another address. Your average handle time target is 360 seconds and you are running at 402 seconds today. Quality audit penalises both unauthorised disclosure and premature closure without a proper disposition. The payment gateway team works 10:00 to 18:00 and reconciliation takes up to 48 hours.
1. Decide what you may and may not disclose to this caller, and describe what you do in the next two minutes of the call.
Read the worked answer
What is blocked: the caller is not the registered consumer and cannot complete OTP verification, so the account balance, bill history, bank details and payment status are all closed to him. Disclosing them would be an unauthorised-disclosure fail even if his story turns out to be true, because social engineering callers use exactly this framing.
What is still possible:
- Capture the claim without confirming anything - date (4 March), amount (Rs 1,450), receipt number quoted by the caller, and the fact that two debits are alleged.
- Log a payment-discrepancy ticket against the consumer number and give the caller the ticket ID, which contains no account data.
- Tell him what will happen next, not what the account currently shows: reconciliation within 48 working hours, and if a duplicate is confirmed the excess amount is adjusted to the next bill or refunded as per the refund process.
- Offer a route to full service: a callback to the registered mobile at a time the father is present, or the father can authorise in the company app.
Reasoning: the verification rule protects the customer, not the process; refusing data politely while still registering the complaint keeps the customer served and the audit clean.
2. Write the CRM note and disposition you would leave, and the follow-up you would schedule.
Read the worked answer
Note (free-text, factual, no speculation):
04-Mar call 15:42. Caller: son of registered consumer, name given, number not verified (no OTP - registered mobile with father). Consumer no. last 4: 7731 confirmed by caller. Claim: Rs 1,450 debited twice on 04-Mar for same bill; one receipt visible to agent RCPT/2025/004417. No account details disclosed. Payment discrepancy ticket PD-2025-11876 raised; forwarded to payment gateway team queue. Caller informed of 48-hr reconciliation timeline. Callback to registered mobile requested for 05-Mar 11:00.
Disposition: Payment dispute - pending reconciliation. Not Resolved, not Query answered - either would close the loop and kill the SLA clock.
Follow-up: a task on the ticket for 05-Mar 11:00 (registered mobile, father present), plus a 48-hour check against the gateway settlement file. If two debits are confirmed, raise the refund/adjustment request and inform the customer on the registered number.
Reasoning: the note must let a second agent, an auditor and the gateway team act without re-calling the customer; the disposition must keep the ticket open, because the customer's problem is not solved on this call.
3. Your team leader says your AHT is high and asks you to close such calls faster. How do you meet the target without breaking verification?
Read the worked answer
Speed has to come from handling, not from skipping steps.
- Front-load the structure. Open with the verification request in the first 15 seconds, before the caller narrates the whole story, so you are not asking for an OTP after eight minutes of detail.
- Use hold instead of silence. Placing the caller on hold for 40 seconds while you key the ticket is faster than narrating what you are typing, and it is measurable.
- Verify the consumer number, then route. The payment gateway desk can take the discrepancy ticket directly; you do not need to resolve it on this call. Transfers and tickets are the correct exit for anything needing back-office reconciliation.
- Cut the wrap, not the note. A two-line factual note written during the call saves the 60–90 seconds of after-call work that is usually inflating AHT.
- Escalate the conflict, do not absorb it. Tell the team leader plainly that the OTP step costs roughly 30–40 seconds and is non-negotiable; ask whether the AHT target for verification-failure calls should be different from the general target. That is a process decision, not an agent decision.
Reasoning: AHT is an average over call types. A compliance failure costs far more than 40 seconds - a privacy breach or a reopened ticket costs minutes of supervisor time and an audit mark.