Facilities maintenance contractors

Work orders from email into the job system

Work orders reach a facilities contractor from client portals and by email, and every portal also sends a copy to the shared inbox. The dispatcher re-enters each one into the job system, checks the not-to-exceed amount and decides whether it is a new job or an update to one already open.

Who it is forFacilities maintenance and trades contractors with 10 to 50 field staff and 2 to 5 in the office
Who decidesThe dispatcher
Where the work livesShared Gmail inbox → FACIL-IT, ServiceTitan or Jobber
BuildTen business days
A contractor's office desk with no computer and no screen: a stack of printed work order sheets with one line circled, a clipboard, a yellow wet floor sign leaning against the desk, a closed teal toolbox and a coffee mug.

Who does what

The office loses its hours retyping what the client already wrote.

Read and sort the inbox It reads each new email and portal copy, sets duplicates aside and groups messages about the same store.The agent
Fill the job record Client, site, address, work order number, trade, service deadline, contact and scope go into the job system. Attachments and links go on the record.The agent
Check against the client's rules It compares the scope with the not-to-exceed amount and flags any required field that is missing before the job can be scheduled.The agent
New job or update When a second email arrives about a store with an open job, the dispatcher decides whether it is new work, a revised scope or a reminder. A duplicate sends two crews to one leak.The dispatcher
Request an increase When the scope plainly costs more than the limit, the dispatcher asks the client for an increase before the truck rolls.The dispatcher

What you get

A filled job record for each work order email, with the files attached and any missing field or over-limit scope flagged for the dispatcher.

Draft for review

Email
Work order email from a retail client's portal: store 214, water leak at the rear door, priority two.
Draft
Update to the open plumbing job at store 214, with a second leak location added to the scope. Not a new job.
Based on
The open plumbing job at store 214 for the same client, opened two days earlier, and the portal reference in this email that matches it.
How sure it is Moderate
Why a person decides The added location widens the scope, and the open job's not-to-exceed limit may not cover both leaks. The dispatcher decides whether to request an increase before the crew goes back.

The rules it follows

It follows each client's limits and deadlines from the first day.

These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.

  • Each client's not-to-exceed amount, and who asks for an increase above it.
  • Each client's service deadline by priority code.
  • The fields a work order must have before it is scheduled.
  • Which trade and which tech take which kind of job at which sites.

What it learns when your team adjusts its work

Useful from the first day, and it keeps getting better. The dispatcher reviews its work.

The busywork it takes off the dispatcher. It takes over re-entering each work order email into the job system and chasing the fields that are missing. That time goes back to the work only they can do.

What it starts out knowing

  • The clients and sites already in the job system
  • Each client's not-to-exceed limits and service deadlines
  • The fields required before a job is scheduled
  • Which trade and which tech take which job

It works from these sources, shows which one an answer came from, and asks when the answer is not there.

Who reviews its work, and when review can stop

The dispatcher reviews every entry at first. For a routine type, such as a plain new job from a regular client, review stops once the agent's record on them is good and the business agrees.

Any email the agent cannot match to a new job or an open one, and every request for a limit increase, keeps going to the dispatcher.

It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.

When your team adjusts its work

When the dispatcher changes the trade on a roof drain work order from plumbing to roofing for one retail client, the change is saved as a rule for that client's work orders, and the next roof drain order from that client goes in under roofing. The dispatcher decides whether a change is saved as a rule, an example or an exception.

It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.

From a request a business posted

A U.S. facilities maintenance contractor, on a public online forum while looking for help.

The company takes in a large number of work orders every week. They arrive by email, and the ones from client portals also land in the inbox as copies. Someone has to pull out the client, store, address, order number, trade, deadline, not-to-exceed amount and scope, then open or update the job in FACIL-IT and let the team know in Google Chat.

Paraphrased from a public post, not quoted, and not a client engagement.

From first principles

Is this email a new job, an update to an open job or a reminder, and does its scope fit the client's limit?

Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.

  1. What has to be true

    • Every work order names a client, a site and a work order number in some form.
    • Each client has its own not-to-exceed limit and service deadline.
    • A job cannot be scheduled until its required fields are filled.
  2. What is only habit

    Retyping each email into the job system by hand is habit, not a rule. So is reading the same order twice because it arrived as a portal copy and as a direct email.

  3. What we delete before building anything

    We set aside duplicate portal copies first, so each work order is read once. We also drop the manual Google Chat post for routine new jobs, since the agent can post it when the record is filled.

  4. What is left

    The agent. The agent reads each email, matches the client and site, fills the job record, attaches the files and checks the scope against the client's limit.

    A person. The dispatcher decides new job or update when the match is unclear, and asks the client for any increase over the limit.

The kind of work: Work that arrives by email and phone. Work orders, bills, voicemails, texts and maintenance requests reach the business as messages, and each one has to be read, sorted and entered into the system that runs the work. The software holds the record once it exists, but someone still has to decide what each message is, where it belongs and whether it fits the rules, so people do it by hand.

What the engagement needs

What we need from you, and how it runs.

The engagement needs read access to the shared work order inbox and write access to the job system. A few months of past work orders show how each client writes them, and the not-to-exceed rules by client complete the picture. If the job system has no open connection, the first step says so and proposes the most stable alternative.

How the engagement runs

  1. 01

    Fit test first

    We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.

  2. 02

    Build in ten business days

    Senior engineers agree the rules with the dispatcher, test on past cases and set approval limits and a way to switch it off.

  3. 03

    Ninety days of support, included

    Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.

  4. 04

    Keep improving it, with your choice of operator

    You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.

When we'd point you elsewhere

Sometimes a ready-made tool is enough.

The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.

  • A handful of work orders a week from one or two clients An email parser feeding a spreadsheet, checked by a careful person
  • Most work orders come through one client portal the job system already imports The job system's own portal import

Honest limits

What this page does not claim.

If the job system has no way in for software, every entry goes through its screens, which is slower and harder to keep running. We look at that before any build.

The situation on this page is drawn from a public request a facilities contractor posted while looking for help, paraphrased. It is not a client engagement.

Show us the work

More use cases

More work of the same kind: work that arrives by email and phone.