When WhatsApp is running your jobs

When WhatsApp is running your jobs, the job board is a group chat, and the only record of who's doing what sits on a handful of personal phones. A proper ops system moves the job itself (address, status, owner, notes, photos) into one shared record. Your team still uses their phones; they just stop using a chat thread as the database.

How WhatsApp became the job board

It happens without anyone deciding it. The office posts new work in the team group and someone replies to claim it. Addresses arrive as screenshots. The scope of work is a voice note recorded between jobs. Before long, the group holds the diary and half the customer history.

And for a while it works. People already have the app, nobody needs training, and replies come back fast. The trouble is that a chat is ordered by time, not by job. Ask "what's still open from last month?" and the honest answer is a long scroll.

What breaks when the chat is the system

These are the failures that show up once a team grows past a few people:

• Missed jobs: a request gets buried under messages about something else, and nobody claimed it.
• Wrong address: someone drives to the address in an older screenshot because the correction came later, in a different message.
• No audit trail: there's no clean answer to who agreed the extra work, when, or at what price.
• Money living elsewhere: the job is in WhatsApp, the quote is in someone's sent folder and the invoice is in a spreadsheet, so nothing lines up.

The quiet one is staff turnover. When an engineer leaves, their phone leaves with them, and so do the photos and private chats with customers. The business never owned that history. We've written separately about quotes and invoices stuck in email and the info@ inbox nobody owns; WhatsApp is the same problem with a faster scroll.

What a proper ops system replaces

It doesn't replace the phone. It replaces the group chat as the place where the truth lives. In practice that means a job record with a status, a named owner and the customer's details attached, so the address is entered once and carried through.

In TradeOps, our own product for trade and service businesses, an accepted quote becomes a job with the customer and quoted lines carried across. The job holds the site address and access notes. The job sheet has a checklist, materials, photos tagged before, during, after or issue, and notes. Statuses run from draft and scheduled through to completed and signed off, and the customer can sign on the device on site. The invoice is raised from the same record. Roles decide which team members can see and change what.

So the engineer still opens a phone. They open the job instead of the group. TradeOps is a web app that runs on the phones and computers your team already has; there's no app-store download to roll out. The details are on the TradeOps jobs page.

Keep WhatsApp for quick conversation between colleagues. Just don't let a job exist only there.

When your team works without signal

One honest limitation. TradeOps isn't built for offline use, so if your engineers spend their day in basements or rural sites with no signal, a browser app will frustrate them. For that, we build custom Flutter apps for iOS and Android that work locally and sync later. We covered the trade-offs in from paper job sheets to a phone app, so I won't repeat them here. Custom work starts with a free scoping conversation and is quoted at a fixed price per agreed release, and you own the code and the cloud accounts it runs on.

When WhatsApp is still fine

If you're a one-person outfit, or two people doing a few jobs a week, a chat and a diary is a perfectly reasonable system. We'd advise against a disruptive move if your simple setup is working well.

The signs you've outgrown it are specific. You can't answer "which jobs are open?" without scrolling. Two people have turned up to the same job, or nobody has. You've had to ask a former employee for photos. Customers are getting quotes from one place and updates from another. If that sounds familiar, the question isn't whether to ban WhatsApp. It's when WhatsApp is running your jobs, what should be holding them instead.

TradeOps also puts your public website on the same system as your enquiries, so a contact form lands as a lead rather than another message to forward. If you only need the site, see our websites service.

My view: the phones were never the problem. The problem is a business whose memory lives in a chat it doesn't own. If your job board is a WhatsApp group and you'd like to see what moving it into one record would look like for your team, talk to an engineer.