From a request a business posted
Voicemails and texts logged to the client timeline
Staff copy each client call, voicemail and text from RingCentral into Karbon by hand, when they remember, and many never get logged.
Facilities maintenance contractors
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 does what
What you get
Draft for review
The rules it follows
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.
What it learns when your team adjusts 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
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
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
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.
What has to be true
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.
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.
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
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.
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.
Senior engineers agree the rules with the dispatcher, test on past cases and set approval limits and a way to switch it off.
Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.
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
The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.
Honest limits
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.
More use cases
From a request a business posted
Staff copy each client call, voicemail and text from RingCentral into Karbon by hand, when they remember, and many never get logged.
From a request a business posted
Coordinators spend the day logging work orders, chasing vendors for dates, waiting on owner approvals and updating tenants on what's still open.
From a request a business posted
The bookkeeper opens each emailed bill and re-enters the vendor, date, tax, amount and coding into the books by hand.