A 14-Character Order ID on a Bad Landline
You are on an inbound order-support line for an e-commerce fulfilment centre in Bhubaneswar. A 72-year-old caller with a hearing aid is on a landline with noticeable echo, asking why his order - a blood pressure monitor - has not arrived. He reads out a 14-character order ID in which letters and digits sound alike: B comes out like D, M like N, and zero like O. He speaks Odia mixed with Hindi, and becomes anxious when asked to repeat, saying, 'I have already told you three times.' The order was placed 9 days ago against a standard delivery of 3 to 5 days, and the CRM shows the shipment stuck at the Cuttack hub for 4 days. Your AHT target is 300 seconds and you have about 90 seconds left on the call. Whisper coaching notes that your pace is 190 words per minute, well above the 130 to 150 advised for clarity.
1. What do you do in the next 30 seconds to get the order ID right without frustrating him further?
Read the worked answer
Stop asking him to repeat the whole string. Repetition is what is making him anxious, and anxiety on a bad line makes the next attempt worse.
- Take it in segments. 'Sir, let us do it four characters at a time.' Short bursts survive echo better than a 14-character run.
- Use phonetic readback instead of open questions. Rather than 'was that B or D?', say 'I have B for Bombay - is that right?' A closed question needs one word, not a re-read.
- Give him the alternative he has not been offered. 'If it is easier, I can send an SMS to this number with a link that shows the order, or call you back on a clearer line.' An alternative path removes the pressure to perform.
- Change the channel if needed. Ask him to move the handset slightly away from the hearing aid to kill the feedback echo, and speak slightly slower rather than louder.
Reasoning: the goal is not to prove he said it correctly, it is to identify the order. Two independent identifiers - order ID and registered mobile or PIN code - let you confirm the record without a flawless transcription.
2. How do you adapt your voice and check that he has understood, without falling into yes-bias?
Read the worked answer
Voice adjustments, all of them deliberate:
- Drop from 190 to about 140 words per minute, and slow further when reading the order ID or the delivery date.
- Lower pitch slightly and increase volume marginally, not sharply; a raised voice on an echoing line sounds like shouting and distorts further.
- Pause for a full two seconds after each instruction, and keep one instruction per sentence. 'Your parcel is at Cuttack' then pause, then 'it will move today'.
- Switch fully to Odia rather than code-mixing, using the everyday words he used - parcel, hub, delivery date - and avoiding English process terms like 'in-transit' or 'escalated'.
Avoiding yes-bias. A hearing-impaired caller on a poor line will say 'haan, haan' to almost anything. Do not ask 'did you understand?' Ask him to say it back: 'Sir, just so I have it right, tell me what I have said will happen and by when.' If the teach-back is wrong or vague, re-explain once in different words rather than repeating the same sentence louder - the same words fail the same way twice.
Reasoning: confirmation from the customer is only evidence if he generated it himself. A mirrored 'yes' is not confirmation, it is politeness.
3. You have 90 seconds left. How do you close the call so accuracy is not sacrificed to the timer?
Read the worked answer
The shipment has been stuck at the Cuttack hub for 4 days against a 3-to-5-day promise, so he is already outside the delivery window and owes him a resolution, not just a status.
Close in this order:
- State the finding in one sentence: the parcel is at Cuttack and has not moved in four days.
- Raise the trace with the hub while he is on the line, and give him the ticket reference. That is 30 seconds and it is the part that matters.
- Give one commitment with a date: a callback or SMS update tomorrow by a stated time, and say what happens if the parcel is not traced - replacement dispatch, not another wait.
- Send the confirmation by SMS as well, because he will not retain a 14-character ID or a ticket number spoken on an echoing line.
On the timer: do not truncate the resolution to hit 300 seconds. A call closed at 290 seconds that generates a callback tomorrow has cost two calls, not one. Log the reason for overrun as 'hearing difficulty / poor line quality - extended verification' so the team leader sees a pattern rather than a slow agent. AHT is a diagnostic, not a target to be met by cutting the customer off.