Half the calls to your shop aren't jobs

Ten past seven on a Monday, still sitting in the yard. Eleven missed calls over the weekend and three voicemails. The owner scrolls the log and what's actually on the screen is eleven phone numbers and eleven timestamps.

One of them was a homeowner with water coming through a kitchen ceiling, who by now has called somebody else. Two were the supply house. One was the same 800 number four times. There's no way to tell which is which without calling all eleven back, and there's a nine o'clock.

Capturing calls is the easy half

Nearly everything sold to a home-service business promises the same outcome: you'll stop missing calls. Fair enough. But an owner who already has a full call log knows the part the pitch skips. Having the call is not the same as knowing what it was.

A list where a supplier, a robocall, an existing customer asking about an invoice, and a nine-thousand-dollar water job all look identical isn't much better than no list at all. It's eleven rows of homework. In a busy week that homework doesn't get done, and the row that mattered was somewhere in the middle of it.

What's actually in a week of calls

Sit with a week of any contractor's phone and the traffic falls into about five kinds. Only one of them is what you'd call a lead.

• New work. Somebody has a problem and wants a company to come fix it. This is the money, and by volume it's the minority of the calls.
• Existing customers. About an invoice, a warranty, a tech who was supposed to come Tuesday. Real and worth answering, but not new revenue, and they don't belong in a pile you're ranking by value.
• Suppliers, subs, and the office side. The distributor confirming a delivery, an adjuster, somebody from the county.
• Sales calls. SEO, merchant services, an extended warranty on a truck you sold two years ago.
• Wrong numbers and robocalls.

Put all five in one list and the list is mostly noise. That's the honest condition of the phone at most shops, and it's why 'just call everyone back' is advice that dies on contact with a Monday.

Why one undifferentiated list rots

Something specific goes wrong when every item in a list has the same shape, and it's the same thing that happens to a smoke alarm that goes off every time you make toast.

If every call fires an alert, then inside of two weeks the alert means nothing. You swipe it away without reading it, because the last nine were a supply house and a warranty robocall. Then the tenth is the burst pipe and you swipe that one away too, out of pure muscle memory. An alert that cries wolf isn't neutral. It's worse than no alert, because it trains you out of the reflex it was supposed to build.

So sorting isn't a refinement you add on top of capture once things are going well. It's the thing that makes capture usable in the first place.

Three piles, not fourteen

The useful sort is coarser than people expect. You don't need a taxonomy. You need three piles, and they're separated by what you're supposed to do about them.

• A job. Somebody wants work done. This gets a written record of what they need, where they are and how urgent it is, and it gets your attention now.
• A message. A real person with a real reason to call, but no new work in it. The existing customer, the adjuster, the sub. Worth writing down and returning. Not worth ranking against a flooded basement, and not worth a notification at 11 p.m.
• Nothing. Robocall, wrong number, cold pitch. This should never become a row in anything you look at.

The third pile is the one most systems get wrong, because keeping everything feels safe and reads well on a feature list. In practice each junk row is a small tax on every future scan of that list, and you pay it every time you open the app.

Sort first, then rank

Once the list is only jobs, the second question is finally worth asking: which one first.

Plenty has been written about calling leads back fast, and it's true as far as it goes. But 'fast' with eleven rows and one truck is a fantasy. What you need is an order. A ceiling coming down beats a routine quote. A quote on a full system replacement beats a service call for a running toilet. Those are judgments about urgency and size, not about who dialed first.

None of that ranking means anything until the sort underneath it is right. Rank an unsorted list and you get a supply-house callback sitting at position two because it happened to come in at 6 a.m.

The rule that makes sorting safe

There's an honest problem with any sorting, whether a person does it or software does. Sometimes it will be wrong.

What makes it safe anyway is that the two mistakes don't cost the same. File a supplier as a job and you lose fifteen seconds glancing at a row that didn't need you. File a homeowner with a flooded basement as junk and you lose the job, the customer, and whatever they tell their neighbors afterwards.

So the rule is: when it isn't clear, treat it as a job. Not as a hedge, but because the arithmetic is that lopsided. Anything that sorts your calls should be built to fail in that direction, and it's a fair question to ask before you hand over your phone. Ask what happens to a call it isn't sure about. If the answer is that it quietly drops it, keep looking.

What a sorted Monday looks like

Take those eleven weekend calls again. Sorted, the morning reads: two jobs, one of them urgent, three messages that can wait until lunch, and six rows that never needed to exist. The owner makes two calls before nine instead of eleven after five, and the water job is one of the two.

Nothing about that requires a bigger office or a better memory. It requires the sorting to have already happened by the time the list reaches you, instead of happening in your head at a red light.