Field service scheduling
Our dispatchers juggle technicians across branches. Where does AI actually help with scheduling and dispatch?
Last updated
AI helps most with the work around the schedule: turning emailed and phoned-in jobs into complete job records, setting priority, checking skills, licences and parts, drafting customer updates and flagging jobs at risk of an SLA breach. The scheduling maths belongs to the optimisation engine in your field service platform, such as Resource Scheduling Optimization in Dynamics 365 Field Service. A dispatcher still approves the board.
Who this is for
This page is for operations, service delivery and dispatch managers in multi-branch field service and facilities organisations running simPRO, Uptick, AroFlo, Dynamics 365 Field Service or Salesforce Field Service, where dispatchers rebalance technicians across branches all day and jobs still arrive by email, phone and customer portal.
It separates what your platform's scheduling engine already does from the work around it that AI can take on, and sets out how to prove the change at one branch before rolling it out.
What the scheduling engine already does
Dynamics 365 Field Service
Resource Scheduling Optimization is a paid add-in that schedules many jobs at once, minimising travel and considering technician characteristics, territory and promised time windows. Microsoft describes runs overnight, every 30 minutes, or when an urgent job is created.
Salesforce Field Service
The optimiser uses work rules to remove technicians who are unqualified or unavailable, then scores the rest against weighted service objectives and job priority.
simPRO, Uptick and AroFlo
These platforms hold the jobs, technicians and schedule board. Ask each vendor which automatic scheduling features your plan includes before building anything.
What that means
Building a new optimiser rarely makes sense when one already exists. The schedule is only as good as the job data fed into it, and preparing that data is where most dispatcher time goes.
Where AI helps, step by step
| Step | AI does | Engine or person does |
|---|---|---|
| Job intake | Reads emails, portal requests and call notes, and creates a draft job with site, asset, fault and contact | Coordinator approves or fixes the draft |
| Triage and priority | Suggests job type and priority from the fault description and the customer contract | Dispatcher confirms anything urgent or safety related |
| Skills and compliance | Checks the job against required skills, licences, site inductions and access rules | Engine only offers technicians who pass |
| Parts | Checks likely parts against van and branch stock and flags shortfalls | Stores or purchasing arranges a transfer |
| Scheduling | Supplies clean job data, durations and constraints | Optimisation engine builds the schedule and the dispatcher adjusts it |
| Customer updates | Drafts confirmations, delay notices and arrival messages from job status | Approved templates send, and staff handle complaints |
| SLA risk | Flags jobs likely to miss response or resolution times early in the day | Dispatcher reschedules, reassigns or escalates |
What makes it work
Current skills and compliance records
Technician skills, licences and inductions need expiry dates recorded in the platform. AI can flag records about to lapse, and a named person owns updating them.
Contract terms in a readable form
Response times, after-hours rules and priority definitions for each customer belong in a table the AI can read, so triage and SLA flags follow the contract.
Job durations from history
Actual durations by job type and asset improve both the engine's schedule and the accuracy of SLA risk flags.
How to start
Measure one branch
For two to four weeks, record how jobs arrive, how long intake takes, how often jobs are rescheduled and how many breach SLA. This is the baseline.
Run a shadow pilot
AI drafts job records, priorities and SLA flags on live work while dispatchers work as usual, and its output is compared with theirs. You set the accuracy bar.
Build into your platform
Drafts write into simPRO, Uptick, AroFlo, Dynamics 365 Field Service or Salesforce Field Service through their APIs, with the AI layer running on your infrastructure in Australia.
Roll out branch by branch
Each branch goes live once its own results meet the bar, followed by support from Solve8 or handover to your team.
How Solve8 delivers it
Each phase above is fixed fee, and you can stop after any phase. A dispatcher or coordinator approves every AI output before it reaches a technician or customer. Workshops run on site at the branch, and builds run remotely under your access controls.
Limits
Low job volumes
A branch with a handful of jobs a day gets more from cleaner job templates in the platform than from AI.
Emergency and safety calls
Calls involving risk to people go straight to a person. AI logs them and leaves triage to the dispatcher.
Promises to customers
AI sends only approved message templates and never commits arrival times, credits or contract changes on its own.
Related work
AI for field serviceDefect coding, quote drafting and job to invoice for multi-branch operators.
Field service to ERP integrationStop rekeying jobs from simPRO, Uptick or AroFlo into finance.
AI for shared inboxesClassify and route customer emails before staff open them.
AI quoting for fire protectionDefect records categorised and quote lines suggested, built in the client's cloud in Sydney.
Sources
Microsoft Learn, Overview of Resource Scheduling Optimization for Dynamics 365 Field Service: https://learn.microsoft.com/en-us/dynamics365/field-service/rso-overview
Salesforce Trailhead, Field Service optimization, Explore Optimization: https://trailhead.salesforce.com/content/learn/modules/field-service-lightning-optimization/explore-optimization
Questions
Can AI replace our field service scheduling engine?
Usually there is no need. Dynamics 365 Field Service and Salesforce Field Service include optimisation engines built for routing and matching. AI adds value by feeding them complete job data, priorities and constraints, and by handling intake, customer updates and SLA flags around the schedule.
Can AI read job requests from emails and phone notes into simPRO or AroFlo?
Yes. AI reads the email, portal request or call note, matches the customer, site and asset, and creates a draft job through the platform's API for a coordinator to approve. Missing details, such as an access code or site contact, are flagged before scheduling. Check API access on your plan first.
How does AI spot jobs at risk of breaching SLA?
It compares each open job's response deadline from the customer contract with its scheduled time, technician location, typical job duration and parts status, then flags jobs likely to miss early in the day. The dispatcher decides whether to reschedule, reassign or contact the customer.
Can AI check technician licences and site inductions before dispatch?
Yes, if licences, inductions and expiry dates are recorded against each technician and site requirements are recorded against each site. AI checks each job against both and flags lapsing records, and the scheduling engine then offers only technicians who meet the requirements.
Who can help with AI dispatch across branches in Brisbane, Sydney or Melbourne?
Your platform vendor or partner configures the scheduling engine. For intake, triage, SLA flags and customer updates built around simPRO, Uptick, AroFlo, Dynamics 365 Field Service or Salesforce Field Service, use a firm that integrates through their APIs. Solve8 runs workshops on site and builds remotely under your access controls.
Related
- Field service and facilitiesJobs, assets and compliance evidence.
- We key jobs from simPRO, Uptick or AroFlo into Pronto, Xero or MYOB by hand. How do we stop the double entry?How to stop rekeying jobs from simPRO, Uptick or AroFlo into Pronto Xi, Xero or MYOB: which connectors exist, their limits, and where AI helps.
- Our team works out of a shared inbox. Can AI sort the emails, update the CRM and draft replies?How AI reads a shared customer service, orders or accounts inbox, looks up the account in your CRM or ERP, logs the case and drafts replies for approval.
- Our technicians code fire protection defects differently at every branch. Can AI make quotes consistent?How AI maps fire protection defect notes from every branch to one defect list and AS 1851 category so quotes stay consistent, with a person approving each.
- AI agents for Australian organisations, built inside your systemsAn AI agent is software that reads incoming work, decides within your rules and acts across your systems. A person approves the result.
- System integrationConnections between the systems you run.
Dispatch stretched across branches?
A 30-minute review with a senior consultant. You leave with a written one-page summary you can share internally.
Fixed-fee phases, agreed before we start. Stop after any phase.