In 60 Seconds
- •Windshield Time = Death: Every minute a tech spends driving is a minute they aren't billing. Your goal is to minimize 'Inter-Job Travel'.
- •Zone Dispatching: Divide your city into Zones (NW, NE, SW, SE). Assign Tech A to Zone NW. Do not send him to SE unless it's a dire emergency.
- •Skill-Based Routing: Don't send the 'Apprentice' to the 'Complex Boiler Repair'. The software should block that assignment.
- •The 'Arrival Window': Stop giving exact times ('10:00 AM'). Give windows ('8-12', '12-4'). It gives the dispatcher flexibility to shuffle the Tetris blocks.
- •GPS Integration: Tracking the trucks ensures you know who is *actually* closest, not just who is scheduled to be closest.
In the Service industry, Logistics is Profit.
If Tech A drives 15 minutes between jobs, he profits. If Tech A drives 45 minutes between jobs, he breaks even.
Dispatching is not just "putting a name on the board." It is an optimization problem.
The Strategy: Zone Defense
Do not treat the city as one big blob.
- Create Zones: Zip code clusters.
- Assign Primaries: Tech Mike owns the "West Side." Tech Steve owns the "East Side."
- The Rule: If a call comes in for the West Side, Mike gets it. If Mike is full, push it to tomorrow. Only cross the lines for "VIP Emergency" calls.
Capacity Planning (The Heatmap)
Modern software (ServiceTitan/Sera) has "Capacity Planning."
[!TIP] The Surge Revenue Opportunity: Don't just fill your schedule; optimize it. When your schedule is 85% full, increase your "Emergency Surcharge" or "Premium Dispatch Fee." This ensures that the last remaining slots go to the highest-margin Emergency Services.
- Green Day: Schedule is open. Open up wide windows.
- Red Day: Schedule is tight. Shrink windows. Increase prices (Surge Pricing).
Common Mistakes
- Pinballing: Sending a tech North, then South, then North. It kills morale, burns gas, and increases the likelihood of an accident.
- Overbooking: "Just squeeze it in." Now the tech is late for the next 3 customers, and you've triggered a round of bad reviews for punctuality.
- Ignoring Skill Levels: Sending a maintenance rookie to a complex system diagnostic. You'll end up sending a senior tech anyway, doubling your labor cost for a single job.
Verification Checklist
- Zone Enforcement: 90% of jobs are assigned to technicians within their primary or secondary zones.
- Real-Time GPS: Dispatchers can see live truck locations and traffic conditions via integrated mapping (Google Maps/Waze).
- Window Accuracy: Customers receive an automated "On My Way" text with a live tracking link when the tech starts the job.
- Skill Tagging: Every service type is correctly mapped to tech skill levels within your Automation Architecture.
FAQ
Q: Should I track my techs' personal driving? A: Focus on "Arrival Accuracy" rather than spying. GPS tracking protects the tech from false customer claims of "He never showed up" and helps you optimize your Response Protection layer.
Q: How many jobs can a tech handle in a day? A: For maintenance, 4-6. For complex diagnostics/repairs, 2-3. If you try to push past this, quality drops and safety risks rise.
Q: Does fuel cost really matter that much? A: In a fleet of 10 trucks, reducing drive time by just 15 minutes per tech per day saves over $20,000 per year in fuel and vehicle wear alone—not counting the extra billable hours.
Conclusion
Dispatching is either a profit center or a drain. At Max Digital Edge, we build the logistics engine that ensures your trucks are moving toward money, not just moving.
Read Next in This Hub:
- Technician App Logic - The other side of dispatch.
- Job Costing - Measuring the profit.
- API Integrations - Connecting the pieces.
Related System:
- Automation Architecture - The software setup.
- Response Protection - Setting the windows.