Staying Professional Under Fire From a Frustrated User

Thursday, 06:40, at Bellweather Logistics. Jonah has had four hours' sleep because his daughter was up with a temperature. He is first on the desk, and the first call is Karl from dispatch, whose scanner gateway has dropped for the third morning in a row. Karl does not say hello. "What do you people actually do all day? Three mornings. Three. I've got drivers sitting in the yard on the clock and I'm the one who gets it in the neck, not you." Jonah knows the gateway is a vendor fault and knows a replacement unit is on order. He knows exactly what he wants to say, which begins with "Well, if your lot would stop unplugging it to charge your phones." He has about half a second before the sentence leaves. This article is about that half a second.

Staying professional means keeping your words and your tone the same as they would be on a good day with a calm requester, while somebody is doing their best to change them. It does not mean having no reaction; the reaction is automatic and not your fault. It means not sending it. This article is part of our Working With Frustrated Users series. It is the one about you rather than the requester. It covers what happens inside the technician when the heat arrives, and the small set of habits that keep the heat from coming back out. The manager's role, what the desk does about a person who does this every week, and the boundaries a desk sets in writing all belong to a later series. This article stays inside the moment.

It covers why the reaction is normal and sending it is optional, then the pause before you reply, on the phone and in writing. Next come why written fire is a different thing from spoken fire, and when and how to hand the ticket to a colleague. Then come the line between anger and abuse, what the desk does at that line, and the reset after the call. A short war story and the personal reset checklist to copy finish the article, in that order.

The Reaction Is Normal; Sending It Is Optional

Being shouted at produces a physical response before any thought does. There is a faster pulse, a tightening in the chest, heat in the face, and a sentence, already formed, that would win the argument. This happens to everyone who has ever answered a desk phone, and it is not a professional failing. It is what a body does when attacked. The failing, where there is one, is in what happens next. The only thing you control in the half-second is whether the sentence that has formed goes out of your mouth or stays behind your teeth. That is the whole skill. It is not complicated. It is just hard.

The sentence that forms is nearly always a defence or a counter-attack, and both make things worse for reasons the previous articles cover. The requester did not call to assign blame, and answering the blame tells them the desk has stopped listening. But there is a second cost that is specific to this article. A technician who sends the sentence has now made the interaction about themselves. Karl was angry about three mornings of drivers on the clock. If Jonah says the thing about the phones, Karl is angry about Jonah. That anger has a name and a face and will be mentioned to Karl's manager by lunchtime. The sentence converts a problem with a gateway into a problem with a person, and problems with people take longer to fix than gateways.

It helps to know that the anger is not aimed where it lands. The first article in this series, Why Users Get Angry at the Help Desk, is about why that is so. The short version is that the desk is the only part of the organisation's technology with a phone number. Karl is shouting at the gateway, the vendor, the two previous mornings and the drivers' clock. Jonah is the address, not the target. Knowing that does not stop the pulse. But it does change what the pulse means, from "I am being attacked" to "something is being delivered to me". A delivery can be signed for without being agreed with.

The Pause Before You Reply

The pause is the half-second made deliberate, and on the phone it has a shape. Breathe out, not in. Say a neutral sentence that buys time and costs nothing: "Right. Go on." or "I'm listening." Let them finish, which takes longer than you think and is not optional. Then say the acknowledgment from the first sixty seconds, in their words, and nothing else: "Three mornings, drivers on the clock, and you're the one taking it. I can see that." By the time that sentence is out, the sentence about the phones has lost its moment, and the moment is the only thing it ever had. Most retorts cannot survive a four-second delay. They are built for the instant, and the instant passes.

On the phone the pause is seconds; in writing it is minutes, and you should take all of them. Read the angry message once, and then do not reply. Open the ticket, write the internal note about the impact and what you know, and do the first practical thing, whatever it is. Then come back and draft the reply. Then read it once as the requester, and once as the requester's manager, because they will. Then delete the first sentence, which is nearly always the one that was still a little bit angry, and send what remains. The draft folder is the most professional object on the desk, and it is used far too rarely.

