From a request a business posted
Work orders from email into the job system
A dispatcher retypes every work order email into the job system, field by field, before anyone can schedule it.
Property management
At many management companies, every maintenance request lands with one coordinator, and the emails, texts and portal tickets get worked top to bottom in the order they arrived. An A/C outage in a unit with a baby can sit behind a running toilet and a humming dishwasher until mid-afternoon.
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 maintenance coordinator. It takes the data entry, vendor chasing, owner follow-up and repeat tenant updates off the maintenance coordinator. 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
At first the coordinator reviews every work order, vendor choice and owner message before it goes out. Review stops for a routine type of job, such as a standard plumbing call under the owner's limit, once the agent's record on that type is good and the business agrees.
Emergency dispatch, costs above an owner's limit, and any dispute with a tenant, vendor or owner keep going to a person.
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 coordinator sends an appliance job at one property to a different vendor because the usual one is slow there, the change is saved as a rule for that property and trade, and next time the agent proposes the new vendor first. The coordinator decides whether a change becomes a rule, an example or a one-time 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
After four years in the role, the coordinator described starting most mornings with more than a dozen new requests and no way to rank them, so urgent jobs surfaced hours late. Vendor insurance had lapsed without anyone noticing until dispatch time. Dozens of owners each had their own approval limits and habits, none of it written down, and slow owner replies left tenants waiting for days.
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
Working the inbox in the order requests arrived is only habit. So is keeping each owner's approval limit and contact preference in the coordinator's memory.
What we delete before building anything
We delete the re-entering of each request into the work order by hand and the status texts typed one at a time. We write down the owner limits that today live in one person's head.
What is left
The agent. The agent logs and ranks each request, proposes the preferred insured vendor, sends approval requests to owners and follows up on silence, and keeps tenants updated on the schedule the company sets.
A person. The coordinator reviews vendor choices and costs, handles anything unusual, and decides whatever needs a judgment call.
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 access to the maintenance inbox, the text line and the tenant portal, plus permission to create and update work orders in AppFolio or Buildium. It also needs the vendor list with trades and insurance dates. We sit with the coordinator to write down each owner's approval limit and preferences.
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 maintenance coordinator, 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
The agent does not judge whether a repair is worth doing or approve spending; the coordinator and the owner decide that.
The situation on this page is drawn from a public request posted by a person at a management company, paraphrased, not a client engagement.
More use cases
From a request a business posted
A dispatcher retypes every work order email into the job system, field by field, before anyone can schedule it.
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
The bookkeeper opens each emailed bill and re-enters the vendor, date, tax, amount and coding into the books by hand.