AI Dispatch · Nearshore · Aqaba
Agentic field dispatch, run nearshore.
Nearshore AI dispatch means running work-order intake, quoting, and contractor routing as an AI-assisted operation in time overlap with the US. STEADYWRK runs that operation from Aqaba — software for the repetitive routing, people for the judgment calls.
What nearshore AI dispatch means
Field-service dispatch is the loop of taking in a work order, quoting it, routing it to the right contractor, and closing it out. "AI dispatch" automates the repetitive middle — ranking contractors, drafting a quote within set bands, routing — so the operations team spends its time where a human decision actually matters.
"Nearshore" describes where that operations team sits: a time-aligned region rather than far offshore. STEADYWRK runs it from Aqaba, on a schedule that overlaps the US business day, so a US work order is acted on the same day rather than relayed overnight.
Where people stay in the loop
The agentic dispatch surface ranks, drafts, and routes — it does not decide alone. Low-confidence cases are escalated to a human queue rather than forced through, and decisions are recorded so the loop is inspectable. The aim is to remove the slow, repetitive top of the funnel, not to remove judgment.
Same-day overlap
The operations team works hours that intersect the US business day.
Escalation, not autopilot
Low-confidence cases route to a human queue instead of being forced through.
Published evals
Dispatch quality is published and inspectable, not asserted.
For the full mechanics — intake, quote, route, dispatch, close — see the Dispatch Engine.
How to evaluate the model
AI dispatch is easy to claim and harder to show. The questions that separate the two are concrete: are decisions recorded and inspectable, where does the human checkpoint sit, how many working hours overlap yours, and are evaluations published rather than asserted. Public posture for current scale is qualitative — <2hr target on quote turnaround and a 90% completion rate are the figures we stand behind.
STEADYWRK runs its own operation in Aqaba rather than reselling a labor pool, so you can talk to the team that does the work. Judge it on the track record you can see.
Frequently asked questions
What is nearshore AI dispatch?
Nearshore AI dispatch is running field-service dispatch — work-order intake, quoting, and contractor routing — as an AI-assisted operation from a time-aligned region rather than far offshore. STEADYWRK runs that operation from Aqaba, Jordan, into the US market. Software handles the repetitive routing and the operations team handles the judgment calls, on a schedule that overlaps the US business day.
Does AI make the dispatch decisions on its own?
No. The agentic dispatch surface ranks contractors, drafts quotes within set bands, and routes work; people stay in the loop. Low-confidence cases are escalated to a human queue rather than forced through. The automation removes the slow, repetitive part of dispatch so the operations team spends its time on the cases that actually need a decision.
Why run dispatch from Aqaba instead of onshore?
Aqaba is in a Special Economic Zone with a simplified business environment, the talent pool is English-fluent and bilingual in Arabic, and STEADYWRK also draws people from Amman. Because the working schedule overlaps the US business day, the operations team can act on US work orders in real time rather than on a next-day cycle. It is nearshore, not far offshore — the time gap is small enough for a working relationship.
What does the dispatch model actually do today?
STEADYWRK exposes dispatch as callable tools — work-order intake, quoting, and routing — over an API and MCP surface, with published evaluations. Public posture for current scale is qualitative: <2hr target on quote turnaround and a 90% completion rate are the figures we stand behind. The point of the explainer is the model, not a scale claim.
How do you evaluate an AI-assisted nearshore dispatch operation?
Evaluate it on observable things: whether decisions are recorded and inspectable, where the human checkpoint sits, how many working hours overlap yours, and whether evaluations are published rather than asserted. Ask what runs today, on what schedule, and how confidence and escalation are handled. As with any automation, trust should rest on a visible track record.
See dispatch in the open
Look at the mechanics and the published evaluations, or talk to the team that runs the operation.
Prefer Arabic? اقرأ هذه الصفحة بالعربية