The 90-Second Target and the Wrong Pincode
At a 40-seat inbound BPO in Sector V, Salt Lake, new agents handle billing calls for a telecom client. The process sheet sets an average handling time (AHT) of 90 seconds and 60 calls per shift; quality audits five calls per agent per week, and a single data-entry error is logged as 'critical' if it changes a customer's address or plan. A trainee takes a call from a customer whose bill shows ₹1,240 instead of the expected ₹620. The CRM screen shows two accounts under the same phone number, one closed last month. The team leader signals 'wrap up' because the queue is at 14 minutes. Last week another agent, hurrying, keyed pincode 700091 as 700019, and the replacement SIM was couriered to the wrong address.
1. What should the trainee do on this call? Weigh the 90-second AHT target against resolving the bill, and give the concrete call flow.
Read the worked answer
Resolve the bill; the AHT is a target, not a rule. An unresolved billing dispute produces a repeat call, a possible complaint and rework - all of which raise total handle time and damage the quality score. Racing the timer to protect one metric usually costs two metrics.
Call flow:
- Greet and verify identity using the registered number plus one security question - not the caller's claim alone.
- Acknowledge the gap between ₹1,240 and ₹620.
- Check both accounts and establish which is active; the closed account is the likely source of arrears or a carried-forward amount.
- Explain the composition of the amount in plain language and state what is due.
- If the screen cannot explain the duplicate account, raise a ticket, give the reference number, and state a realistic timeline - do not guess.
- Summarise and confirm the customer has understood.
If the queue is the issue, ask the team leader for a short hold; that is a supervisor decision, not a reason to skip verification.
2. Analyse the pincode error as a process failure. Where should the organisation have caught it, and why is 'be more careful' not a control?
Read the worked answer
This is a process failure, not a careless-agent story. One transposition (700091 → 700019) survived three checkpoints: entry, dispatch and audit.
Missing controls:
- Field validation: a pincode field checked against a master list would have rejected 700019 as inconsistent with the entered city/state.
- Read-back: confirming '700091, Salt Lake?' with the customer catches transpositions in seconds.
- Maker–checker: address changes are high-risk and deserve a second pair of eyes before dispatch.
- Sampling design: five audited calls per agent per week gives a low-probability error a low chance of being caught; critical fields need 100% validation, not sampling.
Why not 'be careful': vigilance is not measurable, not auditable and not repeatable. Blame also pushes errors underground, so near-misses stop being reported. The durable fix is the field plus the read-back, with logging of every correction.
3. Write two sentences the trainee could use - one showing empathy and ownership, one stating when the call must be escalated.
Read the worked answer
Empathy and ownership: "I can see why a bill of ₹1,240 when you expected ₹620 is worrying - let me check both accounts and explain exactly what makes up this amount, and I'll stay with you until it is clear."
This works because it names the customer's concern, commits to an action, and does not blame the system or the previous agent.
Escalation: escalate to a supervisor when the customer asks for the account to be closed, a refund or a waiver beyond the agent's limit; when the duplicate account cannot be explained from the screen; when unauthorised charges or identity misuse is reported; or when the customer becomes abusive and a supervisor is required for safety.
Escalate warmly - introduce the supervisor, hand over the ticket number and a one-line summary, so the customer does not have to repeat the story. A cold hand-off undoes the empathy built in the first sentence.