AI operations assistant. Dispatch, update, follow through.
Every job matched to a rule you wrote, every update written the moment the status changes, and a person on the send.
On requestBuilt for your company by the Unistaff team. The role that runs in the product today is the AI inbound sales manager.
What it does
Dispatch proposals
Proposes the assignment from your own rules — location, skill, capacity — and names the rule it applied.
Status messages
Writes the update for each job the moment its state changes, so a coordinator sends instead of composing.
Supplier follow-up
Keeps the list of open purchase orders and missing items, and writes the next chase for each one.
Daily reporting
Rolls completions, stalls and open loops into one morning summary with the age of every stuck item.
How it works
Receive
A work order arrives through the form and lands as one record.
Assign
The assistant proposes the match and names the rule behind it.
Update
Status messages are written and go out on a person's send.
Report
Completions roll into a morning summary with the stuck items on top.
What exists today
- On request
Dispatch proposals and status drafts
Assignments proposed from your rules, customer and supplier updates drafted for a coordinator to send.
- On request
Morning roll-up
Completions, stalls and open loops in one summary, with the age of every stuck item.
- On request
Field-service tools
None ships today. A setup can build a connection to a tool such as Jobber or ServiceTitan.
- Planned
Text and phone
No SMS or voice channel ships today; messages go out through the channel your team already uses.
Operations that run overnight
Field-service and logistics teams lose hours to coordination noise: who is free, where is the customer, has the part arrived, did the job finish. The assistant carries every one of those loops and writes the next message for each.
You define the guardrails. It keeps the follow-ups, the updates and the roll-up moving. Your team wakes up to a clear picture of what is done, what is stuck, and what needs a call from a person.
Evidence · AI operations
What it is built on
The pieces of the platform this role is built on, each marked with the site's three words: Live works in the product today, On request is built with you during a setup, Planned is on the roadmap.
Live
A request form on your site posts work orders into one record
The intake endpoint runs in production on our own sites today. It caps the request body before parsing it, absorbs bot submissions without writing anything, and stores the order in Postgres. A request that fails validation gets a reason back instead of a silent success. For your site, the form is connected during an on-request setup.
On request
Assignments are proposed and messages are written, never sent
The assistant applies the rules you wrote and shows which one produced the match, so a wrong call comes with the reason it was made. Nothing reaches a customer, a technician or a supplier without a person on the send.
Planned
Text and phone are planned
The platform ships no SMS provider and no voice connector yet, so messages go out through the channel your team already uses. A field-service tool such as Jobber or ServiceTitan is an integration we build against your account during a deployment.
The gates behind the drafts — approvals, spend caps, the kill switch — are listed on the product page.
Frequently asked questions
Not out of the box today. Jobber, Housecall Pro, ServiceTitan and the rest are connectors we scope and build against your account as part of a deployment.
It writes the message; a person sends it through the channel you already use. There is no SMS provider and no voice connector in the platform today, and we would rather say that than imply a phone line that does not exist.
You define the rules — geography, skill tags, capacity limits — and it applies them every time, with the rule that produced the match written next to the proposal.
It reads your on-call roster, marks the job urgent and puts it at the top of the queue with the escalation message already written. Waking a person up is still a person’s decision.
The message is written the moment the status changes, in the customer's preferred channel and language. Sending stays with your coordinator, which is one click rather than five minutes of writing.
It queues each follow-up for the right local hour and keeps the thread on the list until someone answers, so a silent supplier stays visible instead of quietly ageing.
Yes. IT tickets, facilities requests and logistics tasks run the same loop: one record in, a proposal with its rule, a written message, a person on the send.