The hardest pause is the one after you have already said something you should not have. It happens. The move is to stop, not to recover with more words. "Sorry, that was unfair, let me start again. You've had three mornings of this." A requester who hears a technician catch themselves mid-sentence and reset usually gives them the restart, because it is rare and because it is honest. What they will not give is credit for a sentence that was sent and then explained. I have tried explaining one. The explanation was longer than the sentence and did more damage.

Written Fire Is Different From Spoken Fire

A spoken retort lives for as long as the call. A written one lives forever, is forwarded, and is read at a meeting you are not in. This changes the arithmetic completely. On the phone, a slip can be caught and reset in the same breath. In a ticket reply, the slip has a timestamp and your name. It sits in the ticket's history above every good thing you do afterwards. The requester can quote it, in full, to anyone, for years. Written fire therefore gets a longer pause, a stricter read-through, and a rule. Never reply to an angry message in the same sitting that you read it, unless the reply is only an acknowledgment and a time.

The internal note needs the same discipline as the reply, which surprises people. Technicians treat the note as a private channel, and write things in it about the requester that they would never put in the public reply. Examples are "user being a nightmare again" and "see previous three tickets, same drama". If you run QuerySolv, an internal note is visible to the team and not to the requester. That is the right place for the handoff context and the three suspects. It is still a permanent part of the ticket's history, and ticket histories get exported, audited, and read aloud in grievance meetings. Write every note as if the requester will read it one day, because the organisation may decide that they can. What belongs in a ticket and what never does is the subject of What Not to Write in a Ticket. The short version is: facts, times, actions, and nothing about anybody's character.

Written fire also arrives with an audience already attached. The angry e-mail is copied to the requester's manager, or yours, or both, and the instinct is to reply to all with a defence for the audience's benefit. Do not. Reply to the requester, in the six lines the acknowledgment article describes, with the impact, the honest position on the cause, the next step and a time. Keep the managers in the copy line if they were there, because removing them looks like hiding, and let them read a calm reply. A calm reply read by a manager is the best thing that can happen to a technician's reputation that week. A sharp one is the worst, and it is the same keystroke.

Handing the Ticket to a Colleague

Sometimes the pause is not enough, and the professional move is to hand the conversation to somebody who is not the target. This is not failure. It is the correct use of having colleagues, and desks with one person feel the lack of it acutely; the FAQ below has the solo version. Hand off when you notice you have stopped listening and started waiting for your turn. Hand off when the requester has made it about you personally and nothing you say will change that. Do it when you have a history with this requester that the colleague does not. Or do it when you are simply out of calm, which happens on four hours' sleep and is nothing to be ashamed of.

The handoff has to be done so that it helps the requester rather than looking like an escape. On the phone: "I'm going to bring in my colleague Priya on this; she's dealt with the gateway before and she can pick it up right now. Stay on the line." Then, before Priya picks up, thirty seconds of context: the impact, the rung, what has been said, what has been promised. In writing, leave an internal note with the same four things. Then the colleague claims the ticket so that the requester sees a new name on the next reply. That reply opens with the acknowledgment again, in the colleague's own words, not "as my colleague said". The requester should feel that a second person has arrived, not that the first one has left. How to transfer a ticket so that nothing is lost in the move is covered in Transferring a Ticket Between People or Departments. The hot handoff is the same mechanics done faster and with more care about the first sentence.

Make the handoff a thing the desk does openly, in both directions. A technician who hands off a hot ticket should be able to say this in the team chat: "I've handed Karl to Priya, I was too tired to do it well". Nobody should think less of them. And a technician who receives one should expect to hand one back next month. Desks where handing off is seen as weakness get technicians who stay on calls past the point of being useful. The calls end badly, and the technicians go home carrying them. The desk that normalises the handoff gets fewer complaints and keeps its people longer. Both of those are numbers somebody will eventually ask about.

The Line Between Anger and Abuse

Anger is heat about the problem, the desk, or the history, and the desk absorbs it as part of the job. Examples are shouting about three mornings of outage, swearing about the gateway, "what do you people do all day", capitals in an e-mail, a manager copied in. None of that is abuse, however unpleasant. It is a person under pressure directing the pressure at the one place that answers. Abuse is when the heat stops being about the situation and becomes an attack on you as a person. It includes insults about your intelligence, your competence as a human being rather than as a desk, your accent, your gender, your background. It includes threats, of any kind; slurs; or a sustained personal attack that continues after you have calmly named it. The test is the subject of the sentence. "This desk is useless" is anger. "You are a useless idiot" is on the line. Anything with a slur or a threat in it is over the line, in one sentence, with no warning needed.

