Not All Downtime Is Equal: Why Your Dispatch Queue Is Costing You Money

QUICK ANSWER. Most coffee operators run service dispatch by ticket order and whoever shouts loudest. But a machine down in your biggest account is not the same as one in a quiet corner. Dispatching by value — revenue at risk, business criticality, profitability — instead of arrival time is one of the cheapest ways to protect margin.

Every service team has a queue. The question is what decides its order. For most operators the answer is: whoever called first or complained loudest. That feels fair. It’s also expensive.

What does “not all downtime is equal” mean?

Two machines go down at the same moment. One serves four hundred cups a day in your largest, most profitable account. The other serves forty in a site that barely breaks even. Same “machine down” ticket. Wildly different cost of leaving it down. Treating them the same — first in, first out — quietly burns money every single day, because the real cost of downtime isn’t the repair; it’s the lost revenue and the customer relationship behind it.

Why is dispatching by ticket order costing you?

Because ticket order ignores everything that matters: which account is critical, which machine is profitable, how much revenue is bleeding per hour. A dispatcher working blind can only sort by time and urgency-as-described. So a trivial fault in a small site can pull a technician away from a high-value machine that’s been down for hours. The queue is busy. It just isn’t working on the right things.

A dispatch queue sorted by arrival time is sorted by the wrong thing.

How should coffee operators prioritise service?

By value at risk, not arrival time. The machines that jump the queue should be the ones where downtime costs the most:

• Revenue at risk — how much a given machine earns per hour it’s down.
• Business criticality — flagship accounts, SLA commitments, reputation exposure.
• Profitability — the machines and contracts that actually make you money.
• Fix confidence — whether it can be resolved on the first visit, with the right part.

What data makes value-based dispatch possible?

You can’t prioritise by value if you can’t see value. That takes machine status, contract, consumption and cost joined in one source of truth. So the dispatcher sees not just “machine down” — but “machine down, top-decile account, revenue at risk per hour, part in the nearest van.” This is exactly what CoffeeBrain is being built to surface. The platform is in development now, with first pilots planned for Q4 2026.

Can some downtime skip dispatch entirely?

Yes — and that’s the biggest win of all. More than 25% of machine downtime can be resolved without sending a technician, diagnosed and cleared remotely. Clearing the trivial faults remotely frees the queue for the machines that genuinely need a visit. Pair that with first-time fix and the technicians you do send arrive prepared.

Key takeaways

• A “machine down” ticket says nothing about how much that downtime costs.
• Dispatching by ticket order pulls technicians toward the wrong machines.
• Prioritise by value at risk, criticality and profitability — not arrival time.
• Value-based dispatch needs machine, contract and cost data in one place.
• Resolve trivial faults remotely to free the queue for what matters.

Your queue is busy. But is it working on the right things?