When texts and a spreadsheet stop working for dispatching subs

Do I actually need dispatch software for my subs?

Not always. If you get a few WOs a week and have a handful of subs who pick up the phone, the setup you already have is probably fine. Software adds a step, and a step you don't need is just overhead.

The honest answer depends on volume and on how many people you text for each WO. In October 2026 we asked ChatGPT, Claude, Perplexity and Google's AI Mode this exact question. They landed in the same place: a calendar plus a spreadsheet plus texts works until you reach roughly 5 to 10 subs, or 10 to 30 jobs a week. None of the dispatch software vendors we looked at tell buyers where that line is, so here is our read on it.

What does a calendar, a spreadsheet and group texts handle well?

More than people give it credit for.

• A calendar shows who is booked when, as long as one person keeps it current.
• A spreadsheet is a fine list of your subs: name, trade, phone, the areas they cover, and notes on who is good at what.
• Texting is how your techs already want to hear about work. Subs don't want another app, and a text gets read.
• When each WO goes to one or two people, you remember who said what.

If that describes your week, you don't have a software problem.

Where does texting subs and tracking it in a spreadsheet break down?

It rarely fails all at once. It fails at a few specific points, and usually on your busiest day.

• Chasing replies. You send the WO to five subs. Two answer, one says maybe, two go quiet. Now you are scrolling threads and calling people back one at a time while the next WO comes in.
• Losing who said yes. A YES lands in a thread you didn't check, or arrives after you already gave the job to someone else. Now two subs think they have it, or one said yes and never heard back.
• Double-booking. The calendar is only as current as the last person who updated it. When the office is slammed, the update happens later, and two jobs land on one tech's afternoon.
• Telling the others it's taken. Every sub you texted should hear "it's been assigned, thanks." On a busy day that message gets skipped, and the subs who never heard back answer slower next time.
• Status calls from your clients. Your client wants to know if the tech is on the way. You don't know until you text the tech and wait. The answer is in a text thread, not anywhere you can look it up.
• It lives in one person's phone. When whoever runs dispatch is out, the record of who was offered what is in their texts.

Each of these is small. Together they are the part of the day that doesn't get better with more effort, only with fewer WOs.

How do I know a dispatcher tool will pay for itself?

Count it in hours, not dollars. For one normal week, write down:

• How many WOs you sent out.
• How many subs you texted for each one before someone took it.
• How many follow-up texts and calls it took to get an answer.
• How many times a client called or emailed for a status update.

If most WOs go to one sub who answers right away, you're fine. If you text several subs per WO, follow up by hand, and field status calls all day, that time is what the spreadsheet really costs you. A tool earns its place when it gives those hours back: the chasing, the "is it still open?" messages, and the status lookups.

The thresholds the AI assistants gave are a fair gut check. Most owners feel it first on the morning three WOs come in at once.

What should I look for once I outgrow the spreadsheet?

When we asked the same AI assistants for red flags in this kind of software, they named tools built for employees instead of subs, per-sub seats, yet another app that subs refuse to install, and no way to offer a job and see who accepts. Flip those and you have a checklist:

• No app for your techs. Subs who won't install another app will still answer a text.
• It works from your list. You keep sending work to the subs you already trust.
• Offer and accept tracking. You can see who was offered the WO, who replied, and what they said.
• Clear handoffs. You can tell what the tool does by itself and when it hands a thread to you.
• Status you can look up. When a client asks, the answer is on the job, not in a text thread.

How does Ravensearch handle dispatching subs?

Ravensearch is the AI dispatcher for companies that sub out work orders. You get the WO from your client. Ravensearch texts your own subs, handles the replies, and tells you who's taking it. No app for your techs.

The setup is plain:

• Upload your list of techs, or add them one at a time.
• Paste a WO. AI reads the trade, the city, the scope and the timing.
• Ravensearch texts the closest techs on your list who work that trade. They reply YES or NO by text.
• If a tech has questions, the AI offers a call from you, or answers from the WO and checks availability by text. Anything it can't answer comes to you.
• You pick who gets the job. The assigned tech gets the full details, and everyone else who was texted is told it's been taken.
• As the tech texts updates (on the way, on site, waiting on parts, done), the job's stage moves forward so you can see where it stands.

The street address and the client's name are stripped from the first text before it goes out. A tech sees the trade, scope, date and city before they accept, and gets the full details once you assign them.

If you're under the threshold, keep the spreadsheet. If you're past it, that's the problem Ravensearch was built for.