The line is worth drawing in advance because in the moment it is hard to see. A technician who has just been told they are an idiot is not in a good position to judge whether that counts. So the desk writes the line down, before anyone needs it, in plain words the whole team has agreed. It says what the desk absorbs, what it names once, and what ends the conversation immediately. Then the technician on the call is not deciding whether they are being too sensitive. They are applying a rule that was agreed on a calm Tuesday by people who were not being shouted at. Rules made in advance are the only kind that work at 06:40.

Swearing deserves a specific note, because it is where most desks get the line wrong in both directions. Swearing about the situation ("this bloody gateway", "it's a complete mess") is anger and is absorbed. Swearing directed at the technician ("you're a waste of space") is personal and is named. Volume alone is never abuse; some people are loud when they are frightened of losing their job over a scanner, and loud is not the same as attacking. The desk that ends calls for volume will end calls with people who needed help most. The desk that absorbs personal attacks because "they were just upset" will lose its technicians. The line is about the target of the words, not their volume or their vocabulary.

What the Desk Does at the Line

At the line, the technician says one calm sentence that names it and says what happens if it continues. "I'm going to keep helping with the gateway, and I'm not going to be spoken to like that. If it carries on I'll end the call and continue this by e-mail." Said once, level, with no anger in it and no apology either. Most people stop, and many apologise, because they heard themselves. The sentence is not a threat. It is a description of what will happen, and it is said in the same tone as "I'll be with you in ten minutes".

If it continues, the technician ends the conversation, politely, and keeps the promise about the work. "I'm ending the call now. I'll e-mail you within the hour with where the gateway fix is." Then they do exactly that: the work continues in writing, as if the call had gone well. It has the same acknowledgment of impact, the same honest position on the cause, the same next step and time. The ticket does not get slower because the requester crossed the line. That matters, because the point of ending the call is to protect the technician, not to punish the requester. A fix that is delayed in retaliation makes the desk the problem. For a threat or a slur, the same sentence without the warning: "I'm ending this call now. The ticket will continue by e-mail." No discussion.

Immediately afterwards, two things, both short. The technician writes a note on the ticket that records what was said, as factually as a log. It has the time, the words as close to verbatim as memory allows, the warning given, the call ended, the e-mail sent. No adjectives, no "user was abusive". The words themselves do the work when a manager reads them, and "abusive" is a conclusion for the manager to reach. Then the technician tells their lead, that day, in a sentence. What the lead does with it, whether the requester's own manager is told, and what happens when the same person does it again are decisions above the technician's desk. They belong to the later series on boundaries. The technician's job at the line is the sentence, the ending, the note and the telling. Nothing more is theirs to carry.

After the Call

When a hard call ends, the body is still running at call speed. The next ticket in the queue gets whatever is left of it unless something is done first. Stand up. Get water. Walk to a window if there is one. Two minutes is enough, and the two minutes are not slacking. They are the cost of the previous call, paid now rather than charged to the next requester. That requester has done nothing to deserve a technician still shaking from Karl. Then write the note on the ticket, factually, while the words are fresh. Put the time you promised in it so that whoever picks it up next can keep your promise if you cannot.

Then say it to someone. "That was a rough one." Thirty seconds with a colleague, out loud or in the team chat, is the difference between a call that is over and a call that is carried home. The colleague does not need to fix anything or agree with everything; they need to have heard it. Desks that do this as a habit have technicians who last. Desks where everyone absorbs their calls alone, because talking about it looks like weakness, have technicians who are fine for a year and then are not. The thirty seconds is cheaper than the recruitment.

The last part of the reset is to put the call where it belongs, which is in the ticket and the monthly review, and not in your opinion of yourself. A hard call is information about a gateway that has failed three mornings, a vendor replacement that is late, and a dispatcher under pressure from drivers. It is not information about whether you are good at this job. The desk that reads its angry tickets together once a month, looking for the system behind them, is the desk that stops its technicians taking each one personally. That review is the subject of What Angry Tickets Teach the Desk. The reset is complete when the call has become a line on that sheet and nothing else.

