What's usually included
- Turning web form requests, booking-widget entries and emailed requests into scheduled jobs with complete customer and site details.
- Confirming appointment windows the day before, by text or email through your software, and logging the reply.
- Collecting the details techs actually need: equipment age and brand if known, access notes, gate codes, pets, parking, whether a tenant or landlord must approve.
- Rebuilding the board after cancellations, no-shows, sick techs or a job that runs long, and telling affected customers.
- Flagging jobs that are waiting on parts or a permit so they don't get booked too early.
- Keeping job types, durations and tags consistent so your reports mean something.
The rules you write down first
Remote dispatch only works when the decisions a good office manager makes by instinct are written as rules. Before handover, settle these:
| 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 a back-office task. A customer reporting a gas smell, sparking or flooding should be told to follow the utility's or emergency services' instructions and routed to you at once. Put that rule at the top of the playbook.
Tools this is commonly 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 with their own user account. Shared inboxes, the booking widget on your website and your text-messaging tool are usually part of the setup too. If your shop still runs on a paper calendar and a whiteboard, the first job is often moving active customers into a system, which is a project in itself.
Hours and handover
Decide which hours the remote team covers and what happens outside them. A common pattern: the support team handles everything that arrives in writing during business hours and builds the next day's board by late afternoon; after-hours emergencies stay with the owner or an on-call tech. Write down how a job is handed over (a note in the job record, not a text to the tech's personal phone) so nothing lives only in someone's head.
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 much volume swings between them.
- Who on your side approves exceptions, and how fast they answer.
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 habit matters more than the dispatcher.
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