Why running your crew from a LINE group eventually breaks

Almost every Thai installation business starts the same way: one LINE group, the owner posting today’s jobs, technicians replying with photos. It works, until it doesn’t.

If your team has three technicians, LINE is fine. But at five or six people — with multiple jobs running in parallel, customers calling in for updates, and parts being ordered on the fly — the cracks appear fast.

Where it falls apart

The schedule lives in one person’s head. When the owner is busy, sick, or driving, nobody else can see who’s free or what’s booked. A LINE thread is a log, not a plan. Your office staff can’t look at a LINE group and confidently tell a customer what time the technician will arrive — they have to wait for the owner to reply.

Jobs get double-booked or lost. A message scrolls away, two customers get the same time slot, and someone shows up to an empty house. With aircon jobs this happens constantly during April and May when you’re handling fifteen requests a day and the LINE notifications never stop.

There’s no history. Six months later a customer calls about a warranty claim and you’re scrolling through thousands of chat photos trying to find the original install. What brand was it? Which technician did it? Was there a wiring note? The answer is buried somewhere in a chat nobody can search properly.

You can’t see capacity at a glance. If a new customer calls and wants a CCTV install Thursday morning, can you take it? With LINE, answering that question means mentally tracking who’s already assigned where — and hoping you remembered correctly.

Status updates disappear. A technician texts “on the way” and that message is ancient history by the time a second one comes in an hour later saying “delayed, traffic.” Your customer calls you. You have no idea what’s actually happening.

A real example

Imagine a five-technician aircon business in peak season. The owner manages the LINE group from his phone, replies to customers directly, and holds the entire schedule in his head. On a Wednesday he gets a toothache and takes the afternoon off. Three jobs that needed confirming don’t get confirmed. One technician goes to the wrong address. One customer doesn’t get a callback. By the time the owner is back the next morning, there’s a complaint on Facebook.

None of that is a failure of effort. It’s a failure of system. The schedule was a single point of failure.

What a dispatch board actually fixes

A real dispatch board shows every job and every technician in one view. You assign a job by dragging it to a technician. The technician sees it on their phone immediately — no waiting for someone to forward a message. If a job runs long, you can see it affecting the afternoon slot before the afternoon arrives.

The whole team sees the same information. Your office staff can check the board and tell a customer “your technician leaves for you at 2pm” without calling the owner. That alone reduces how many times the owner gets interrupted by questions they shouldn’t have to answer.

Jobs don’t fall through gaps. Every request becomes a job card. Unassigned cards stay visible until someone picks them up. Nothing scrolls away.

The history is searchable. When a customer calls about last year’s install, you filter by their address and see every job, every photo, every note. A warranty dispute that used to take thirty minutes of scrolling takes thirty seconds.

The point isn’t to replace LINE for talking to customers. Keep LINE for customer conversations — it’s genuinely good at that. The goal is to stop using a messaging app as your operations backbone.

When does it make sense to switch?

You probably don’t need a dispatch board if you have two technicians and the owner handles everything personally. But if any of these apply, it’s time:

• You’ve had at least one double-booking in the last three months
• Customers sometimes don’t get a callback because a request got buried
• You can’t answer “who’s free Thursday?” without making a few calls first
• A team member other than the owner sometimes needs to assign or check jobs

Start small

You don’t need to overhaul everything in a week. Take this week’s existing jobs and put them on a board. Ask your technicians to check in via the app when they arrive and when they finish. Keep LINE for what it’s good at: conversation with customers, quick questions between the team.

The difference shows up the first time two jobs don’t collide — and you didn’t have to do anything special to prevent it.

---

Related feature: see how OnSiteQ’s dispatch board puts every job and technician on one view.