Your biggest customer meeting starts in 20 minutes.
Tina is supposed to finish the project update, but Excel has crashed.
She logs a ticket with IT and waits for somebody to call her back.
Don’t worry, though.
It only affects one user, so it has been classed as a minor issue.
The service-level agreement allows eight hours for a response.
They should be in touch later.
Unfortunately, the meeting is in 20 minutes.

Minor to IT. Major to the Business.
To IT, it was one user with a minor problem.
To the business, it was an important meeting falling apart. The figures weren’t ready, and Tina was left explaining why the information everyone expected was missing.
Nobody did anything wrong by the rules. The ticket was logged, prioritised and answered within the agreement.
That’s exactly the problem.
How Most IT Support Prioritises Tickets
Most service-level agreements rank problems by how many people are affected:
- Whole company down: top priority
- A team or department affected: high priority
- One person affected: low priority, often hours for a response
On paper, that makes sense. In practice, it ignores the one thing that matters most.
What is that one person trying to do?
One person unable to use Excel might be preparing:
- A major customer presentation
- The month-end figures
- A tender submission with a 12 o’clock deadline
- Payroll
- Tomorrow’s production schedule
The technical problem might be minor. The business impact might not be.
Why a Ticket Number Can’t Explain the Problem
A ticket captures what is broken. It rarely captures why it matters right now.
A person can.
When your team can pick up the phone and speak to an engineer, they can explain in ten seconds what a ticket form would never ask: “I need this for a meeting in 20 minutes.”
That single sentence changes everything about how the problem is handled.
At Affirm IT, our average telephone answer time during 2026 has been 11.7 seconds. That means your team explains the problem to a person, rather than waiting for a ticket number to move through a queue.
What Good IT Support Looks Like
Fast answers matter, but they’re only part of it. Good support also means:
- Knowing your business: who does payroll, when month-end falls, which systems production can’t run without
- Judging impact, not just headcount: one person can be the most important person in the building that morning
- Being easy to reach: a phone answered by an engineer, not a voicemail or a portal
- Keeping you updated: so nobody has to chase
Questions to Ask Your Current IT Provider
- What is your average time to answer the phone?
- How many calls went to voicemail last month?
- How do you prioritise a problem that only affects one person?
- Who on your team knows how our business actually works?
If the answers are vague, that tells you something.
Frequently Asked Questions
What is an SLA in IT support?
A service-level agreement sets out how quickly your IT provider must respond to different types of problem. Response usually means acknowledging the issue, not fixing it.
Is a fast answer time more important than a fast fix?
Both matter. But you can’t fix a problem properly until someone understands it, and that starts with speaking to a person.
Need Help?
At Affirm IT, we start with simple questions:
- How quickly does your team reach someone who can help?
- Does your IT provider understand what each person does?
- Are urgent one-person problems being treated as minor?
From there, we put support in place that matches how your business actually works.
Not sure how your current support compares? Take our free 2-minute IT scorecard. Four questions, an instant result, and no email needed unless you want the breakdown.
Or get in touch with us. At Affirm IT, we provide IT support for manufacturers and managed IT support in Derbyshire and across the East Midlands.
