The machine goes down on a Tuesday. Someone reports it to the office manager, who calls the number on the sticker, waits on hold, and receives a ticket number. A technician is scheduled for "within five business days." The machine comes back the following Monday. Six working days, one breakroom, one small business.
Nobody logs that as an incident, so nobody costs it. Here is what it is actually worth.
The arithmetic of six days
Take a 30-person office where 24 people drink coffee. When the machine is down, most of them do one of three things: go without, bring their own, or leave the building. The third one is the expensive one.
A café run in Burlington or Oakville realistically costs 15 to 20 minutes door to door once you count the walk, the queue and the conversation on the way back. If even eight people do that once a day for six days, you are looking at roughly 12 to 16 hours of paid time spent standing in someone else's line — plus the staff who quietly decide the office coffee situation is a joke, which is the cost that outlasts the repair.
In a dealership service lounge or a clinic waiting room, the same six days hit customers rather than staff, which is worse. See our notes on waiting-room amenities for that version of the problem.
Why the ticket takes a week
It is not usually incompetence. It is structure. A national program is built to be uniform across a very large map, and uniformity at that scale means centralisation:
- Dispatch is not local. Your call is triaged by someone with no knowledge of your building, your machine's history, or how far away the nearest technician actually is.
- The technician is often a subcontractor. National coverage is frequently stitched together from third-party service partners, so the person who arrives has not seen your machine before and may not carry parts for it.
- Parts move through a warehouse. If the fix needs a component, the clock restarts on shipping.
- Your ticket is one of thousands. Priority is set by SLA tier, not by the fact that your entire office runs on that one machine.
This is also why the service clause in the contract says "prompt" rather than a number of hours. Ambiguity is doing real work in that sentence — see our breakdown of contract red flags.
What a local route changes
We run Burlington, Oakville and Hamilton. That is a deliberately small map, and it produces three concrete differences.
Your machine is already on a schedule. A technician visits weekly to clean and restock, which means most failures get caught as symptoms — a grinder sounding wrong, a seal starting to weep, scale building where it should not — before they become a dead machine on a Tuesday.
The person who fixes it is the person who knows it. Same route, same machines, same buildings. No handover, no reading a history file, no discovering on arrival that this is a model they do not stock parts for.
The drive is short. Between Burlington and Hamilton is a matter of minutes, not a regional dispatch decision. Proximity is not a service philosophy, but it is the thing that actually determines when someone shows up.
Prevention beats response
The best downtime number is the one you never generate. Most breakroom machine failures trace back to maintenance that did not happen: milk lines that were not flushed, a brew unit never properly cleaned, scale from unfiltered water. All three are handled on a weekly visit, and all three are why we include cleaning, restocking and repair rather than selling them as a service tier. A machine we maintain badly costs us a customer with no contract to hold them.
Two questions for your current provider
How often does a human physically look at my machine, and what happened the last time it broke? If the second answer involves a ticket number, you already know what the next outage will look like.
Our free one-week trial includes the install and the service visit, so you can see the response model rather than read about it. No contract, no obligation, machine removed at no charge if it is not for you. Or just call 416-995-0577 — a local number, answered locally.