Jobs completed per technician per day
The most direct view of capacity. Compare the same season year over year where you can.
Protect margin
Job scheduling and dispatch, with your dispatcher still in charge
In most field service companies, the schedule lives in one person's head. The dispatcher knows which technician is certified for which equipment, who is running late, which customer needs a call before arrival and which van has the part. When that person is out sick, the whole day wobbles.
Signs you need this
- Your dispatcher spends most of the morning on the phone confirming who goes where.
- Technicians arrive without the right part or skill and need a second visit.
- Customers call to ask when the technician will arrive.
- Drive time between jobs is high because routes are planned by memory.
- Nobody can say how many jobs per technician per day you completed last month.
Scheduling and dispatch automation does not replace that judgment. It handles the repetitive parts: booking requests into open slots, suggesting the best-fit technician, sending on-my-way texts and flagging jobs at risk of running over. The dispatcher spends less time on the phone and more time on the exceptions that actually need a human decision.
How it works
Clean up job types and skills
List your job types, typical durations and the skills, certifications or equipment each needs. Tag each technician with what they can do. This setup work in your field service software matters more than any AI feature.
Book into real availability
Online booking, phone intake and service agreements feed into the same calendar with realistic time windows. Requests that do not fit a standard job type are routed to the dispatcher instead of being forced into a slot.
Suggest assignments
The system proposes a technician for each job based on skills, location, workload and parts on hand. The dispatcher accepts, swaps or overrides. Overrides are logged so the rules can be improved.
Keep customers informed
Confirmation, reminder and on-my-way messages go out by text or email from templates you approve. Customers can confirm or reschedule without calling the office.
Handle the day as it changes
When a job runs long or an emergency call comes in, the dispatcher sees which later jobs are affected and gets suggested reshuffles. Reschedule messages are reviewed before they go to customers.
Ways to do it
| Approach | Best fit | Notes |
|---|---|---|
| Settings in your field service software | Companies already on ServiceTitan, Housecall Pro, Jobber, FieldEdge or Service Fusion. | Many teams use a fraction of their scheduling, skills-tagging and customer notification features. Turning them on and cleaning job types is often the biggest and cheapest win. |
| Route and capacity add-ons | Teams with many short jobs a day across a wide service area. | Route optimization tools and marketplace add-ons can reduce drive time. Check that they read and write to your main system rather than creating a second schedule. |
| No-code automation | Firms using general tools such as Google Calendar, Microsoft Bookings or a spreadsheet for scheduling. | Zapier, Make or n8n can connect booking forms, calendars and text messaging. It works for smaller teams but becomes fragile as job volume grows. |
| AI-assisted dispatch suggestions | Larger teams where the dispatcher is clearly the bottleneck. | Some platforms now offer AI recommendations for assignments. Treat suggestions as a starting point and track how often the dispatcher overrides them. |
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
What we would measure
First-time fix rate
Shows whether skill and parts matching is working. Return visits are expensive and frustrate customers.
Drive time between jobs
Lower drive time means more billable hours without adding staff. Most field service platforms can report it.
Inbound where-is-my-technician calls
A drop shows customer notifications are doing their job and the office has more time for booking.
Risks and how we handle them
| Risk | Mitigation |
|---|---|
| Bad job durations produce an impossible schedule. | Base durations on your own completed-job history, review them monthly and let the dispatcher adjust windows on the day. |
| Technicians ignore the app and phone the office anyway. | Involve two or three senior technicians in the setup, keep the mobile steps few, and fix what they complain about in the first month. |
| Automated messages give customers wrong arrival times. | Send on-my-way messages only when the technician starts the drive, and keep reschedule notices under dispatcher review. |
When not to do this
If you run fewer than three or four technicians and the owner still dispatches comfortably, a shared calendar and text templates may be all you need. Do not add AI dispatch on top of messy job types and missing skills data, because it will make confident suggestions from bad inputs. And if your software contract renews soon, settle the platform question before building automation around it.
Common questions
Will this replace our dispatcher?
No. The aim is to take routine booking, confirmations and first-draft assignments off the dispatcher's plate. Emergencies, upset customers, warranty calls and judgment about which technician a particular customer trusts still need a person. In most companies the dispatcher becomes more valuable once they stop living on the phone.
Do we need to switch field service software?
Usually not. Most businesses on ServiceTitan, Housecall Pro or Jobber have scheduling features they have not configured. We would start by reviewing what your current system can already do, then decide whether an add-on or a different platform is actually justified.
How do we handle emergency calls?
Emergency jobs get their own job type and rules, such as which technicians are on call and which existing jobs can move. The system can flag affected appointments and suggest options, but the dispatcher decides who gets bumped and approves the messages to those customers.
What data do we need to start?
A few months of completed jobs with types, durations and assigned technicians, plus a list of each technician's skills and certifications. If that data is incomplete, the first weeks of a project are spent cleaning it, which pays off even without any automation.
How quickly would we see a difference?
Customer notification and booking changes can show results within weeks. Assignment and routing improvements take longer because job durations and skills need tuning. A 90-day pilot is usually enough to compare jobs per day and drive time against a baseline.
By industry
Job scheduling and dispatch for your industry
Commercial cleaning companies
Cover night-shift callouts faster, keep cleaning schedules current and give every cleaner clear site instructions on their phone.
See the details →Electrical contractors
Match electrical jobs to the right licensed crew, truck stock and inspection window with fewer phone calls and less rework.
See the details →HVAC companies
Put the right HVAC technician on the right job with fewer phone calls, better arrival updates and smarter use of shoulder-season capacity.
See the details →Landscaping companies
Build tighter maintenance routes, recover faster from rain days and give crew leads a clear daily plan. Fractional tech leadership.
See the details →Logistics and freight companies
Plan loads against drivers, hours of service and equipment with suggested assignments dispatchers approve. Fewer calls, fewer empty miles.
See the details →Plumbing companies
Put the right plumber on the right job with fewer phone calls. Smarter dispatch for plumbing shops using your field software.
See the details →Property management companies
Route work orders to the right vendor or in-house tech, with resident access and owner approval handled. Faster repairs, fewer calls.
See the details →Guides
Other solutions
KPI and pipeline dashboardsSoftware stack auditDocument intake and data extractionInvoicing and collections follow-upInternal knowledge assistantHiring and staff onboardingAI usage policy and governanceSystems integrationContract and document review supportCompliance documentationTechnology vendor selection
Next step
Bring one expensive workflow. Leave with a clear next step.
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
Book a 30-minute workflow review
Not ready to talk? Take the 3-minute check
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.