A Quarter of Your Downtime Doesn’t Need a Truck

QUICK ANSWER. More than 25% of coffee machine downtime can be resolved without a technician visit — when support can actually see the machine. Most operators dispatch anyway, because a support agent working from the customer’s description has only one safe option: send a truck. That makes the most expensive response the default response.

Think about how a downtime call works in a typical coffee operation today.

A customer calls: “the machine isn’t working.” The support agent asks what the display says. The customer reads something back, or doesn’t. The agent logs a ticket, makes a judgment call with almost no information — and books a technician.

That sequence repeats hundreds of times a month across a fleet. In a European market that EVA counts at roughly 4.5 million installed machines across 24 markets, it is one of the most quietly expensive routines in the industry.

Why does support always send a truck?

Because when you can’t see the machine, dispatch is the only safe answer. The agent doesn’t know whether the fault is a descaling need, an empty water line, a settings issue or a genuine component failure. Guessing wrong means an angry customer and a second call. Sending a technician means the problem becomes someone else’s — at the cost of a truck, a technician-hour and a day of downtime.

The economics are upside down:

• The cheapest possible resolution is the one that happens during the first phone call.
• The most expensive resolution is a site visit.
• Without machine visibility, the most expensive option becomes the default.

This is pain point number one in our work with operators: troubleshooting runs on the customer’s description, not the machine’s data. It’s the same blind spot that hides machine-level profitability — see Which Machines Actually Make You Money?

What does the 25% number actually mean?

Public operator experience shows that more than 25% of downtime can be resolved without a technician visit when support can see the machine’s live status: error codes, temperatures, cleaning cycles, usage patterns.

Read that as an operations leader. A quarter of your downtime events could end:

• Without a truck rolling
• Without a technician-hour consumed
• Within minutes instead of days
• With the customer back to serving coffee the same morning

And every remote fix frees a technician-hour for the failures that genuinely need hands on the machine — the ones threatening your SLA and your busiest accounts.

What changes when support can see the machine?

The support role itself changes. Instead of taking messages and booking technicians, the agent opens the machine’s live view while the customer is still on the phone. Many faults turn out to be guided-resolution cases: a cleaning cycle, a water supply check, a settings reset — walked through in one call. “A technician will come Thursday” becomes “let’s fix it right now, together.”

The measurement changes too. A support function measured on call handling time is optimized for ending conversations quickly. A support function measured on resolution impact — how much downtime it removes without dispatch — is optimized for exactly what the P&L needs. That shift, from message-takers to remote problem-solvers, is Step 1 of the 9-step operating model in our report. The full workflow and the KPI set that goes with it are in the report — deliberately not in this article.

Why do operators find out about this last?

Because nothing in the standard toolset exposes it. The ticket system counts tickets. The ERP counts work orders and invoices. Neither can say: “this dispatch was avoidable.” The cost of blind support never appears on a report — it’s distributed across hundreds of truck rolls that each looked reasonable at the time.

That’s also why the leakage compounds with scale: more machines, more calls, more default dispatches. The same scale logic applies to lost coffee sales — the subject of Revenue Leakage: The Coffee Sales You Lose Without Noticing.

Key takeaways

• Support without machine visibility has one safe option — dispatch, the most expensive option.
• Public operator experience: more than 25% of downtime can be resolved without a technician visit.
• Every remote fix returns a technician-hour to the failures that actually need one.
• Measure support on resolution impact, not call handling time.
• The remote-resolution workflow is Step 1 of From Coffee Machines to Profit Machines.

How many of last month’s truck rolls would have survived a support agent who could see the machine?
Request the white paper — From Coffee Machines to Profit Machines: a step-by-step model for a more profitable OCS operation.