How To Deal With Difficult Customers: IT Helpdesk Guide

Acknowledge what the problem has cost the customer, let them finish, and repeat the problem back. Then name your next step and the time of your next update, and keep it. Personal abuse gets one calm warning before you end the call. A threat of violence gets no warning.

Below: how to deal with difficult customers on the phone, by email, and in the ticket, with a phrase bank to download. It comes from the team behind SherpaDesk, a helpdesk and professional services automation (PSA) tool a small IT team can run alone.

Key takeaways

• Acknowledge before you troubleshoot. The Steps
• Promise an update time, not a fix time you don't know. Worked Example
• You own the update until someone accepts the handoff. Handoffs
• Frustration, abuse, and threats get different responses. When To End A Call

What Makes A Customer Difficult?

A difficult customer is someone whose emotion, demands, or behavior makes the conversation harder than the technical problem. Something they rely on has failed, sometimes not for the first time.

Often the anger is aimed at the failure: callers are "upset at the technology or the process or both - not at you," as one r/ITCareerQuestions member put it. Sometimes it is about you, such as a missed callback. Then it deserves a straight answer.

With difficult customers, respond to what they say and do. Five situations come up often.

What You Need Before The Next Hard Call

Decide how to handle difficult customers before the call, not during it. Set these up on a quiet day:

• A written rule for frustration, personal abuse, and threats: who may end a call, and who is told.
• A named person for decisions such as credits. If you're the owner and a technician, decide what you'll offer, and name an outside peer or vendor for technical help.
• Update intervals per priority, so "I'll update you" has a number. Our SLA Management Guide shows how to set them.
• The ticket open while you talk, and the phrase bank within reach.

How To Handle Difficult Customers, Step By Step

1. Pause and acknowledge

   Take one breath, then name what the problem costs them. Opening with a fix can sound like you skipped their point. CISA's de-escalation guide lists "Remain calm" first among its de-escalation actions.

   Example: "You've called twice and still can't run payroll. I'll read the ticket so you don't repeat it."

2. Let them finish

   Hold the fix until they've described the problem; an early fix can target the wrong symptom. Say "Go on" and take notes.

   Common mistake: transferring an angry caller before you understand the problem, so they tell it twice.

3. Repeat it back

   Summarize the problem in one sentence and ask if you got it right. CISA lists active listening among its de-escalation steps.

4. Ask what decides the next move

   What fails, since when, and what changed? Then two questions that set priority: who is stopped from working, and is there a workaround?

   Example: "Can the other two printers take the invoices until this one's back?"

5. Promise an update time, not a guessed fix time

   Say what you'll do next and when they'll hear from you. Give a fix time only when you know it, so you aren't explaining a missed deadline later.

   Example: "I don't have a restore time yet. I'll update you at 10:30 either way."

6. Apologize for the right thing

   Acknowledging harm isn't accepting blame. The Apology Section shows when and how.

7. Follow through and close the loop

   Update at the time you named, even with no news. Confirm the fix with the customer before closing.

   Common mistake: closing the ticket silently, so the customer reopens it to complain.

How To Deal With Difficult Customers On The Phone

CISA's guidance on calming a tense encounter lists four controls: tone and volume, word choice, rate of speech, and inflection. When the caller gets louder, try slower and quieter, so you don't match their pitch.

Identity checks. If a locked-out caller pushes you to skip verification, keep the check: "I know you're up against a deadline. I still have to verify you first." Our Helpdesk Best Practices cover the verification itself.

Dealing With Difficult Customers By Email And In The Ticket

A written reply to an angry message does three jobs: acknowledge the problem, answer the point in dispute, and set the next action.

Keep the tone of a calm call: a greeting, their name, no capitals for emphasis. Reply fast to the first message, even just to say who has it. Our Support Ticket Response Templates cover acknowledgment, delay, and closing messages.

When more email stops clarifying things, offer a call, unless the customer prefers writing. Afterward, record what you agreed in the ticket.

How To Apologize To A Customer, And When

Acknowledge the impact every time. Apologize when your side caused or worsened the problem: an outage, a missed update, a wrong fix. When the customer caused it, acknowledge the cost without taking the blame. Avoid "I'm sorry if you feel that way," which shifts the problem onto them.

A working apology has five parts:

1. Say sorry for the specific thing. "I'm sorry we missed your update at 2."
2. Own it. "That's on us." No "but."
3. Explain in one sentence. Not a defense.
4. Name their goal. The payroll run, the board meeting.
5. Give the next step and a time.

When The Facts Or The Scope Are Disputed

Show what the record says and offer the way forward: "Here's what the sign-in log shows. Let's try it this way."

• Work outside the agreement. Confirm scope before any work starts: "Your agreement covers the office network and laptops. Moving the phone system is a project. Dana, your approver, must accept the written scope and quote before we start."
• A billing dispute. Don't argue an invoice on a support call. Capture the invoice number, the disputed line, and the outcome they want. Hand it to whoever approves credits, and say when you'll update them.

When To Hand Off, Escalate, Or End The Call

Hand off when the issue requires skills or a decision you don't have. A minimal handoff names the impact, the checks done, the decision needed, and the next update time. You own the update until the recipient accepts. Our Escalation Matrix Template sets who takes what. If nobody sits above you, say plainly what you can offer and when you'll decide the rest.

