What to expect from your CMMS vendor's support

Support is the part of the contract that gets compared the least and is noticed the most starting around the third month. In the demo everything works; the problem shows up when you have to configure an unusual checklist, when someone accidentally deletes something, or when the system has to do something nobody planned for.

Here’s what’s worth asking before signing, and what’s reasonable to expect.

The three phases, which aren’t the same thing

They tend to get lumped together and they have different needs.

Startup. Configuring the minimum for the system to start working: critical assets, families, checklists, and frequencies. It’s the phase that needs the most support and the shortest one.

Adoption. Getting the team to actually use it. Here support isn’t technical: it’s resolving specific friction points — a field that gets in the way, an alert that’s annoying, a screen that doesn’t match how they work.

Operation. The day-to-day over the years. What’s needed here is someone to answer when something doesn’t work, and for the product to keep evolving.

A vendor can be good at one and weak at another. It’s worth asking about all three.

What to ask before signing

Who configures the startup, and how long does it take? If the answer is “it’s very easy, you do it yourselves,” ask them to show you configuring a real checklist with several periods and a cascade by family.

What happens when I need something that doesn’t exist today? Three possible answers, and it’s worth knowing which one you’ll get: it gets configured, it goes into a future release, or it’s billable custom development. All three are legitimate; mixing them up isn’t.

What happened to old versions the last time there was a major change? And who handled the migration. The answer describes the vendor better than their catalog does.

How do I get my data out if I leave? It’s an uncomfortable question and exactly the one you should ask.

Is there documentation and recorded training? Because turnover happens, and retraining every new hire by phone doesn’t scale.

What’s included in every GMAO Cloud plan

Licenses are unlimited across all three plans — your team, clients, and subcontractors join at no per-user cost — and all of them include a help center with guides and training recordings, a client portal, request intake by email or form, online support, and an AI assistant.

The difference between plans isn’t in the product’s features, but in the support and resources: from Advanced up, there’s a recurring executive report on the service and on-demand follow-up meetings.

It’s worth knowing when comparing, because it’s different from the common practice of stripping out features by tier.

What no vendor can do for you

And it’s the biggest part of the work, so it’s worth spelling out.

Deciding what’s critical. Which equipment halts production or service if it fails is a business decision, not a configuration one.

Setting the technical criteria. What gets checked on each piece of equipment and how often is set by the manufacturer, the standard, or your own people’s experience.

Agreeing on the process. If today nobody decides who handles what or with what priority, no support will solve that: the system will just record the same disorder more precisely.

Getting the team to use it. Support can help, but adoption is carried by someone in-house.

A vendor who promises to take care of all four is selling something they won’t deliver.

The role you do need on your side

Someone internal who owns the project. They don’t have to be technical: they have to understand the operation and be able to make decisions.

Without that person, every configuration question turns into a meeting, and startup drags out for months. With them, most get resolved on the spot.

Training, which goes stale

A point almost never covered in the contract and that decides year four: people change.

The technician you trained at startup may not be there in two years, and the one who joins learns from their colleagues. That works for the basics and fails exactly where it’s needed least often: configuring a new checklist, fixing a frequency, pulling a report other than the usual one.

What fixes this isn’t more in-person training: it’s having reference material — guides and recordings — that someone can go to when they need it, and configuration built in a comprehensible way, with families and profiles instead of case-by-case exceptions nobody remembers the reason for.

It’s worth asking about this in the demo: what material exists, whether it’s up to date, and whether it’s accessible without opening a support ticket.

How to know if support is working

Three signs, at the three-month mark:

The team asks fewer questions. Not because they’ve given up, but because they already know.

The questions change type. From “how do I do this” to “how do we configure that,” which signals the system is adapting to how you work.

There’s data in the reports. This is the final proof: if by the third month the completed plan and logged hours make sense, the rollout has worked.

What’s reasonable to ask for, and what isn’t

For the relationship to work, it helps to be clear on where the line is.

Reasonable: getting help configuring a complex checklist, having them explain how to set up a status workflow, having them respond when something doesn’t work as it should, being notified of product changes, and being told openly when something can’t be done.

Not reasonable: asking them to decide your equipment’s inspection frequency for you, loading your inventory without anyone in-house validating what’s critical, or having custom development count as “support.” The third one isn’t vendor stinginess: it’s that custom development has scope, cost, and ongoing maintenance, and treating it as support ends badly for both sides.

What to do if it stalls

It’s almost always the same thing: too much was attempted at the start.

The way out is reducing scope, not asking for more support. Go back to critical assets, with their checklists and frequencies, and leave the rest for once that’s been running smoothly for weeks. Six months of loading data before seeing a result exhausts any team.

There’s more on startup in how a maintenance management program gets rolled out.

If you’d like to ask us about anything in this article, you can get in touch or request a demo.