When did you last have a conversation with your IT support provider that wasn’t about a ticket, an invoice or a contract renewal?
Those conversations are necessary, but they don't tell you whether you are getting everything you need from the relationship. Good IT support should resolve day-to-day problems effectively. It should also help you understand what is happening across your technology environment, address recurring issues and make informed decisions about how you mitigate risk, innovate and align technology with business objectives.
The questions below aren't designed to catch your provider out. Nor does an uncertain answer automatically mean you need to replace them. They’re intended to open a more useful conversation about the service you receive and how it could develop.
Your IT provider should understand more than your systems, devices and user numbers. They should be developing a clearer picture of how your organisation operates, which services matter most and where technology is helping or hindering your people.
During the past year, your organisation may have grown, changed direction, introduced new working practices or faced different pressures. Your provider should be aware of the changes that affect your technology needs.
A useful answer might include observations about how teams work, where users experience difficulty or how your priorities are evolving. It should demonstrate that your provider is listening and learning, rather than delivering the same service regardless of what changes around it.
If the question is difficult to answer, it may suggest that the relationship is focused more on individual transactions than on understanding your organisation.
Every service desk deals with repeated incidents. What matters is whether those incidents are being recognised as a pattern.
Your provider should be able to identify the issues that appear regularly and explain what may be causing them. Some will be unavoidable such as password resets and therefore won’t justify further action. Others may point to a configuration problem, an ageing system, a difficult process or a gap in user knowledge.
Resolving the immediate ticket is important, but a recurring problem deserves a wider conversation. Ask your provider which issues are creating the most repeated disruption and what would be required to address their underlying causes.
The answer should help you distinguish between unavoidable support activity and problems that could potentially be reduced or prevented.
All organisations have some technology risks. The important thing is to understand them and make proportionate decisions. Your provider should be able to explain the most significant risks they see, why those risks matter and how urgently they need attention.
The discussion should extend beyond a long list of technical findings and not be siloed into a “cyber security” service conversion. Risk management and cyber security strategies should be considered across the whole technology environment and aligned with the organisation’s wider priorities, operations and appetite for risk.
You need enough context to make a decision:
A good provider shouldn’t use uncertainty or fear to create urgency. They should help you prioritise risks based on their potential effect on the organisation. They should also be honest about what they don’t yet know and where further investigation may be necessary.
Organisations often have technology that is underused. This can happen when licences accumulate, features are introduced without enough guidance or systems no longer match the way people work. In other cases, users may create workarounds because the available tools feel difficult or unsuitable.
The answer isn’t always to remove a service or purchase something different.
Sometimes the organisation needs better configuration, clearer processes, training or help with adoption. There may also be an opportunity to simplify the environment by removing unnecessary duplication.
Your IT provider should help you understand whether you are receiving meaningful value from the technology you already have. Recommendations should be based on how people work and what the organisation needs, rather than on selling another product.
Most organisations could identify a long list of possible technology improvements. Few have unlimited time, budget or internal capacity to deliver them.
Your provider should help you decide what matters most. For each recommendation, they should be able to explain:
You should come away with a sensible order of priority rather than an unstructured list of desirable changes.
The right recommendation isn’t always the largest project or newest technology. It may be a small improvement that removes a common frustration, reduces a meaningful risk or makes an existing service more reliable.
Technology services are often sold as separate capabilities, but users experience them as one environment.
A problem accessing an application, for example, could involve a device, identity, permissions, connectivity, security controls or the application itself. A planned change in one area may create dependencies or consequences elsewhere.
Your IT provider should understand these dependencies and consider how well different technologies interoperate. When an issue crosses service boundaries, they should bring together the right people rather than expecting you to coordinate each technical team or supplier.
This question can reveal whether your provider sees the whole environment or only the individual service they are contracted to manage. Joined-up thinking is especially important when planning change. Decisions made in isolation can create avoidable complexity, gaps in responsibility or a poor experience for users.
Technology should support change rather than become an obstacle to it.
If your organisation is recruiting in volume, opening locations, introducing services or changing the way teams work, your provider should be involved early enough to help you prepare.
They should be asking questions such as:
Your provider doesn’t need to be part of every business decision. But they should understand the plans that may affect your technology environment and help identify what needs to happen before the change takes place.
If they only become involved when users start encountering problems, the opportunity to plan properly may already have passed.
A technology roadmap should provide direction, not simply list renewal dates.
It should bring together the changes your organisation is planning, the risks that need attention and the improvements that will provide the most value. It doesn’t need to predict every requirement. Priorities will change, and any plan should be reviewed as the organisation evolves.
However, it should give you a clearer view of:
Your provider should be able to explain how their recommendations fit into your plan and what business outcomes they can deliver.
Without a roadmap, decisions are more likely to be driven by urgent problems, renewal deadlines or individual product opportunities. A shared plan allows you to make choices in a more considered way.
Ticket numbers, response performance and system availability are useful measures. They help you understand whether the support service is meeting SLAs.
But they don't necessarily show whether your technology environment is improving.
Ask your provider how they measure outcomes such as:
Not every improvement can be reduced to a single metric. Context and customer feedback matter too. The purpose of this question is to move the conversation from how much activity took place to what difference that activity made.
A report showing that hundreds of tickets were closed may look positive. A more useful discussion asks why those tickets were needed and whether some could be prevented in future.
This may be the most revealing question of all.
A proactive provider should sometimes raise topics before you ask about them. They should be able to share observations from your support activity, highlight changes in the wider technology environment and identify matters that deserve consideration.
That might include an emerging risk, a recurring source of frustration, an underused capability or a future decision that requires preparation.
The answer doesn’t need to lead to an immediate project. A good provider should be comfortable raising an issue simply because the customer ought to be aware of it.
This question also gives them permission to challenge the usual agenda. If every review meeting follows the same pattern, important issues can remain outside the conversation. Asking what’s missing can reveal where the relationship needs to become broader, more open or more forward-looking.
These questions are only useful if the answers lead somewhere. At the end of the discussion, agree on a small number of practical actions. Be clear about who owns each action, when it will be reviewed and what progress should look like.
You may discover that the relationship is stronger than you thought. You may identify areas where expectations haven’t been communicated clearly. Or you may realise that your organisation now needs a different level of support.
The first step is understanding whether your current IT support is simply responding to what happens or actively helping your organisation improve and prepare.
When did your provider last help you see something you hadn’t already identified yourself?
If you can’t remember, these ten questions are a good place to begin.
If you would like an independent conversation about what your organisation should expect from its IT support, TIEVA would be happy to help.