A Short War Story: The Reply That Reached the Partner at Greyfield Legal

Imogen had been on the desk at Greyfield Legal for a year when a partner's assistant e-mailed, in capitals. The message said a client's bundle had vanished from the document system two hours before a hearing. It also said "IT has clearly lost it again". Imogen had restored the same assistant's misfiled documents three times that quarter and was tired of it. She replied inside four minutes with the restore instructions. Her first line read "Perhaps if the documents were saved in the right folder in the first place this would happen less often." The documents were back in nine minutes, which nobody remembered, because the assistant forwarded the reply to the partner. The partner forwarded it to the managing partner with the subject line "Is this how IT speaks to us?" The sentence was read aloud at a partners' meeting the following week. Imogen received a formal note on her file. The desk spent a month with every reply being reviewed by the IT manager before it was sent. The assistant, who had in fact been saving to the wrong folder, never raised another ticket and asked a colleague instead for the rest of the year. The restore had been perfect and the first sentence cost more than every outage that quarter. Imogen now drafts every reply to a message in capitals, does something else for ten minutes, and deletes the first line before sending. She says the first line has not once been needed.

The Personal Reset Checklist

The checklist below is for the technician, not the ticket. Keep it somewhere you can see it without the requester seeing it: a card by the phone, a note on the second monitor, a page in the drawer. The first block is for the half-second and the pause; the second is for the line; the third is for afterwards. It is deliberately short, because nobody reads a long checklist while being shouted at. The whole of it should also become habit within a month, at which point the card is for the next new person.

PERSONAL RESET CHECKLIST — UNDER FIRE

IN THE MOMENT (phone or chat)
  [ ] Breathe out. Say a neutral sentence: "Right. Go on."
  [ ] Let them finish. Count the gap to four before speaking.
  [ ] Acknowledge the impact in their words. Nothing about fault. Nothing about me.
  [ ] The sentence that formed in my head: not sent.
  [ ] If I said something I should not have: stop, "that was unfair, let me start again."

IN WRITING
  [ ] Read it once. Do not reply.
  [ ] Internal note first: impact, what I know, what I am checking.
  [ ] Do the first practical thing.
  [ ] Draft. Read as the requester. Read as their manager.
  [ ] Delete my first sentence. Send the rest. Six lines or fewer.
  [ ] Nothing in the note I would not want read aloud.

HAND OFF WHEN
  [ ] I have stopped listening and started waiting to speak.
  [ ] It has become about me personally and will not move.
  [ ] I have history with this requester that a colleague does not.
  [ ] I am out of calm today.
  How: name the colleague, say they can pick it up now, thirty seconds of context,
       colleague takes the ticket in their own name and opens with the acknowledgment.

AT THE LINE
  Anger (about the problem, the desk, the history; swearing about the situation): absorb it.
  On the line (insults about me as a person): one calm sentence, once:
     "I'll keep helping with ______, and I won't be spoken to like that.
      If it continues I'll end the call and carry on by e-mail."
  Abuse (slur, threat, or it continues after the sentence): end it, politely, now:
     "I'm ending the call. I'll e-mail you within the hour with where the fix is."
  [ ] Keep the promise. The ticket does not slow down.
  [ ] Factual note on the ticket: time, words as said, warning given, call ended, e-mail sent.
  [ ] Tell my lead today, in one sentence.

AFTERWARDS
  [ ] Stand up. Water. Two minutes before the next ticket.
  [ ] Note on the ticket with the time I promised, so someone else can keep it.
  [ ] Say "that was a rough one" to a colleague. Thirty seconds.
  [ ] This call is information about a system, not about me.

Jonah did not say the thing about the phones. He breathed out and said "Right, go on," and Karl went on for another forty seconds. Then Jonah said "Three mornings, drivers on the clock, and you're the one getting it. I can see that. I'm going to get the gateway back up now the way I did yesterday, which takes about four minutes. Then I'm going to tell you exactly where the replacement unit is, because you should know." Karl said "Fine," which from Karl at 06:40 is warm. The gateway came back at 06:47, and the replacement arrived the next Tuesday. The sentence about the phones stayed where it was, which is where all the best sentences in this job end up.

Frequently Asked Questions