Fifty-Five or Five Hundred Fifty? A Noisy Order on the Line
At 8:12 on a Tuesday morning, a candidate interning at a Tehran pastry distributor checks the shared voicemail. A regular client, Mr. Bāqeri, has left a 38-second message about a company event on Thursday. The line is bad: a motorcycle passes exactly as he gives the number, and the last syllable of the date is cut off. The candidate's transcription of what was heard: 'Salam, sobh be kheyr. Rāje' be sefāresh-e shirini: panjāh-o-panj tâ mikhām, na pansad-o-panjāh - panjāh-o-panj. Tārikh-e tahvil ham panjshanbe sobh na, chahārshanbe sobh, sā'at-e noh. Agar na, hamin fardā ham mishe, vali khob, shomā behtar midunid. Dastetun dard nakone.' The supplier's cutoff for next-day production is 9:00 a.m. The order form has two fields, quantity and delivery, and the supervisor reminds the candidate that Bāqeri disputed a charge of 550 last month because he had ordered 55. The candidate has 40 minutes.
1. Complete the two form fields (quantity and delivery) and explain which parts of the message you rely on and which you would still verify before 9:00.
Read the worked answer
Quantity: 55. The speaker produces the number, then marks a repair with «na» and contrasts it with «pansad-o-panjāh» (550), then repeats «panjāh-o-panj». In listening, a repair marker resets what came before; the post-repair token is the operative one. The motorcycle noise covers the first attempt, but the repetition after the repair gives a clean second token, so the quantity is recoverable.
Delivery: Wednesday at 09:00. There are two independent cues. First, the explicit repair «panjshanbe na, chahārshanbe» cancels Thursday. Second, «hamin fardā» - if the call is Tuesday morning - also points to Wednesday. A repair plus a deictic expression agreeing with it is strong evidence.
Still verify. Call or message the client with digits and an absolute date before the cutoff. Not because the message is unintelligible, but because the cost of a 55/550 error is high and this client has already disputed a similar charge. A written confirmation is cheap insurance; the candidate should not spend the 40 minutes re-listening instead of confirming.
2. Was «agar na, hamin fardā ham mishe» a genuine alternative date? How should the candidate treat it?
Read the worked answer
Treat it as a face-saving flexibility formula, not as an offer to move the delivery. Three reasons. First, «fardā» points to the same Wednesday already named, so it does not propose a different day. Second, «shomā behtar midunid» returns the decision to the listener, which is typical taarof rather than a transfer of scheduling authority. Third, the event is Thursday and the client has already fixed Wednesday 9:00, so a Thursday delivery would miss the purpose.
The real risk is the opposite: treating the courtesy as permission to deliver late. A good response acknowledges the courtesy and restates the concrete plan: «Sepās, hamun chahārshanbe sā'at-e 9 tahvil midahim.» Do not answer «har chi shomā befarmāyid»: in a work order that pushes the decision back and can read as evasive. Also note that «dastetun dard nakone» is a closing courtesy, not a request for anything.
3. Write the one-line confirmation in Persian and explain what it must lock down.
Read the worked answer
«سفارش: ۵۵ عدد شیرینی خشک، تحویل چهارشنبه ۱۹ اردیبهشت، ساعت ۹ صبح. لطفاً تأیید کنید.»
Why this wording:
- Digits, not words. «۵۵» cannot be misread as «۵۵۰» at a glance; written-out number words can be re-segmented under time pressure.
- Absolute date plus weekday. «چهارشنبه ۱۹ اردیبهشت» removes the relative «فردا», which depends on when the message is read.
- An explicit confirmation request. «لطفاً تأیید کنید» turns the message into a written record, which matters because of the earlier billing dispute.
The date 19 Ordibehesht must be taken from the calendar, not invented; if it is wrong, the confirmation defeats its purpose. The line stays short enough to send by SMS or WhatsApp.