Handing off emergency calls without a group-text meltdown

It is 9:40 on a January night and your phone lights up three times in four minutes. A slab leak in the Reyes house, water coming up through the tile. A water heater letting go into a finished basement. A commercial account with a supply line blown behind a reception desk. You have three trucks out and a crew group text, so you do what you have always done: you drop all three into the thread and start typing addresses.

That is the moment the group text stops being a convenience and becomes a liability. On a normal Tuesday it holds one job at a time and the cracks stay small. On a burst-pipe night, when calls stack faster than anyone can read, the single thread is exactly the wrong tool, and the customer with water on the floor is the one who pays for it. This is the same wall every crew group text hits, covered across the proof and getting paid guides, and emergency dispatch is where it hits hardest.

Burst-pipe week, dispatched by group text

Picture the week every on-call plumber has lived. A hard freeze breaks, thirty calls come in over four days, and you have three trucks: Marco, Danny, and a two-man truck with your apprentice on it. Here is one night in the thread.

9:41, you: Reyes, 1400 Oak, slab leak, whoever is closest. 9:41, you: also water heater at the Bishop house on Linden, dispatched into basement. 9:42, you: and Danforth Dental, supply line behind reception, key is under the mat. 9:44, Marco: on it. 9:47, Danny: heading over.

Who is on it? Marco typed “on it” right after three addresses landed. He means Reyes, the one he was already near. Danny means Reyes too, because it scrolled to the bottom and it is the one he saw. Nobody claimed Bishop. Nobody claimed Danforth. Two trucks are now rolling to the same slab leak, the water heater is still dumping into a finished basement, and the commercial account is sitting dark. You will not find this out until 10:05, when Marco and Danny pull up to the same curb.

That is not a discipline failure. Those are good plumbers moving fast. The tool gave three jobs one line to land on and no way to say which truck owns which call. So the same failures show up every hard-freeze night, in the same order.

Two guys answer the wrong one. “On it” attaches to nothing. In a single thread there is no field for which job a reply belongs to, so the newest address wins and the older two go quiet.

A call gets no truck at all. The dangerous one is not the double-covered job. It is the one nobody claimed, because in a wall of texts a job with zero replies looks exactly like a job that is handled.

The handoff loses the details. Marco clears Reyes and you send him to Bishop, but the gate code, the customer’s callback number, and the shutoff location are forty messages up. He calls you from the driveway to re-ask what you already typed.

Nobody can tell you the board. At 11pm the owner wants to know what is still open. You scroll a two-hundred-message thread trying to reconstruct which of thirty calls got a truck, got closed, or fell through. There is no board. There is only the scroll.

What the missed call costs

Put a number on the one nobody claimed. The Bishop water heater ran into a finished basement for the ninety minutes it took to notice Bishop was never picked up.

Start with the roll you wasted: two trucks to Reyes instead of one, so one truck drove a night call for nothing. Call that an hour of a plumber and the fuel, easily a hundred dollars you cannot bill. Then the real number, the basement. Ninety extra minutes of clean water across a finished floor is not a mop-up. It is baseboard, drywall, and pad, and now it is a water-mitigation claim with a deductible and a week of dryers running. Even if insurance covers the structure, your customer remembers that your crew was told at 9:41 and nobody came until after 11. That is the callback that does not call back, and on a good commercial account it is a five-figure relationship, not a one-night invoice.

The information existed. You dispatched Bishop at 9:41. The group text just had no place to hold a job that nobody had answered yet, so a claimed job and an orphaned job looked identical until the damage told you which was which.

The same night, dispatched by thread

Now run the burst-pipe night with a thread per job instead of one thread for everything.

Each emergency call opens its own thread the second it comes in: Reyes slab leak, Bishop water heater, Danforth supply line, three separate work orders. You drop the address, the shutoff location, and the customer’s number into the Bishop thread once, and it stays at the top of that thread instead of scrolling away. You assign Marco to Reyes and Danny to Bishop, and each man is looking at one job, not three stacked in a feed. There is no “on it” pointing at the wrong call, because the reply lives inside the job it belongs to.

The apprentice truck takes Danforth. When they arrive, the “before” photo of the flooded reception area lands on the Danforth task, timestamped, attached to that work order and no other. When Marco clears Reyes, you hand him Bishop, and the gate code and shutoff are already at the top of the Bishop thread. He does not call you from the driveway. He reads the thread.

At 11pm the board answers itself. Three threads, three states: Reyes marked done, Danforth in progress with a photo on it, Bishop assigned and rolling. Nobody scrolls two hundred messages to find the one call that fell through, because a call with no truck on it is not buried in a feed. It is a job with no one assigned, and it is sitting right there unassigned.

Threads for the work, the group text for the memes

The point is not to kill the crew group text. Keep it. It is where the coffee runs and the ballbusting and the “who left the jetter at the shop” live, and it is good at exactly that. The mistake is asking it to also be your dispatch board on the worst night of the year, because a single thread cannot hold thirty calls and three trucks without dropping one. Once the emergency work moves to a thread per job, the group text goes back to being for memes, which is the only thing it was ever reliable at.

This is worth two related reads. When the leak comes back a month later and you need to know whether it is your callback or a new problem, the warranty callback versus new problem guide walks the sorting, and it depends on having a thread that remembered the first visit. If you are the one-man shop just now adding trucks, the dispatching without forwarding texts guide covers the same handoff at smaller scale. And every one of these nights should close with a sign-off, so the job does not stay half-open in someone’s memory.

That thread per job is the whole idea behind Crewmigo. Each emergency call is its own work order that remembers the address and the shutoff, photo proof lands on the task it belongs to, and the primary button moves the job from Mark done to Approve to Sign off so you can see the board at a glance instead of scrolling for it. Subcontractor guests are free if you pull in an outside truck on a bad night, and the record of the whole week belongs to you and exports clean for the mitigation claim. We are new, so put one hard-freeze night on it and watch where the calls land.