How Tech Teams Handle Angry Stakeholders Without Making It Worse: The ACER Framework
Frankie Kemp
19 October 2026
The service desk team at an international charity had a pattern. An incident would arrive, and there could be three common responses: silence, blame, or “That shouldn’t have happened.”
But it did. That’s rather why it’s an incident.
Your “shouldn’t have”, whether it’s aimed at the glitch or at what the user did, is about as welcome as a tiger at a tea party.
Then there were the instructions. Jargon, or knotted step-by-step directions that left users either baffled or risking their necks. One call had an internal client, crawling behind their desk, trying to locate a socket.
If your client – a term I’m using for internal and external stakeholders – hasn’t already electrocuted themselves, they’re definitely ready to turn the heat up on the tech consultant.
At this point, the Head of Data, responsible for this particular team has her hands up in despair. A problem that a little empathy, a little clarity and a solution would have sorted was now plonked itself on her desk.
So if you’re on a service desk and feeling helpless or frustrated, or you’ve had enough of your team rolling issues in your direction, meet ACER: turning communication alchemy in dealing with tricky help desk situations into a concrete guide.
ACER is a four-step de-escalation framework for Tech teams dealing with frustrated stakeholders, customers or suppliers:
1. Acknowledge the problem,
2.Clarify the facts,
3. Ease the pain with a workaround, then
4. Return with a time.
It stops a tense conversation becoming an escalation, and it does it without you promising anything you can’t deliver. Your future self will be grateful.
Why Tech teams can end up annoying stakeholders
People know tech runs into problems. But it’s the response of support which determines how disruptive this feels and how much damage it leaves.
The charity’s service desk wasn’t unusual. A stakeholder who is stressed, late or being chased by their own boss doesn’t hear an explanation, whatever you say. They hear one of three things:
- Defensive: “That’s out of scope.” (Translation: not my problem.)
- Vague: “We’re looking into it.” (Translation: no idea, no date.)
- Jargon: a perfectly accurate answer in language they can’t follow. (Translation: you’re not worth explaining this to or “wlrhgrhosix”.)
Each one raises the temperature.
ACER replaces all three with a sequence you can run on a call, in a chat window or in an email.
Before and after: the same problem, two replies
Imagine a Finance Director locked out of a system on the morning of a deadline.
Typical Tech reply:
“The account locks after three attempts. That’s policy. Raise a ticket and it’ll be picked up in the queue.”
Technically right. Practically, it’s a flat refusal with a side order of “not my job”, and a ticket number as a parting gift.
ACER reply:
- Acknowledge: “I can see this has been frustrating.”
- Clarify: “The system locks after three attempts to protect your data.”
- Ease: “For now, let’s reset it from my side. It takes 30 seconds.”
- Return: “I’ll come back to you by 3pm with an update.”
More understanding, an explanation, a way out and a reassurance – in four short phrases. Completely different conversation.
The ACER framework: breaking it down
A: Acknowledge
Purpose: drop the emotional temperature and show you’ve heard them, before you say anything else.
Recognise both what they’re trying to achieve and how the problem feels. Use:
“I can hear how important this is.”
“Okay, I see why this is causing pressure.”
“I understand why you need this sorted quickly.”
Acknowledge doesn’t mean agree. And it definitely doesn’t include ‘but’.
I was working with a service desk team at the international charity, I mentioned above. I beamed a live actor onto their giant screen through Teams to play a customer who was, to put it politely, absolutely livid. Not “mildly disappointed”. Livid.
Simon (not his real name) opened with: “While I appreciate you’re frustrated…”
You could see the customer go red through the screen. Quite a feat, for a Teams call.
In feedback, Simon was adamant he’d acknowledged them. He had. Technically. But “while” is just “but” in a smarter jacket. The customer hears the empathy being cancelled and the excuse approaching.
You don’t have to agree with them. You do need to show you can see it from where they’re standing, keeping your ‘but’ out.
C: Clarify
Purpose: give the facts and the boundaries, without sounding like “not my job”.
This is the step Tech teams find hardest. The reason might include the SLA [Service Level Agreement] security, process, capacity. These are real but it’s theway you deliver these limitations that can frustrate others.
Firstly, keep it fact-led and evidence-led, and frame it as what is, not what you can’t be bothered with:
“Here’s what’s inside the SLA, and here’s what sits outside it.”
“This part is yours, but I’ll help you map the next steps.”
“We can move this forward if we bring your internal team into the loop.”
Give one reason, not five. Mountain Goat Software, founded by Mike Cohn of Scrum Alliance, makes the point well in this guide to saying no to a stakeholder: when you offer a list, people attack the weakest reason and the conversation becomes about that instead of the real issue. Pick your strongest fact and stop.
Then there’s jargon. Explain it like a neighbour, not a technician. “It’s basically a locked door and we’re finding the right key” beats a paragraph of acronyms. Nobody has ever calmed down on hearing “it’s a DNS thing”.
“How do I know if what I’m saying is jargon?”
You don’t. Words you use eight times a day have stopped sounding technical to you. That’s rather the problem.
So give them an exit before they need one. Early in the call, say:
“If I use a word that doesn’t make sense, stop me. Many do.”
Then, when they do stop you, explain, check understanding and move on. Avoid: “Does that make sense?”. People can feel stupid saying it doesn’t whereas a statement such as “Tell me if I’m getting too techy” puts the problem with you, and lets them keep their dignity.
A few more habits that help:
- Test your phrases on a non-technical friend or colleague before you need them live. Anything that gets a blank look goes in the bin.
- Avoid acronyms, or explain them. Never let them stand alone. “MFA” means nothing to most people. “The second check when you log in” does.
- Reach for an everyday comparison. “A digital home address” does more for most people than “IP address”. Need an analogy? Here’s how to find one.
E: Ease
Purpose: give immediate relief and momentum. Go from “It’s stuck. Here’s why”, to “This is what we can do”.
This is the workaround: stabilise first, solve the root cause second.
“For now, let’s reset this on my side. It takes 30 seconds.”
“Here’s the quickest next step.”
“Let’s get you stable, then we’ll look at the root cause.”
“Here’s what we can do today.”
If you can’t give them what they asked for, this is where you give them a route to something close. That’s where “Yes, if” comes in (see below).
How to say no without saying no: “Yes, if”
You can’t always promise an outcome. But you can almost always offer a pathway. Instead of a flat “no”, use a conditional “yes” in your Ease step:
“Yes, we can do that, if we adjust the timeline.”
“Yes, we can fix this, if you can give me access.”
“We can get this moving, if you can send me the file.”
It keeps momentum, makes the boundary clear and invites the other person to meet you halfway, which turns resistance into partnership. I go further into the principle in how to say ‘no’ to your managers. A follow-up post will cover more scripts for IT teams.
R: Return
Purpose: commit to a specific point where you’ll come back, so they’re not left wondering in limbo. Vague reassurance (“we’ll get back to you soon”) leaves uncertainty and a risk of the client hounding you. Name a time and keep to it:
“I’ll come back to you by 3pm with an update.”
“I want to give you the right answer. Let me check and come back by 10am tomorrow.”
“I’ll return with options, not just a yes or no.”
The commitment itself does the de-escalating. It tells them someone owns this, which in some organisations counts as a minor miracle.
Have your ACER at hand
Here it is: ready to save or print:
What not to do
- Don’t say “calm down”. It’s the fastest way to make someone angrier. Nobody in recorded history has calmed down on being told to. Let them vent, then move to Clarify.
- Don’t follow your acknowledgement with “while” or “but”. It cancels the empathy before it has landed. (Simon’s story is above, in case you skipped it.)
- Don’t ask “why did you…?” “Why” tends to sound like blame and sets off defensiveness. Ask “What happened?” or “What have you already tried?” instead. Here’s more on avoiding that word.
- Don’t say “you shouldn’t have…”. You can’t change the past (unless Tech has a time machine nobody’s mentioned), and it only annoys people. Look forward instead: “What would you do differently next time?”
- Don’t shout back, even a little. Matching their volume and speed spreads the tension. Keep your tone calm and your pace steady.
- Don’t hide behind jargon or ticket numbers. A ticket number is not an apology.
Making ACER work: the small signals
The words only work if the delivery backs them up. A soothing script delivered through gritted teeth is still gritted teeth.
- Voice: match their energy calmly, but don’t mirror shouting.
- Eye contact: soft and unsustained. It signals empathy without dominance.
- Distance: adjust your angle or space so you’re not squaring up face to face.
- Validate: repeat back what they’ve said without agreeing to it. “So the report didn’t run and you’ve got a meeting at 11. Is that right?” Then check you’ve understood.
For more on listening and rapport, see what a hostage negotiator taught me about rapport and what active listening really means.
FAQ
What if they’re still angry after I’ve acknowledged it?
Don’t skip ahead. Let them keep talking, stay calm, then reflect back what you’ve heard and check it: “So it’s X. Is that right?” Once the heat drops, move to Clarify.
What if I don’t know the answer yet?
Use Return. Say so honestly and name a time: “I want to give you the right answer, so let me check and come back by 10am tomorrow.” Honest and specific beats confident and wrong.
What if the answer is genuinely no?
Acknowledge, give one clear reason, then offer the nearest alternative you can. If it really is a never, say so clearly rather than leaving the door open.
Is ACER only for service desk and support teams?
No. It works anywhere a stressed person is relying on your expertise: project updates, supplier chasing, change requests, internal stakeholders and colleagues.
Can I use ACER in email?
Yes. The order is the same. Open with the acknowledgement rather than the policy, give one reason, offer the workaround and end with a specific time.
Putting ACER into practice:
- Pick one live situation this week, such as a chasing stakeholder or a ticket that’s about to escalate,
- Run through A, C, E and R before you reply.
- Write down what you’d say for each step first. It takes a minute and changes the tone of the whole exchange.
Want more tools like this? Join my free Tips ‘n’ Tools list and become a Communication Ninja. If you’d like your IT team trained on this, take a look at my communication skills training for technical teams or get in touch. And that bit about beaming in actors for that extra touch of reality? That’s possible for you too.


Leave a Reply