Dispatch: tech schedules, one tech per job, and vans as resources
Add vans and equipment as resources, and give every job one assigned tech.
Read the lesson
Goal: Run dispatch from one ServiceAgent calendar. Assign every job to a tech, get job details to techs without a login, and add vans as resources.
You need: The calendar set up from lessons 1 to 4. A list of techs, crews and vehicles. Growth if every tech needs a login.
Why this matters
Dispatch decides who goes where. Done well, the right tech arrives with the right van and parts. Done badly, two crews go to the same house, and one customer waits all day.
The most common dispatch failure is not software. It is two schedules. The calendar says one thing. The dispatcher's whiteboard says another. A crew follows the whiteboard to the wrong job. Two schedules always drift apart.
The rule for this lesson: one schedule, on the calendar, where the whole office sees every job.
Dispatch also costs real money in office time. A dispatcher's median US pay is $46,620 a year. Every hour spent copying between a whiteboard and a calendar is an hour not spent fixing the day.
How assignment works in ServiceAgent
Each appointment has one Assigned To field. It holds one team member. There is no crew assignment with several people on one appointment.
So you need clear rules:
- One tech per job. Assign that tech.
- A crew of two or more. Assign the crew lead. Write the helper's name in the appointment notes.
- A tech must have a login to be assigned. Core has only 2 users. The Operator's login is one of them.
That last rule shapes the plan. A fleet on Core cannot assign jobs to techs who have no login. There are two fixes:
- Move to Growth, which has unlimited users. Each tech gets a login and can be
Assigned To. - Stay on Core and send each job to the tech by text or email. Build a workflow on
Appointment Scheduledthat sends the job details.
A mobile app for techs is coming soon to ServiceAgent. Until then, use one of these two methods.
Getting jobs to techs
- 2 users; the Operator takes one
- Most techs have no login
- Job text or email by workflow on Appointment Scheduled
- Unlimited users
- Every tech has a login
- Assigned To in Jobs
Vehicles as resources
Vans and trucks can be added as resources. Go to Jobs → Manage Resources → Calendar Resources → Add Resource. Pick the type Vehicle. The fields are Name, Type, Description and Capacity.
Add each van once, with a clear name such as "Van 7, ladder rack". How a resource attaches to one appointment was not confirmed in the app check. Check how resources show on bookings in the client's account before you promise van scheduling to the owner.
Do not add hand tools or small equipment as resources. Too much detail clutters the calendar and nobody keeps it current.
Adding a van as a resource
Add Resource
Reading the board
Jobs gives the dispatcher what a whiteboard did, with more detail:
| Tool | Use in dispatch |
|---|---|
Day view | Today's board, by person |
Week view | Plan the week and spot overloaded techs |
List view | Every job in order, good for calls |
Filter Staff | One tech's day |
Filter Status | Find Scheduled jobs not yet Confirmed |
Filter Location | One branch's jobs |
Color by Service | See the mix of work at a glance |
Block Time | Time Off or a Break for one person |
Statuses move a job through the day: Scheduled, Confirmed, In Progress, Completed, No Show, Cancelled.
A job through the day
- 1ScheduledBooked
- 2ConfirmedOffice marks it after the reply
- 3In ProgressTech starts the job
- 4CompletedFeeds review requests and the survey
Build it in ServiceAgent
- List every tech, crew and vehicle with the dispatcher.
- Check the plan. If techs need logins on Core, decide with the owner: Growth, or job texts by workflow.
- On Growth, invite each tech in
Settings→Team & Access→Team members & invites. - On Core, build the job text.
Workflows→Build from scratch.Trigger Type:Event Trigger→Appointment Scheduled. Add aSend SMSstep with the job details. Type the tech's phone number in its recipient field, "Enter a recipient". - Add each van in
Manage Resourceswith the typeVehicle. - Check how a resource shows on a booking in this account. Write down what you find.
- Set up
Color by Serviceso the board shows the mix of work. - Agree on status rules. Who marks
In Progress, and who marksCompleted? - Book three test jobs for different techs. Check each tech sees their job, by login or by text.
- Retire the whiteboard. Agree a date with the dispatcher. From that date, only the calendar counts.
Check it works: every test job has one Assigned To. Each tech received their job details. The dispatcher can run tomorrow from Day view alone.
The dispatcher's day
Give the dispatcher a simple rhythm. It replaces the habits the whiteboard held.
- Before 7 am. Open
Dayview. Check every tech has a full, sensible day. CheckBlock Timefor anyone off. - First hour. Watch statuses. Each first job should move to
In Progress. A tech with no status by 9 am gets a call. - During the day. Handle changes. Text the customer first, then move the job.
- Afternoon. Run the no-show routine from lesson 6 for tomorrow.
- End of day. Every finished job is
Completed. Completed jobs feed reports and review requests, so this step matters.
The dispatcher's day
- Before 7 amDay view: every tech has a full, sensible day
- First hourFirst jobs move to In Progress
- 9 amCall any tech with no status yet
- During the dayText the customer first, then move the job
- AfternoonNo-show routine for tomorrow
- End of dayEvery finished job is Completed
For a multi-location business, each branch dispatcher runs this rhythm with the Location filter. One person checks each branch at the end of the day.
Status matters beyond dispatch
Statuses feed other builds. Appointment Completed is the trigger for review requests and the post-service survey. If techs never mark jobs Completed, those workflows never fire. So agree on who marks it, and check it daily for the first month. After that, a weekly check is enough. Look for any day where completed jobs are far fewer than booked jobs. That gap usually means a tech forgot, not that the work was skipped. Fix the habit with that tech the same week.
Same-day changes
Days change. An emergency pulls a tech off a booked job. A van breaks down. The dispatcher moves jobs in Jobs, and the customer must hear about it.
Text the customer the new time from Conversations before the old arrival window starts. A one-minute text saves an angry call later. Then move the appointment, so the reminders follow the new time.
Worked example: Polar Air Services
Polar Air Services has about 20 techs on Growth. Example inputs: 18 vans. The lead dispatcher keeps a whiteboard next to the calendar. Twice this month, the two disagreed, and a crew went to the wrong job.
You count the cost of the copying. The dispatcher spends about 45 minutes a day keeping the whiteboard and calendar in step.
- Minutes a month: 45 x 22 working days = 990 minutes
- Hours a month: 990 / 60 = 16.5 hours
- Hourly cost at the median dispatcher pay: $46,620 / 2,080 hours = about $22.41
- Monthly cost: 16.5 x $22.41 = about $370
The cost of two schedules at Polar Air
That is the cost before the two wrong trips. Polar Air is on Growth, so each of the 20 techs gets a login. Each job has one Assigned To. You add the 18 vans as Vehicle resources. The dispatcher uses Day view with Color by Service. On an agreed Monday, the whiteboard comes down.
Polar Air's dispatch, before and after
- Calendar plus a whiteboard
- 45 minutes a day of copying
- 2 wrong trips this month
- One schedule in Jobs
- Each job has one Assigned To
- 18 vans as Vehicle resources
- Whiteboard retired
How business size changes dispatch
An owner-operator dispatches themselves. They need a clean Day view on their phone and nothing else. A small Core team of 3 to 6 often cannot give every tech a login. Job texts by workflow are the practical fix. A fleet like Polar Air needs logins, statuses and vehicles. A multi-location business needs the Location filter and a dispatcher per branch, all on the same calendar.
Common mistakes
- Keeping a second schedule. Whiteboards and spreadsheets drift. Keep one schedule on the calendar.
- Promising crew assignment. One
Assigned Toper job. Put helpers in the notes. - Forgetting the Core user limit. Techs without logins cannot be assigned. Use Growth or job texts.
- Adding every tool as a resource. Add vans and large equipment only.
- Moving a job without telling the customer. Text first, then move it.
Do this now
For one roster fleet, write the dispatch setup in 6 lines. Cover the plan and how techs get jobs. Add the vehicles and the dispatcher's views. Name who marks statuses, and the date the old board retires.
Practice the conversation
- Owner My dispatcher loves their whiteboard.
- Operator I get it. It's fast. But it disagreed with the calendar twice this month.
- Owner That was a bad week.
- Operator It cost two wrong trips and about $370 of their time in copying.
- Owner So what replaces it?
- Operator The calendar's day view. Every tech, every job, color by service.
- Owner Do my techs need logins?
- Operator On Growth, yes, and they're included. Each job then has a named tech.
- Owner What about the vans?
- Operator We add each van as a resource. I'll check how they show on bookings in your account first.
Quick check
- An HVAC fleet with about 20 techs uses the ServiceAgent calendar. The dispatcher also keeps a whiteboard. Twice this month, the two disagreed and a crew went to the wrong job. What is the fix?
- Update the whiteboard first, then copy it to the calendar each night
- Add every hand tool as a resource, so the calendar shows more detail
- Give each dispatcher a whiteboard to check against the calendar
- Keep one schedule on the calendar, and retire the whiteboard
- A plumbing shop on Core has the owner and 6 techs. You run the account with your own login. The techs have no logins. How do they get their jobs?
- Share your Operator login with all the techs
- Add them as free extra users on Core
- Move to Growth for logins, or text each job to the tech by workflow
- Keep jobs on paper until the tech app arrives
- A roofing job needs a crew of three. How do you record it?
- Put all three names in `Assigned To`
- Assign the crew lead, and write the other two names in the notes
- Create three copies of the appointment
- Add the crew as a `Vehicle` resource
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.