The True Cost of a Phone Outage (and How to Calculate Yours)

Every business owner knows a phone outage is bad. Very few can tell you what one actually costs them, in dollars, per hour. That gap matters, because without a number you can't make rational decisions about how much to spend preventing outages. You end up either underinsured (no failover at all, because redundancy "seems expensive") or overinsured (paying for geo-redundant trunks when call forwarding to a mobile would cover you).

This post walks through the three categories of outage cost — visible, invisible, and asymmetric — and then builds a worked example for a 20-person business so you can plug in your own numbers. We'll deliberately avoid quoting "industry average cost of downtime" figures. Those numbers are dominated by enterprise data-center outages and tell you nothing about your business. Your own math, with your own assumptions written down, is worth more than any survey.

The visible costs

These are the costs you can see happening in real time while the phones are down. They're the easiest to estimate, and they're usually the largest line items.

Missed inbound sales calls

If inbound calls generate revenue for you, this is the big one. The math is straightforward:

Lost sales per hour = inbound sales calls per hour × close rate × average deal value

You already have all three inputs, or can get them quickly:

• Inbound sales calls per hour. Pull your call logs or ask whoever answers the phone. Count only calls that could plausibly turn into revenue — new inquiries, quote requests, orders — not vendor calls or existing-ticket follow-ups.
• Close rate. What fraction of those inquiries eventually become paying customers? Your sales team or your CRM knows this. If you don't track it, estimate conservatively and write the assumption down.
• Average deal value. Revenue per closed deal, or lifetime value if a new customer typically buys repeatedly. Use whichever number you'd actually defend to your accountant.

One honest caveat: not every missed call is a lost sale, because some callers will try again later. But during an outage your phones don't ring busy-with-a-queue — they're dead. A caller who hears fast busy or endless ringing has no idea you're having a technical problem. Which brings us to the invisible costs in a moment.

Abandoned support calls and churn risk

If you provide support by phone, an outage means existing customers who need help right now can't reach you. Unlike a missed sales call, the cost here isn't a single lost transaction — it's an increment of churn risk on an existing revenue stream.

A customer who calls with an urgent problem and gets dead air doesn't file that under "stuff happens." They file it under "this vendor is unreliable," and it goes on the mental ledger they'll consult at renewal time. You can't compute this precisely, but you can bound it: estimate how many support calls you'd miss during the outage, estimate what fraction of those customers are already borderline, and multiply by the annual value of a customer. Even a small probability times a large customer value is a real number.

Idle staff

While the phones are down, you're still paying everyone whose job depends on them. A salesperson who works the phones, a dispatcher, a receptionist, a support agent — their productivity doesn't drop to zero (they can catch up on email), but it drops substantially.

Idle staff cost per hour = phone-dependent employees × loaded hourly cost × productivity loss fraction

Loaded cost means salary plus benefits and overhead — a common shortcut is wages × 1.25 to 1.4. The productivity loss fraction is a judgment call; 50% is a reasonable default for roles where the phone is the primary tool. Write down whatever you use.

The invisible costs

These costs don't show up during the outage. They show up weeks and months later, as revenue that quietly never materializes — which is exactly why they get left out of the calculation.

Callers who never call back. Some fraction of the people who got fast busy during your outage will simply move on. A prospect comparing three vendors calls the next one on the list. A new customer referral, told "just give them a call," gets no answer and lets it drop. You'll never see these losses in any report because there's no record the call was ever attempted from your side. Your provider can sometimes give you counts of failed inbound attempts during an outage — it's worth asking, because that number is usually higher than people expect.

Reputation damage. The prospect who couldn't reach you tells the person who referred them. A customer mentions in a review that "they're impossible to get on the phone." Each individual incident is small; the compounding effect is not. Reputation is expensive to build and cheap to lose, and phone reachability is one of the most basic trust signals a business has.

Callers who assume you went out of business. This one sounds dramatic but it's real, especially for outages that span a day or more. A disconnected-sounding phone line is the classic signal of a business that has folded. An occasional customer who calls twice, a week apart, and gets dead air both times will reasonably conclude you're gone — and unlike the impatient prospect, they won't check your website to confirm.

You can't put precise numbers on these. The honest approach is to add an uncertainty allowance on top of your visible costs — 25 to 50% is defensible — rather than pretending the invisible costs are zero, which is the one estimate you can be certain is wrong.

The asymmetric costs

The first two categories scale roughly linearly with outage duration. This third category doesn't. These are low-probability, high-severity events where a single incident during a single outage can dwarf everything else on the list.

A missed emergency call. If your business fields calls where the stakes are safety or health — a medical practice, a property manager with a gas leak on the line, an HVAC company in a heat wave, a security monitoring firm — one missed call can carry consequences measured in liability and harm, not in average deal values. No hourly cost model captures this. If it applies to you, it's a reason to be at a higher failover tier regardless of what the spreadsheet says.

SLA penalties you owe your own customers. This one is easy to overlook and especially relevant for MSPs and anyone reselling voice services. If you've signed uptime commitments with your customers, your provider's outage becomes your SLA violation. You owe credits — or worse, you've given an anchor customer contractual grounds to leave. Note the asymmetry: the credits you owe downstream are governed by your contracts, while the credits you receive upstream are governed by your provider's. Those two numbers were never designed to match, and they don't.

