By Clarus Content Team · Published 22 november 2026
Good warehouse management system support means a named route to a person when a process stops, written response and resolution times for each severity level, and clear hours. It also means a plan for training and releases. The test is simple: when a supervisor is stuck mid-shift, how long until someone who can fix it is looking at the problem?
This guide is for UK warehouse and 3PL operators choosing or reviewing WMS support, often called WMS support or a WMS helpdesk. It covers support models, severity levels and SLAs, hours and out-of-hours cover, onboarding, releases, and the questions to put to a vendor before you sign.
What WMS support actually covers
WMS support is the service that investigates and fixes problems with the system after go-live, answers how-to questions, and keeps it updated. The commitments sit in a service level agreement (SLA), which defines response times, resolution targets and what is excluded.
Most vendors borrow their incident vocabulary from ITIL, the service management framework: log the incident, set a priority, respond, resolve. If you are buying a hosted system, the NCSC cloud security guidance is a useful companion, because support and security questions overlap when a supplier runs the platform for you.
Three things get blurred in sales conversations:
- Response time is how long until a person acknowledges and starts work. An auto-reply is not a response.
- Resolution time is how long until the problem is fixed or a workaround is in place. At Clarus, a resolution may be a workaround or temporary fix, and the Support Schedule says so.
- Availability is a separate promise about the platform itself. Clarus states an uptime target of 99.9% a month, excluding planned maintenance, emergency downtime, third-party faults, force majeure and security-related outages.
Support models: ticket portal or help inside the system
Most WMS support is a ticket portal and an inbox. That works for a slow-moving question and fails for a supervisor who cannot finish a process during a shift. A complicated problem is hard to describe in an email, so it goes back and forth for hours.
Clarus moved support into the product. The support bubble inside Clarus holds an always-on AI assistant that answers from the documentation (answers can be rated, and the support team reviews the poor ones), live chat, live video calls with the support team, the product roadmap with voting, news and the changelog. It has been live for every customer since early August 2026 and replaced the previous ticket desk. The team aims to respond within 5 minutes during support hours. That is a goal, not a contracted SLA.
Be clear about the limits. The AI assistant answers from the documentation, so anything undocumented goes to the team. Video calls start when the team invites you, not on a pre-booked slot. The people are there in support hours only.
Severity levels and SLAs, with real numbers
Severity levels stop the loudest customer winning. Clarus uses four priorities: P1 is the platform down or unavailable, P2 is a major loss of essential functionality with many users affected, P3 is moderate impact on a small number of users, and P4 is low impact or a general question. Priority follows the impact, not how urgent the caller sounds.
The table below shows the response and resolution targets in the Clarus Support Schedule, by tier.
| Priority | Standard (response / resolution) | Gold (response / resolution) | Platinum (response / resolution) |
|---|---|---|---|
| P1: platform down | 3 hrs / 6 hrs | 2 hrs / 5 hrs | 1 hr / 4 hrs |
| P2: major loss of function | 6 hrs / 12 hrs | 3 hrs / 10 hrs | 2 hrs / 8 hrs |
| P3: moderate impact | 8 hrs / 24 hrs | 6 hrs / 20 hrs | 4 hrs / 16 hrs |
| P4: low impact or question | 24 hrs / no target | 20 hrs / no target | 16 hrs / no target |
Read it like this: P1 and P2 are the stop-the-warehouse levels. P3 and P4 are measured in business hours, and if you log one outside business hours, the clock starts at the start of the next business day. In practice, a P3 is a non-core function failing, or a core one failing in a narrow case with an acceptable workaround, such as an incorrect report or a screen that errors on one edge case.
Den incident management process behind this also matters: who triages, who confirms severity, and how a fix moves to a release. Ask any vendor to describe it. At Clarus, the support team confirms the severity of each reported issue before it moves on.
Hours, out-of-hours cover and who you talk to
Hours are where support promises quietly narrow. Clarus support hours are Monday to Thursday 08:00 to 17:00 and Friday 08:00 to 16:00, UK time, closed at weekends and on UK public holidays. There is no helpdesk outside the hours in your contract unless you take an enhanced tier. The platform itself is hosted on AWS and monitored continuously, and if there is an infrastructure issue Clarus is on hand to fix it.
| Funksjon | Standard | Gold | Platinum |
|---|---|---|---|
| Knowledge base articles | Ja | Ja | Ja |
| Business hours support | Ja | Ja | Ja |
| Phone support in business hours | Nei | Ja | Ja |
| 24/7 support for P1 and P2 only | Nei | Nei | Ja |
| Dedicated business manager | Nei | Nei | Ja |
Round-the-clock cover is a Platinum feature, and it covers P1 and P2 incidents only. Clarus does not offer 24/7 human support for everything, and you should be wary of any vendor that implies it without showing the contract wording. Higher tiers cost more, so factor them into your WMS-kostnad comparison rather than finding out at renewal.
If your site runs nights or weekends, work out what you need. A 3PL running a Saturday despatch needs to know what happens when a P2 hits at 06:00 on a Saturday, not on Monday. Out-of-hours support can sometimes be arranged on request with notice, with costs agreed in advance, but treat that as a conversation to have before you sign, not a fallback to assume.
Onboarding and training are support too
Most support tickets in the first months trace back to training and configuration, not defects. The Clarus Support Schedule excludes issues caused by use by untrained users, which tells you how seriously a vendor takes it. HSE warehousing guidance makes the same point about people and workplace safety: competence has to be built, not assumed.
The Clarus approach follows four steps: requirements evidenced in workshops, documentation issued after the workshop for customer sign-off, training built around the agreed configuration, and a user acceptance test (UAT) schedule that acts as sign-off. All UAT is manual, run by the people who will use the system. A standard project aims to go live in around 12 weeks with the right support on both sides, because people need time.
The most useful single thing a customer can do is name a super user. Mathew Buttar, Head of Solutions at Clarus WMS, puts it this way: the aim at the start of any project is to get the customer to identify a super user, because that embeds in at least two people why the system was set up the way it was. They manage the UAT, so they are confident the processes work, and they become the go-to person on site.
People new to scanners are usually less of a problem than managers fear. On a go-live earlier this year, a first-time user was panicking, so Mathew picked the first two real orders alongside him, and within two or three hours he found it easy. Build that sit-beside-them step into your plan. The håndholdte arbeidsflyter on the floor are the part of the system most people touch every minute, so that is where training time pays back.
Release management: how fixes and updates reach you
Ask how fixes ship. In a cloud-native system such as Clarus there are no version upgrades to schedule, and you are always on the latest release. That moves the release question from “when do we upgrade” to “when does my fix land”.
At Clarus, a P3 issue is resolved in the next scheduled release and a P4 issue is prioritised into the backlog with no target date. Releases are published in the product updates and changelog in the Clarus documentation, and you can subscribe to them. Requests for improvements go to the community page and then to the product team. Customers can vote on the roadmap in the app and get an email when an idea moves into active work and again when it ships.
For a 3PL, release notes matter because a change to picking or billing logic can affect client SLAs. Read them, and check your inventory accuracy routines after a release that touches stock movements.
Questions to ask a WMS vendor before you sign
Use these in a supplier meeting. They are also a reasonable checklist for a support review with your current vendor.
- Can I see the written severity definitions and the response and resolution times for each tier?
- Which priorities are covered outside business hours, and in which tier?
- What is the difference between your goals and your contractual SLAs?
- Can I speak to or video call a person from inside the system, and when are they available?
- What is excluded from support: third-party software, unapproved integrations, untrained users?
- How is severity decided, and who decides it?
- How do fixes and updates reach me, and how will I know what changed?
- Who runs training, what is the super user model, and what does sign-off look like?
- How do I suggest a change, and will I hear what happened to it?
- What is the uptime target, what is excluded from it, and where can I see incidents?
- Is a named account or business manager included, or only in a higher tier?
Check supplier risk the way you would for any critical system. The NCSC supply chain security guidance gives a framework for doing it, and trade bodies such as UKWA og CILT are good places to ask peers who supports them well. If you are comparing vendors for a multi-client operation, read our guide to the best WMS for 3PL and the overview of a 3PL WMS alongside it.
Measuring whether support is working
Track your own numbers rather than trusting a dashboard. Log every request with its priority, the time you raised it, the time of the first useful response and the time it was fixed. Review them monthly against the contract targets and against your warehouse KPIs. A pattern of repeated how-to questions points to a training gap. A pattern of P3 issues in one workflow points to a configuration or product problem you should raise with the vendor.
Clarus is a purpose-built 3PL solution, and it works with 3PL-leverandører that need clear, written support terms. Its AI-assistent handles documented how-to questions at any hour so the team can spend time on problems that need a person.
Snakk med en lageransvarlig
Hvis du vurderer ulike alternativer og ønsker å se hvordan et spesialutviklet lagerstyringssystem (WMS) fungerer i praksis, er Clarus verdt å ta en prat med. Vi samarbeider med 3PL-leverandører og distributører over hele Storbritannia for å implementere lagerstyringsprogramvare som tilpasses din driftsmodell – ikke omvendt.
Ta kontakt med teamet vårt å snakke gjennom dine krav.