Workplace Hebrew Register in a Customer-Service Role
A 24-year-old oleh from France has worked for eight months at a Israeli insurance call centre. Her Hebrew is fluent for everyday conversation but she learned mostly from friends and television. Her team leader notes three complaints in one month: a customer said she was 'too blunt' when refusing a claim; another said she 'sounded like a friend, not a company'; and a third asked to be transferred. Her written notes use slang abbreviations and emojis. The team leader must complete her probation review in ten days. The role requires explaining policy exclusions, refusing claims, and de-escalating angry callers, all in Hebrew. She handles 40 calls a day and resolves 85% at first contact, above the team average of 78%.
1. Diagnose the problem: is this a language-competence issue, a register issue, or both? Support your judgement with the evidence given.
Read the worked answer
It is primarily a register/sociolinguistic issue, with secondary written-formality problems - not a general competence deficit.
Evidence for register, not competence:
- 85% first-contact resolution (above the 78% team average) shows she understands policy and communicates outcomes effectively. A competence problem would depress resolution rates.
- The complaints are about tone, not accuracy. 'Too blunt' and 'like a friend' are evaluations of how she speaks, not what she said. She is likely transferring French directness and Hebrew slang learned from peers into a formal service context.
- The written notes (slang abbreviations, emojis) confirm she has not yet internalised the formal register expected in written customer records.
Evidence that some competence work remains:
- Refusing claims and explaining exclusions require specific formulaic Hebrew (e.g., softened refusal patterns, conditional phrasing) that conversational Hebrew does not supply.
So the review should treat this as register training, not remediation of Hebrew itself. Framing it as a competence failure would be inaccurate and demoralising.
2. Design a ten-day intervention plan that fits before the probation review, and state what the review should conclude if it succeeds or fails.
Read the worked answer
Days 1–2: Diagnosis. Team leader listens to five recorded calls (with consent) and marks where tone slips: refusals, empathy statements, closing. Identify two or three recurring patterns rather than a general 'be more polite' instruction.
Days 3–5: Modelling. Provide a one-page bank of Hebrew service formulas: softened refusal ('אני מבין/ה לאכזבתך, אך לצערי...'), empathy openers, and formal closing. Role-play three scenarios daily with the team leader: claim refusal, angry caller, policy exclusion.
Days 6–8: Live practice with feedback. She self-rates two calls a day against a three-item checklist (empathy opener, softened refusal, formal close). Team leader spot-checks two calls per day.
Days 9–10: Written register. Rewrite five of her own case notes in formal Hebrew; compare with a model note.
Review outcomes:
- If patterns improve: confirm probation, record the register issue as resolved with a 30-day follow-up check.
- If not: extend probation by 30 days with a specific, measurable target (e.g., no tone complaints in 20 sampled calls), rather than termination - her resolution rate is a strong asset worth developing.