AI operations assistant: dispatch, updates, a morning roll-up.
For dispatch, field-service and logistics desks: every job matched to a rule you wrote, every customer, crew and supplier update drafted when 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.

In one paragraph
What does an AI operations assistant do?
An AI operations assistant carries the coordination loops of a dispatch or logistics desk. The Unistaff operations role, built on request for one company, proposes each assignment from the rules you write and names the rule it used, drafts customer, crew and supplier messages when a job changes state, and rolls the day into one morning summary. A person sends every message.
Next step
A scoping call about your dispatch rules, where orders arrive and who sends each update. Price and timeline are agreed there, before anything is built.
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.
The path of one work order
Five steps from an incoming order to the morning summary. The machine proposes and writes; a coordinator confirms every match and sends every message.
- 01
Order arrives
A form on your site or an export lands as one record
- 02
Assignment proposed
From your rules — location, skill, capacity — with the rule named
- 03
Coordinator confirms
Accepts the match or changes it
- 04
Updates drafted
Customer, crew and supplier messages at each status change
- 05
Morning roll-up
Done, stalled and open loops, with the age of every stuck item
Never by itself
Sending a message, calling or texting a customer, waking the on-call person. The platform has no send path of its own and no SMS or voice connector, so each of these waits for a person.
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.
On a logistics or field-service desk
An AI logistics operations assistant works the same loops a coordinator does: who is free, where the customer is, whether the part or the shipment arrived, whether the job finished. The role keeps each loop on one list and writes the next message for it.
You write the rules once at the scoping call — territories, skills, capacity, the on-call roster, how long a supplier may stay silent. Your team starts the day with one summary 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
The intake form already runs on our own sites
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 rules held in code behind the drafts — approvals, trust levels, pause and the stop button — are listed on the product page; connector status is on integrations.
Frequently asked questions
It carries the coordination loops: it proposes who takes each job from the rules you wrote, drafts the status update when a job changes state, keeps the open supplier and purchase-order chases on one list, and writes a morning summary of what is done and what is stuck. A coordinator confirms and sends.
For the coordination, yes: delivery and pickup orders, carrier and supplier follow-ups, and the morning list of stalled shipments. No TMS, carrier or tracking connector ships today, so orders arrive through a form or an export until a setup builds that connection.
The operations role is built on request and quoted after a scoping call. Scope and price are agreed before anything is built, then it is one flat monthly fee per AI employee with no seat or message meters. The ROI calculator models 35 routine hours a week for this role, and you set the share you hand over.
Jobber, Housecall Pro, ServiceTitan and the rest are connectors we scope and build against your account as part of a deployment. None ships out of the box today.
It writes the message; a person sends it through the channel you already use. Phone and SMS are Planned, and no voice or SMS connector ships in the platform today.
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.
The on-call roster is part of the rules written at setup. An urgent job goes to the top of the queue with the escalation message already written, and waking a person up stays a person’s decision.
Each open purchase order stays on the list with the date of the last message, and the next follow-up is drafted once the silence passes the limit you set. A person sends it, and the thread stays visible until someone answers.
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.
Write your dispatch rules down once
Bring your dispatch rules, the status messages you send most and the suppliers you chase to the scoping call. It settles where orders arrive, who sends each update and the price. The team replies within one business day.
Continue learning
Metric
Which KPIs an AI employee is measured on
Compare
AI employee vs. human virtual assistant
Guide
How to choose your first AI employee
Integrations
Integrations: what connects today and what is planned
Calculator
ROI calculator with the operations role preset
Pricing