Then tell three situations apart:

• Frustration, even loud, at the failure: keep working the steps.
• Personal abuse, such as insults, slurs, or swearing at you: give one calm warning.
• A threat of violence or any sign of danger: no warning. End the contact, tell your lead or owner, and get help.

I want to fix this. I can't continue if the language stays like this.

If the abuse continues, say you're ending the call and when they'll get an update, then hang up and log it. OSHA's definition of workplace violence includes threats, harassment, intimidation, and verbal abuse at the work site. CISA's advice: know your limits, get help, and if violence appears imminent, call 9-1-1.

When one client keeps abusing staff or refuses to meet basic support requirements, the owner reviews the relationship, with your ticket notes as the record. In an r/msp thread about owners who keep every customer, one reply called for "a bare minimum for supportability." Another, about a client who filed weekly slow Wi-Fi tickets but refused upgrades: "We fired a top 5 client for the wifi thing earlier this year."

One Hard Call, Start To Finish

Document It In The Ticket

When dealing with difficult customers, write the note within minutes. CISA's rule for reporting fits support notes too: give the facts of what was observed or heard, and avoid conjecture. A useful note covers five things:

• When it happened.
• What the customer said, in exact words for anything abusive.
• What you said.
• What you promised, and by when.
• Who you told.

Keep it in an internal note, without guesses about their mood.

After The Call: Follow Up, Reset, And Train The Team

Follow up. Ask "Did this fix it?" before closing, and record the answer.

Reset. After dealing with difficult customers back to back, take a short break when you can.

Train the team. Practice how to handle difficult customers in a ten-minute exercise:

• Scenario: the second outage this week, a frustrated caller, and no known restore time.
• Roles: one caller, one technician, one observer.
• The observer checks four things: acknowledgment, a clarifying summary, clear ownership, and a stated next-update time.
• Debrief: the observer names one thing done well, the kind worth praising on a real call. Pick one missed check and retry that exchange.

Share fixes in the knowledge base so customers can try them after hours; see our Knowledge Base Guide. Rotate calls with difficult customers among available technicians.

Phrase Bank: What To Say To Difficult Customers

Copy or download these lines to handle difficult customers. Revise them after each monthly ticket review.

DIFFICULT CUSTOMER PHRASE BANK
For IT support calls, emails, and tickets
Say the first line. Avoid the line marked "Not".

ACKNOWLEDGE (before you troubleshoot)
  "You've called twice and still can't [task]. I'll read the ticket so you don't repeat it."
  Not: "Calm down."

CLARIFY
  "Can I stop you for a second? Who can't work right now?"

NO FIX TIME YET
  "I don't have a restore time yet. I'll update you at [time] either way."

APOLOGY (our side caused or worsened it)
  "I'm sorry we missed the update at 2. That's on us."
  Not: "I'm sorry if you feel that way."

IDENTITY CHECK
  "I know you're up against a deadline. I still have to verify you first."
  Not: "Fine, I'll skip it this once."

OUT OF SCOPE
  "Your agreement covers [scope]. This is [work]. [Name], your approver, must accept the written scope and quote before we start."
  Not: "That's not my job."

HANDOFF
  Asked: "I've asked [Name] to take this. Until they confirm, it's mine, and I'll update you by [time]."
  Accepted: "[Name] has this now and will update you by [time]."
  Not: "Someone will call you."

PERSONAL ABUSE (one warning)
  "I want to fix this. I can't continue if the language stays like this."
  Then: "I'm ending this call now. I'll email you an update by [time]."

THREAT OF VIOLENCE (no warning)
  "I'm ending this call now." Tell your lead or owner. Call 9-1-1 if anyone is in danger.

How To Measure It Worked

Each month, review tickets with difficult customers: a complaint, an escalation, or an ended call. Tag them at close. Compare months with rates, because raw counts move with ticket volume.

Track two rates: updates kept ÷ updates promised, and the share of reviewed tickets reopened for the same problem within 14 days of closing. Calculate reopens only after the full 14-day window.

Give each change one owner and a review date. Fewer complaints alone don't prove success; customers may have stopped telling you.

Keep The Record On The Ticket

How this works in SherpaDesk

Tech Only notes, escalations, and the wait clock in one ticket

You can post a Tech Only response on the ticket that the customer never sees, or send one from your inbox with cmd techonly. A Wait (Tech) clock shows how long the user has been waiting for a technician's response, and it resets when any technician responds to the user. Levels & Escalations move the ticket through your tiers when it needs a lead.

A helpdesk and PSA a small IT team can run alone. No contract. No implementation project. No dedicated admin.

Base Camp is $45 per agent per month ($40 billed annually). The first agent is free, forever, so a team of three pays $90 a month ($80 billed annually). The trial is 14 days free with no card.

Ticket Management In SherpaDesk →

Frequently Asked Questions

How do you de-escalate an angry customer on the phone?

How do you respond to a complaint when the customer is wrong?

How do you deal with rude customers?

How do you answer "How do you handle difficult customers?" in an interview?

What if a customer refuses identity verification?