WhatsApp works up to about ten jobs a day. Here are the five things that break after that, what to keep it for, and how to move a team across without a mutiny.
Almost every Indian service business starts on WhatsApp, and that is a sensible choice, not a mistake. Everyone already has it. It costs nothing. It works on the cheapest Android phone. A supervisor can create a group in thirty seconds and start assigning work, with no procurement, no training and no vendor. For a team of three doing six jobs a day, it is genuinely the right tool.
What changes is volume. At six jobs a day, one person holds the whole day in their head and the group is just how they broadcast it. At twenty-five jobs across eight technicians, that same person is scrolling to find whether the Aluva complaint was assigned, a customer is calling because nobody arrived, and two technicians have both gone to the same site. The tool did not get worse. The job outgrew what a conversation can carry.
This article is about the specific things that break, what to keep WhatsApp for, and how to move without the rollout collapsing in week two — which is what usually happens.
This is the root of everything else. When a technician types “done”, nothing changes anywhere. No job flips from open to closed, no counter decrements, no invoice becomes ready. The status of the work lives only in the memory of whoever read the message. So the only way to know where thirty jobs stand is to ask thirty times, or to scroll — and scrolling gives you the messages that were sent, never the jobs that were forgotten.
The most expensive failure in field service is the job nobody remembered. A chat system cannot surface it, because an absence of messages looks exactly like a quiet day.
A job posted to a group of eight is assigned to everyone and to no one. In practice it gets picked up by whoever is free or whoever replies first — which is also why it does not go to whoever is nearest, and why your technicians criss-cross the city. When it is missed, no individual failed, so nothing is corrected. Assignment without ownership makes accountability impossible without anyone behaving badly.
Six months later a customer disputes a bill and asks what was replaced in March. The answer exists — somewhere in a group, in a photo sent by a technician who has since left, on a phone you do not control. Two structural problems here: chat history cannot be queried by customer, site or asset, and it sits on personal devices tied to personal numbers. When a supervisor resigns, the institutional memory of your operation walks out with their phone.
Photos in a group are proof of nothing in particular. They are not attached to a job, not timestamped in a way that survives, and not linked to the invoice. When a customer says the work was not done, or an insurer or a corporate client asks for a service record, you are assembling evidence from a chat thread. Real proof of service — a checklist, photos, a customer acknowledgement, all attached to a specific job at a specific site — is not something a group chat can produce.
Ask a WhatsApp-run business how many jobs each technician completed last month, the average time from complaint to closure, or how many jobs were reopened, and the honest answer is that nobody knows. You can feel that things are busy but you cannot see that one technician does twice the work of another, or that complaints in one area take three days longer to close. Every improvement in a service business starts with a number, and chat produces none.
The rollouts that fail are the ones that declare WhatsApp banned. Staff need somewhere to have a conversation, and if the new system does not allow one they will use the group anyway — and now you have two systems both holding half the truth. Draw the line by function instead.
Keep in WhatsApp: clarifying an address with a customer, sending a customer a photo or a payment link, a quick question to a supervisor, informal coordination between colleagues.
Move out of WhatsApp:
Said simply: conversation stays in chat; state moves to a system.
Three to four weeks, staged deliberately.
The single most important rule: the app must be the only place the day's list exists. The moment a technician can find their work in the group, the group wins, because it is familiar. Shadow systems do not fade out on their own.
A rollout is asking field staff to do data entry. It only sticks if they get something back on the same day:
If the app asks more of them than the group did and gives back nothing, it will be abandoned, and that will be a reasonable response rather than resistance to change.
Record these for two weeks before the cutover and two weeks after, or you will never know whether it worked:
The last one usually moves first, and it is the number owners feel most.
If you are running eight jobs a day with three technicians, stay on WhatsApp and spend your attention elsewhere. If you are past that — if jobs are being missed, if invoicing lags completion by days, or if one coordinator cannot take a holiday — the problem is not discipline and no amount of scolding fixes it. Job state has to live somewhere it can be queried.
Move assignment, status, proof and invoicing into one system, keep WhatsApp for conversation, run a one-crew pilot for a week, and set a cutover date you actually enforce. VeloCrew runs dispatch, field attendance, complaints, proof of service and GST invoicing in one login on phones your technicians already carry — see field service management, and if you are still deciding what to look for, start with our guide to field service management software in India.
Nothing, until volume rises. WhatsApp is a conversation tool, so it carries messages perfectly and job state not at all — a message saying "done" does not change anything anywhere, cannot be counted, and cannot be searched reliably six months later. The problems begin when you need to know the status of thirty open jobs at once, or prove what was done at a site.
Most teams cope up to roughly eight or ten jobs a day with two or three technicians, because one person can hold the whole day in their head. Past that the coordinator becomes the bottleneck and the first jobs start slipping — usually noticed as customers calling to ask why nobody came.
No, and trying to is why most rollouts fail. Keep WhatsApp for conversation — clarifying an address, sending a customer a photo, a quick question to a supervisor. Move the things that need state and history: job assignment, status, proof of service, and invoicing. Two tools with clear roles works; two tools doing the same job does not.
It works if the app asks less of them than the group chat did. A technician should be able to see their day's list, open a job, take photos and mark it done in a handful of taps, on the phone they already carry. If the new system takes more effort than typing in a group, they will go back to the group and they will be right to.
Realistically you do not migrate it, and it is worth accepting that. Export what you must keep, then start clean: enter your live open jobs, your customer list and your contracts into the new system, and treat the groups as a read-only archive from the cutover date. Trying to backfill history is how a migration stalls for months.
Plan for three to four weeks with a small pilot first, not a single weekend. One crew for a week, then the rest, with the old group deliberately closed for job assignment on a named date. The technical part takes a day; the habit change is what takes weeks.
Explore how VeloCrew can help you manage employees, field operations, attendance, tasks, HR and business workflows from one login — built for Indian operations teams. Every account starts on a 14-day Pro trial.
Start free ›Prefer a walkthrough first? Request a demo for your business.