Every request. The right shop. The first time.
The intake and triage layer for facilities work orders — built for the buildings, the trades, and the people who have to report the numbers.
What it is
An intake layer, not another system
The front door for facilities work orders. It sits in front of Archibus, Maximo, or whatever you run today and takes over the part that touches people. Nothing gets replaced. Nothing gets migrated.
The problem it solves
Tickets that start wrong stay wrong
Tenants are asked to classify problems in words they never use, so they guess — and about half guess wrong. A wrong ticket doesn't bounce, it sits. Work gets done in the field and never gets closed.
What it does
Reads it, routes it, proves it closed
Takes the request in plain language, resolves the right shop before it's submitted, asks instead of guessing when a word is ambiguous, and closes only when the technician who did the work says so.
Fix the front door of facilities work.
Most work orders fail before anyone picks up a wrench. Facilities Help Desk takes the request in plain language, routes it to the right shop before it's submitted, and won't let it close until the person who did the work says it's done. It sits in front of the system you already own.
The ticket was wrong before it ever reached a technician.
Ask someone to classify a problem in vocabulary they don't use and they'll guess. About half of them guess wrong — and a wrong ticket doesn't get corrected, it just sits.
Tenants classify work they can't classify
A tenant doesn't know whether a wet floor is plumbing or general maintenance, or whether a labor agreement makes that distinction legally binding. They know the floor is wet.
Misrouted tickets don't bounce — they age
Nobody at the receiving end owns a wrong ticket enough to redirect it, and no triage function exists to catch the error. The tenant learns the system doesn't work and starts calling instead.
The work gets done. The ticket never closes.
Your trades carry phones. If closing a job means walking back to a desktop, the job gets finished and the ticket stays open forever — and every number you report is computed from that.
One record. Four windows onto it.
A single shared ticket underneath, so work genuinely travels from the person who reported it to the person who fixes it to the person accountable for it. What each person sees is derived from who they signed in as.
There is no AI in this product. That's the feature.
Every routing decision comes from a table a cybersecurity reviewer reads line by line. No model to interrogate, no training data to disclose, no external calls, no data leaving your organization. The security review that stalls other vendors for months is, here, a short meeting.
Auditable by design
Any routing decision can be reconstructed after the fact — which rule fired, and why. Every state change is signed with a name and a timestamp. Nothing is deletable.
Numbers that survive an audit
Every figure is computed from the event log. No stored counters to drift out of sync, and no way to produce a number that isn't traceable to the events that made it.
Built for a procurement review
Jurisdiction rules from your labor agreements live in the routing table where they can be read and updated. Certification lapses hard-gate assignment. Every pick carries a reason code.
Frequently asked questions
Straight answers to what facilities directors, IT reviewers, and procurement ask us first.
Book a twenty-minute walkthrough.
Fill in the form and we'll set up a call. Send us a few of your own work orders that went wrong — misrouted, duplicated, or still sitting open — and we'll run them through the system while you watch. No slide deck. If it turns out intake isn't what's hurting you, we'll say so.