Operations · Playbook

How to set up dispatching for a service business

From paper schedule and personal phone to a real dispatch operation. Skill matching, on-call rotation, real-time communication, and how to know when you need a dedicated dispatcher.

Dispatching looks like calendar work to outsiders. It's actually a real-time decision-making job that combines logistics, customer service, and crew management. This playbook is for operators going from "I do dispatch in my head" to a real dispatch operation that scales past 5 trucks.

The phases

  1. Phase 1

    Define what good dispatch looks like for your business

    Week 1

    Before installing software, decide what dispatch should achieve in your business:

    - Skill matching: every job goes to a tech with the right skills (HVAC vs plumbing, residential vs commercial, install vs service) - Geography: routes optimize drive time within crew capacity - Customer history: dispatcher sees prior visits, equipment installed, payment status before assigning - Communication: customer gets on-the-way SMS, dispatcher can text/call any tech from inside the dispatch view - Real-time visibility: live tech status (en route, on site, done) without phone tag - Emergency routing: after-hours calls auto-route to on-call tech with customer history pre-loaded

    Make a list of which of these matter most. Different trades emphasize different things — emergency-heavy plumbing prioritizes on-call rotation; recurring-heavy lawn care prioritizes route density.

    Checkpoints

    • Priority list of dispatch capabilities for your operation
    • Current state documented: where dispatch breaks today
  2. Phase 2

    Pick the right software and set up the basics

    Week 2

    Pick FSM software that includes a real dispatch board (not just a calendar). The minimum capabilities:

    - Drag-and-drop calendar with crew columns and time rows - Skill tags on techs and on jobs - Customer record one-click accessible from the dispatch view - Real-time tech status (live map or status indicators) - Two-way SMS integrated, not separate - Mobile app for techs with offline support

    Set up:

    1. Tech profiles: name, skills (HVAC certified, EPA 608, master plumber, etc.), territory, schedule. 2. Service types: each service category tagged with required skills. 3. Customer records: import existing customer book. 4. On-call rotation: define shifts (Tech A: weeknights, Tech B: weekends, etc.). 5. Default views: dispatch sees today + tomorrow; office sees full week; tech sees today only.

    Checkpoints

    • FSM software with dispatch board live
    • Tech profiles with skills configured
    • Service types tagged with required skills
    • On-call rotation defined
  3. Phase 3

    Run for 30 days and refine

    Month 2

    The first 30 days reveal what your dispatch process actually needs:

    - Patterns in skill mismatches: which jobs got assigned to wrong techs? Adjust skill tags or training. - Route inefficiencies: which days had unusually high drive time? Adjust route density or geographic clustering. - Customer-communication gaps: which on-the-way SMS didn't fire? Where did "where are you?" calls happen? - Tech load imbalance: are some techs constantly overloaded while others have slack?

    Most operators discover their original process had 3-5 dispatch decisions that were happening implicitly (in the owner's head) that need to be made explicit in the software. Examples:

    - "Bob always handles the elderly customers" — this needs to be documented in the customer record so dispatch can route to Bob automatically. - "Don't schedule new installs on Friday" — this needs to be a dispatch rule, not tribal knowledge. - "Emergency calls during lunch get routed to whoever finishes their current job soonest" — make this a rule.

    After 30 days you should be running with measurable improvements in: drive time per crew, first-time fix rate, customer-satisfaction proxies (review scores, complaint rate).

    Checkpoints

    • Drive time per crew measured and trending down
    • First-time fix rate measured
    • Customer no-show / wait-issue complaints trending down
    • Tech load balanced
  4. Phase 4

    Hire a dedicated dispatcher (when ready)

    Month 3+

    In a 1-3 truck operation, dispatching is part of the owner's job. By 5+ trucks, dispatching becomes a full-time role. The transition typically happens between trucks 4-6.

    Signs you're ready for a dedicated dispatcher:

    1. You're spending 4+ hours/day on dispatch: that's a full-time job hidden in your day 2. Reactive scheduling: you're moving jobs around constantly because the calendar gets stale 3. Customer wait times growing: callbacks not happening, customers not getting status updates 4. Tech communication friction: techs calling you instead of dispatch when problems arise

    Hire profile: ideally a former tech (understands the trade, can match skills correctly), good phone presence, organized, calm under pressure.

    Compensation: typically $50K-$80K for residential service operations, $80K-$120K for commercial / multi-trade operations.

    Checkpoints

    • Dispatcher role defined and posted
    • First dedicated dispatcher hired and trained
    • Owner's dispatch time drops from 4+ hours/day to 0-1 hour/day
    • Operation can scale to truck #6, #7, #8 with the same dispatch overhead

Common pitfalls

  • Skipping skill tags because 'all my techs can do anything'

    Wrong-tech assignments are the largest single source of return visits. Even within HVAC, there are sub-specialties (heat pump, gas, mini-split). Tag and dispatch with discipline.

  • Doing dispatch in your head and never writing it down

    Dispatch knowledge that lives only in the owner's head doesn't scale and doesn't survive vacations. Make decisions explicit in the software.

  • Hiring a dispatcher who's never done the trade

    A dispatcher who can't tell which jobs are emergencies vs which can wait creates more chaos than they solve. Former techs make the best dispatchers.

  • Adding more software instead of fixing the process

    If your dispatch is broken on paper, it's broken in software too. Define the process first, then automate it.

What good looks like

  • Drive time per crew under 25% of total work hours
  • First-time fix rate above 75%
  • Customer 'where are you?' calls under 5% of dispatched jobs
  • Owner spends under 1 hour/day on dispatch
  • Operation scales to 8+ trucks with stable dispatch overhead

Frequently asked

Ready to see what an honest tool feels like?

Start your 14-day free trial. No credit card. Cancel anytime.