Fixing problems
Investigate and resolve problems that affect users or everyday work.
We support software that is already in use, helping resolve problems, keep it maintained and make useful improvements over time.
Support should help keep everyday work running while problems are fixed, maintenance is planned and useful changes are made.
Investigate and resolve problems that affect users or everyday work.
Watch availability, errors and important signs that something is slowing down or failing.
Apply agreed updates and deal with known problems before they become more serious.
Review access, configuration and security-related updates.
Add or change features when there is a clear business need.
Help decide which maintenance and improvements should happen next.
Every request follows a simple path so people know what needs attention, what is being done and what happens next.
Tell us what happened, who is affected and what information is available.
Check the impact and decide what needs attention first.
Fix the problem or provide a practical temporary solution.
Check the result and identify anything else that needs attention.
Priority is agreed according to business impact, the number of users affected and whether a practical workaround is available.
A key service is unavailable or severely affecting operations.
A major function is impaired and only a limited workaround is available.
The issue affects everyday work but operations can continue.
A scheduled update, enhancement or non-urgent correction.
Ongoing support can also highlight repeated problems and useful changes that make the application easier to use and maintain.
Find parts of the application that are slow and make useful improvements.
Turn repeated user problems or requests into sensible changes.
Simplify steps, approvals and notifications where they cause unnecessary effort.
Update the application when business needs or connected systems change.
Customers should know how to request help, who owns the next action, how progress is communicated and how completed work is confirmed.
A clear way to report a problem and provide the information needed to begin.
Know who is handling the next step and what priority has been agreed.
Receive useful updates while the issue is being investigated or fixed.
Confirm what changed, whether the problem is resolved and whether anything else is needed.
The right level of support depends on how important the application is, when it is used and how much ongoing help is needed.
For applications that mainly need issue handling and planned maintenance.
For important applications that need monitoring, maintenance and regular review.
For applications that also need planned changes and improvements.
The final level of support is agreed based on the application, business importance, operating hours and level of assistance required.
Yes, after an initial review. We first need to understand how the application is built, where it runs, what information is available and any known problems before agreeing what we can support.
Support can cover application problems, failed connections, access issues, performance concerns and agreed maintenance. The exact coverage is agreed for the application.
Yes. Useful changes can be planned alongside support when there is a clear business need.
Urgent problems are assessed according to business impact, affected users and whether a practical temporary solution is available. The response arrangements are agreed as part of the support service.
Tell us what software you use, what problems you are seeing and what kind of help you need. We’ll help you work out a practical way to support it.