Most Israeli field-service teams between five and fifty technicians are dispatching jobs in WhatsApp groups. Some have moved to a shared Google Sheet. A few use a CRM-shaped tool that someone bought during a "we need software" phase and that nobody opens during dispatch.
The default isn't WhatsApp because it's the right tool. It's WhatsApp because the right tool doesn't seem to exist at the price an Israeli SMB can stomach, and because the alternatives — Skedulo, Salesforce Field Service, ServiceMax — are priced and shaped for fleets of two thousand technicians and an IT department.
So you default to WhatsApp. And for a while, it works.
The thing WhatsApp can't do
WhatsApp transmits messages. That's it. It doesn't have:
- A state model. A job is "assigned" because someone wrote "אורי תעשה את זה" in the group at 8:14 AM. The state lives in whoever read the message and remembers.
- A historical record that's queryable. By Friday, "what did we actually do this week?" is a question that takes hours to answer.
- A model of who's qualified. "Send a tech to the new client" requires a human to know which tech has the right certification, isn't already on the other side of the country, and isn't on vacation.
- A reaction loop. When a technician calls in sick at 9:30 AM, you re-orchestrate four hours of work in a chat thread. The replanning happens in your head.
WhatsApp's strength — speed of message transmission — is the wrong strength for an operational system. You don't need faster messages. You need a system that holds the state.
The cost is invisible
Here's what people don't measure:
The dispatcher's morning. Every team I've talked to lands somewhere between 60 and 120 minutes of "laying out the day." That's not 60-120 minutes of valuable work. It's mostly transcription — copying yesterday's plan, adjusting for who's available today, sending individual messages to each technician. Three weeks per year per dispatcher.
Customer reschedules nobody knew about. A customer cancels via WhatsApp, the technician sees it but the dispatcher doesn't, the route is built around a job that won't happen. The empty slot becomes a paid hour the technician spent on the road for nothing.
Recurring services that slip. The customer pays you ₪400 a quarter to come do an inspection. It's tracked in the dispatcher's printed calendar. They miss it. The customer calls in October. You apologize. Twelve months later, the customer doesn't renew.
The end-of-month invoicing dance. What was done. What hours. What parts. You reconstruct it from photos in three different technicians' phones, signatures on paper that's been in a glove compartment, and the WhatsApp thread. Some hours never make it onto an invoice. That's not theft — it's just leakage. It compounds.
What dispatch actually looks like in a system
When dispatch lives in a system rather than chat, four things change:
- State is canonical. A job is "assigned" because a row in a database says so. The technician sees it on their app. The dispatcher sees the same row. Nobody has to remember anything.
- Constraints are explicit. "Send a tech to the new client" becomes "find the tech with HVAC certification, within 15 km of the address, with capacity in the next three days, not already booked, not on regulatory leave." The system answers in a hundred milliseconds.
- Reactions are continuous. When the technician calls in sick at 9:30 AM, the system replans the rest of the day before the dispatcher has finished her coffee. The dispatcher reviews and approves — she doesn't reconstruct.
- History is queryable. "What did we do this week" is one click. So is "which customers haven't had their quarterly inspection." So is "what hours did each tech actually log." Invoicing isn't an archaeological project anymore.
The honest tradeoff
WhatsApp is free. A real dispatch system has a monthly cost. You're paying that cost anyway — in the dispatcher's morning, in missed recurring service, in invoiced-vs-actual gaps. The question isn't whether to pay. It's whether to pay in hours or in shekels.
If you're at five technicians and you're not growing, WhatsApp is fine.
If you're at fifteen and growing, you've already crossed the line. The cost is just hidden from you.