Picture a plumbing company on a Tuesday morning. ServiceTitan is down. Not "slow." Fully down. Eight technicians sitting in their trucks waiting for the next dispatch. Office staff calling customers manually from paper schedules. The owner has been on hold with vendor support for 40 minutes.
By the time the system comes back up two hours later, half the morning's jobs have been rescheduled. Three customers have been "no-showed" because the dispatcher couldn't reach them in time. One competitor's truck has already shown up on a call that should have been theirs.
That can easily be a several-thousand-dollar morning. And most owners never add up what downtime actually costs.
This isn't a ServiceTitan problem specifically. Housecall Pro, Jobber, FieldEdge, all of them have outages. It's a dispatch software dependency problem. When the system that schedules your trucks goes down, your business stops earning money the moment the first call queues up.
The Real Cost of Downtime
Here's an illustrative example of the math. Plug in your own numbers.
Hourly cost of an idle technician (illustrative ranges, not a local survey):
- Fully loaded labor: $45-$65/hour (wage + payroll tax + insurance)
- Truck and overhead allocation: $25-$40/hour
- Total idle cost per tech: $70-$100/hour
Now multiply by your fleet. A six-truck shop with everyone idle for two hours: $840 to $1,200 in pure idle cost , and that's before you count anything they would have earned in those two hours.
Lost revenue from missed jobs:
- Average ticket on a service call: $400-$700 depending on the season
- Skipped or rescheduled jobs per truck: about 1 for every 2 hours of downtime in peak season
- Six trucks, two hours, average ticket: $2,400 to $4,200 in delayed or lost revenue
Soft costs that don't show up on the spreadsheet:
- Customer-rebooking churn: some rescheduled customers will call a competitor instead, especially in heat-wave or cold-snap weeks.
- NPS hit: every rescheduled customer is a Google review risk. One unhappy customer venting publicly is worth weeks of reputation work.
- Office staff overtime to clean up the mess after the system is back.
- Dispatcher fatigue, which compounds into errors for the rest of the day.
Rough total for a half-day outage in this example: about $6,500-$11,000. And it happens more often than owners realize, because the small outages (30 minutes here, 90 minutes there) don't get measured. They just hurt.
3 Ways Downtime Happens
Dispatch software downtime generally falls into three buckets. Each one has a different fix.
Bucket 1: Vendor-Side Outages (ServiceTitan / Housecall Pro is Down)
This one is out of your control. Sort of. When the cloud platform itself goes down, you can't bring it back. But you can prepare for it:
- Know the status page URL for your dispatch platform. ServiceTitan status, Housecall Pro status, Jobber status are all public. Bookmark them on every office workstation.
- Have a paper-and-phone fallback plan. Yes, paper. A printed schedule of the day's jobs, customer phone numbers, and tech assignments. Every dispatcher should be able to pivot to it within 10 minutes.
- Subscribe to vendor incident notifications. Most platforms will email or SMS you when there's an active incident. The faster you know, the faster you can pivot.
- Know your contractual SLAs and remedies. Some platforms credit your account for extended outages, but you have to ask.
You can't prevent vendor outages, but you can shrink the impact. Many shops have no fallback plan at all. The first 30 minutes of any outage is wasted figuring out what's happening instead of how to keep working .
Bucket 2: ISP Outages (Your Internet Is Down)
This is the most common cause of "we can't dispatch" calls, and it's the most preventable. If your office only has one internet connection, you have a single point of failure on the most revenue-critical infrastructure in your business.
The fix is failover internet. Two ISPs, ideally on different physical paths (cable + fiber, fiber + cellular). When the primary drops, the secondary takes over within seconds. Most office staff don't even notice the switch.
Total cost for a typical small shop: $150-$300/month for the secondary connection, plus a one-time hardware spend for a dual-WAN router. Compared to one $10,000 outage, the math is obvious. And yet most shops are still single-homed.
A related issue: office wifi quality. If your dispatchers' computers are on flaky wifi instead of wired ethernet, you'll get random "ServiceTitan is slow" complaints that aren't really ServiceTitan's fault. Run cable to every desk. It costs an afternoon. It pays back in years of fewer help-desk tickets. Network problems are usually fixable . They just don't fix themselves.
Bucket 3: Software Bugs and Configuration Issues
This bucket is the sneakiest. The platform is "up" (the status page is green), but your tenant is broken. Common scenarios:
- A bad import locks up a scheduling view
- A custom workflow update broke a trigger
- A user accidentally deleted a price book entry that's referenced in 200 jobs
- An integration to your accounting platform threw a sync error and stopped writing tickets
These don't show up on the vendor status page because they're not vendor-wide. They're your problem, and the resolution depends on how fast you can get a knowledgeable hand on the keyboard.
This is where managed IT actually earns its keep. A good MSP that supports your dispatch platform fixes more than the internet. They know your ServiceTitan or Housecall Pro setup well enough to troubleshoot when your tenant breaks. They have admin access (with your blessing), they know your customizations, and they can get on the phone with vendor support immediately.
Without that support, the owner ends up on hold with the vendor at 7am, and the techs are idle until someone solves it.
What Managed IT Actually Prevents
To be clear: managed IT doesn't prevent vendor outages. Nothing does. But it dramatically reduces:
- ISP-related downtime , through failover internet and proper network monitoring that catches problems before users feel them.
- Configuration-driven outages , by managing changes, testing integrations, and acting as a knowledgeable second pair of eyes on platform updates.
- Time-to-resolution on any incident , because someone who knows your stack can get on it quickly.
- Compounding errors. Every minute of downtime increases the chance of a second issue piling on (rescheduling errors, frustrated customers, dispatcher mistakes). Fast response keeps a 30-minute issue from becoming a 4-hour mess.
The other thing managed IT brings is measurement. If you don't know how often your dispatch system is unavailable, even briefly, you can't manage it. Good managed IT monitors uptime and logs incidents so the owner actually sees the pattern.
Small, untracked outages add up, and most shops have never measured how much dispatch time they lose to them.
The Honest Take
If you run a dispatch-dependent shop in the Treasure Valley, the cost of downtime is a line item in your P&L whether you measure it or not. The shops that grow the fastest are the ones that figure out how to keep the trucks moving when something goes sideways.
That requires three things: a real fallback plan, redundant internet, and someone on call who knows your platform. None of those are expensive in absolute terms. All of them pay for themselves the first time they save you from a four-hour outage on a 95-degree day.
If you want me to walk through your specific dispatch setup and tell you where the failure points are, request a free 15-minute call and we'll talk through the likely failure points and what to fix first.
For trades-specific IT, you can also dig into my construction and HVAC playbook . Same approach, written for owners who don't have time to chase tickets.
Let's Talk
You don't need IT to be perfect. You need it to not be the reason you lost a customer today. Let's make sure it isn't.