What remote dispatch support usually includes
- Turning web form requests, booking-widget entries and emailed requests into scheduled jobs with full customer and site details.
- Confirming appointment windows the day before, by text or email through your software, and logging the reply.
- Collecting what techs actually need to know: equipment age and brand if known, access notes, gate codes, pets, parking, and whether a tenant or landlord has to approve.
- Rebuilding the board after cancellations, no-shows, sick techs or a job that runs long, and letting affected customers know.
- Flagging jobs that are waiting on parts or a permit so they aren't booked too early. The permit and inspection tracker feeds this.
- Keeping job types, durations and tags consistent so your reports mean something.
Dispatch rules to write down before handover
A good office manager makes most dispatch decisions by instinct. A remote dispatcher needs them written as rules. Settle these first:
| Decision | Example rule to agree |
|---|---|
| Which tech gets which job | Only two techs do tankless water heaters; new hires don't get commercial rooftop units. |
| Job durations | Drain clearing 1.5 hours, system replacement full day, maintenance visit 1 hour. |
| What counts as an emergency | No heat below a set outdoor temperature, active leaks, no water; these jump the queue and go to the owner first. |
| What can be said about price | Quote the trip or diagnostic fee only; never estimate repair cost over text. |
| When to escalate | Upset customer, warranty dispute, any request for a discount, anything involving gas smell or electrical burning. |
Safety calls are not back-office work. A customer who reports a gas smell, sparking or flooding should be told to follow the utility's or emergency services' instructions, and the call goes to you at once. Put that rule at the top of the playbook.
Field-service software the work is done in
Most shops already run a field-service management platform with a dispatch board, customer records and automated reminders. The support team works inside it under their own user account. Shared inboxes, the booking widget on your website and your texting tool are usually part of the setup as well. If your shop still runs on a paper calendar and a whiteboard, the first job is often moving active customers into a system, and that's a project of its own.
Coverage hours and job handover
Decide which hours the remote team covers and what happens outside them. One common pattern: the support team handles everything that arrives in writing during business hours and has the next day's board built by late afternoon, while after-hours emergencies stay with the owner or an on-call tech. Write down how a job gets handed over. A note in the job record works; a text to the tech's personal phone doesn't, because then the information lives only in someone's head.
Dispatch scoping checklist
- Number of techs and trucks, and how many jobs a typical day holds.
- Where requests come from: web form, booking widget, email, a rented answering service.
- Your field-service software and whether it supports separate user roles.
- Peak seasons and how far volume swings between them.
- Who on your side approves exceptions, and how quickly they answer.
Dispatch often pairs with booking maintenance agreement visits, since both draw on the same open slots.
Remote dispatch FAQ
Can a remote team see where my techs are?
Only if your software has GPS or status tracking and you give their user that permission. Many shops share job status (en route, on site, done) but not live location.
What if a tech changes the plan in the field?
Ask techs to update job status and notes in the app. The dispatcher works from what the system shows, so the techs' habit matters more than who is dispatching.
Does a remote dispatcher take emergency calls?
Not by default. The usual setup has the support team handle requests that come in writing during covered hours, with emergencies and anything safety-related going straight to you or your on-call tech.
Want this off your desk? Tell us which tickets you'd hand over first and roughly how many jobs you run a week.
Request a quote