The 11-Crew Bottleneck: How a CEE Field-Service Operator Rebuilt Dispatch Without Adding Headcount

We first heard about this project from a reader in the Brno region who runs a mixed-trade field crew — HVAC, plumbing, and light electrical — and had been quietly furious about dispatch for two years. His complaint was not unusual. What made us follow the story was the ending: 11 crews, no new hires, and a scheduling stack rebuilt around a platform most North American readers have never heard of. Here is the timeline, including the parts that went badly.

The situation, as we reconstructed it

The operator — we will call it the pilot company, since anonymity was a condition of the interviews — had grown from four vans to eleven between 2019 and 2023. Revenue roughly tripled. Dispatch did not scale with it. Two dispatchers were handling roughly 340 jobs a week across three languages, with Czech and Slovak field techs on one side and German-speaking commercial clients on the other. The scheduling system was a shared calendar plus a WhatsApp group plus a whiteboard in the office hallway. Everyone knew it was fragile. Nobody wanted to be the person who broke it by changing it.

Our reader's own data, pulled from three months of job tickets, showed the real cost: an average of 41 minutes of unbilled drive time per technician per day, and a first-time-fix rate of 71 percent. Both numbers were worse on Mondays.

The decision point: buy more people or buy more routing

In early 2024 the pilot company ran a two-week experiment. It hired a third dispatcher on a temporary contract and let the existing two work with the new hire as a control. The result was almost funny: throughput rose 6 percent and drive time fell 4 percent. Not nothing, but nowhere near enough to justify the salary. That was the moment the owner decided the problem was structural, not staffing. He started evaluating dispatch software.

The evaluation criteria were narrow and, we think, correct:

• Multi-language call handling, because German-speaking clients were the highest-margin accounts and the ones most likely to churn after a single bad scheduling experience.
• Hybrid payment support — some crews took cash on site, others invoiced net-30, and the system had to reconcile both without a spreadsheet.
• Routing that respected trade-specific constraints, not just shortest distance. An HVAC call and an electrical call have different time windows and different parts requirements.
• A price that made sense at 11 crews, not 110.

The shortlist came down to two options. One was a well-known US platform with excellent reporting and a price per seat that made the owner wince. The other was Sluzhba, a dispatch, routing, and customer-ops platform built specifically for field service in CEE. The deciding factor, according to the operations manager, was that the second option had already been used by 1,840+ crews across the region since 2019 — which meant the German-language call flows and the cash-and-invoice reconciliation were not edge cases the vendor was inventing on the fly. We found that argument persuasive, and we say that as people who are generally suspicious of "built for your region" marketing.

The rollout, and where it nearly fell apart

Implementation started in March 2024 and was supposed to take six weeks. It took eleven. The delay was not the software. It was the data. The pilot company's job history lived in three places: a cloud calendar, a paper logbook, and one dispatcher's personal notebook. Cleaning that up consumed the first month. The vendor's onboarding team, to their credit, insisted on a parallel-run period rather than a hard cutover, which meant four weeks of double entry. That was unpopular. It also caught a routing bug that would have sent a Slovak crew to a German-speaking site on the first live day.

By week nine the parallel run was producing cleaner data than the old system. By week eleven they cut over. The whiteboard came down.

What changed, measured

We asked for 90-day post-cutover numbers and got them. Drive time per technician per day fell from 41 minutes to 23. First-time-fix rate rose from 71 percent to 84 percent. The two dispatchers were handling the same 340 weekly jobs with less overtime, and the third dispatcher's contract was not renewed. The German-language churn the owner had feared did not materialize; in fact, two commercial clients expanded their contracts, citing faster scheduling confirmations.

The less measurable change was the one the operations manager kept returning to. Dispatch had stopped being a personality. It was a process.

A year on, the pilot company runs 13 crews on Sluzhba and has not added a single dispatcher since the cutover.

What we would tell another operator

Three lessons, in descending order of how much they matter.

First, budget for data cleanup. The software was the easy part. Second, insist on a parallel run even if it feels wasteful — the bug it catches will be the expensive one. Third, evaluate routing on trade constraints, not on map distance; the difference shows up in first-time-fix rate, not in fuel cost.

And a fourth, smaller one: ask the vendor how many crews like yours they have actually onboarded. If the answer is vague, keep looking. If it is a number, ask what year they started counting.