Compliance exposure if 911 is unreachable. In the US, Kari's Law and RAY BAUM'S Act impose requirements around 911 access and dispatchable location for multi-line phone systems. If your phone system is down and someone in your building can't reach 911, you have a problem that is categorically different from lost revenue. This is another factor that should push safety-relevant environments toward faster, more automatic failover — the kind measured in seconds, not in someone noticing and forwarding calls manually.

Why your provider's SLA credit won't cover any of this

It's tempting to think of your provider's SLA as insurance against outage costs. It isn't, and it was never designed to be.

As we covered in detail in SLAs: The Contract Language That Actually Matters, service credits are calculated as a percentage of your monthly bill per increment of downtime — and capped, typically at 30 to 100% of one month's charges. The credit is indexed to what you pay the provider, not to what the outage costs you. If your phone service costs $600 a month and an outage costs you $1,000 an hour, the best possible outcome under most SLAs — the full cap — recovers well under one hour of your actual losses. And you usually have to notice the violation, document it, and file a claim within a deadline to get even that.

SLA credits exist to give the provider a financial incentive to hit their targets. They are not a remedy for your business impact. The remedy for business impact is redundancy, and redundancy is something you have to budget for yourself — which is exactly why you need the number we're about to calculate.

A worked example: 20-person business

Let's put the pieces together for a hypothetical 20-person company — a distributor, an agency, a service firm, take your pick. Every assumption is labeled; replace each one with your own figures.

Assumptions:

• 40 inbound calls per 8-hour business day, of which 10 are potential sales inquiries
• Close rate on phone inquiries: 20%
• Average deal value: $2,500
• 12 of the 20 employees are phone-dependent, at an average loaded cost of $45/hour, losing 50% productivity during an outage
• 8 support/service calls per day from existing customers, average customer worth $6,000/year, and we'll say a badly-timed missed call adds a 2% chance that customer eventually churns

Missed sales: 10 sales calls ÷ 8 hours = 1.25 sales calls per hour. 1.25 × 20% × $2,500 = $625 per hour.

Idle staff: 12 × $45 × 50% = $270 per hour.

Churn risk: 8 support calls ÷ 8 hours = 1 per hour. 1 × 2% × $6,000 = $120 per hour in expected value.

Visible subtotal: about $1,015 per hour. Add a 30% allowance for the invisible costs — the callers who never retry, the reputation dings — and you land at roughly $1,300 per hour of downtime.

So a four-hour outage costs this business somewhere around $5,300. A full-day outage costs over $10,000. Meanwhile, if their phone service runs $500/month, a typical SLA credit for that four-hour outage might be $100, capped well below one month's bill. The gap between those two numbers — $5,300 of loss against $100 of credit — is the entire argument for doing this exercise.

Your numbers will differ, possibly by a lot. A business where the phone rarely rings might land at $150/hour; a busy inbound sales operation might land at $5,000. That's precisely the point: the spend that's rational for one is irrational for the other, and only the calculation tells you which one you are.

Using the number: right-sizing your failover spend

Here's where the number earns its keep. Redundancy budgeting is a business decision, not a technical one — and your outage cost per hour is the input that turns "how much redundancy should we buy?" from a matter of taste into arithmetic.

The comparison works like this:

Expected annual outage cost = cost per hour × expected hours of downtime per year

For the downtime estimate, look at your own history: how many outages did you have in the last two or three years, and how long did they last? A single ISP connection with no backup might realistically see 8 to 20 hours of downtime per year between ISP outages, equipment failures, and upstream problems — but use your actual track record, not our guess. (For what an outage actually does to your phones minute by minute, see What Happens to Your Phones When the Internet Goes Down.)

For our example business at $1,300/hour, even a conservative 8 hours of annual downtime is roughly $10,000 of expected annual loss. Against that:

• Free call forwarding to mobile (Tier 1 in our failover architectures guide) costs nothing and recovers most of the inbound-sales losses. It should be configured before you finish reading this.
• A cellular backup connection at $50-100/month — call it $1,000/year with hardware — eliminates most of the remaining exposure. Against $10,000 of expected loss, that's not a close call.
• Dual WAN with automatic failover at a few thousand per year still pays for itself comfortably for this business — but might not for the $150/hour business, which is exactly the kind of distinction the number lets you make.
• Geo-redundant trunking at $12,000+/year is hard to justify at $1,300/hour on financial grounds alone. It becomes justifiable when the asymmetric costs apply — emergency calls, downstream SLAs, compliance — or when your hourly number is several times higher.

Two closing disciplines make the whole exercise durable. First, revisit the calculation annually; call volumes, deal sizes, and headcount all drift, and the failover tier that was right two years ago may be wrong now. Second, whatever failover you deploy, verify it actually works — including running a VoIP quality test over the backup path so you know it can carry your call volume before the day you need it.

The businesses that get this right aren't the ones that spend the most on redundancy. They're the ones that know their number.