Dispatch Software for Small Service Shops: What to Look For and What to Skip

• Dispatch software solves assignment and status, not invoicing. Tools that promise everything take longer to set up and cost more to keep running.

• Per-seat pricing is the main reason small shops overpay. A tool that charges per technician punishes you for hiring.

• Technician adoption decides whether a rollout works. Software your crew will not open is worse than a whiteboard they will read.

• US carriers require A2P 10DLC registration before you can text customers under your business name. Approval takes time, so start it early.

• Run a two-week trial on real jobs before you commit, and export your data at the end to check you can actually get it back out.

The core jobs

Strip away the marketing and dispatch software does four things. It holds your jobs in one place, assigns them to a person, tells that person what the job is and updates the board when the status changes.

Everything else is an addition. Some platforms layer on customer history, job types with saved defaults, time windows, recurring work and reporting. Those are useful, but they are not what makes the tool work on a Tuesday morning.

The status loop is the part that earns its keep. When a tech marks a job en route or done, the desk knows without calling, and the next job can go out. That single loop removes most of the phone traffic a small shop generates internally. The same status-and-notification problem shows up in tracking and delivery workflows across other industries, and the fixes tend to rhyme.

What it should not try to do

Dispatch software is not an accounting system, a marketing platform or a GPS fleet tracker. If a product claims all of those, you are looking at a full field service management suite, which is a different purchase with a different setup burden.

There is nothing wrong with a suite if you need one. The problem is that many shops buy one to solve a dispatch problem, then spend weeks configuring modules they will never open. If your invoicing already works, replacing it as a side effect of fixing dispatch is a self-inflicted project.

Most owners know the moment it stops working, but it helps to name the symptoms.

• Two trucks have been sent to the same address at least once

• Job details live in a thread and have to be scrolled back to

• You call a tech to ask where they are more than twice a day

• Customer history is in somebody's head rather than a record

• A schedule change means individually texting three people and hoping

One or two of these is manageable. All five at once means the coordination cost has already exceeded what software would charge you.

Full field service management platforms

These cover scheduling, dispatch, quoting, invoicing, payments, marketing and reporting in one system. For shops that want everything under one login and have someone to configure it, they are genuinely good products.

Pricing is where small shops run into trouble. The common structures are a base plan with a small number of included users, then a monthly charge for every additional person, or a plan tier with a hard user cap that forces an upgrade when you hire. A few of the larger platforms do not publish pricing at all and route you to a sales call.

Model the cost at the headcount you expect in eighteen months, not today. A per-seat structure that looks reasonable at three techs can double before you have added a truck.

Dispatch-only tools

A narrower category has emerged for shops that want the board without the suite. These handle assignment, scheduling and status, and deliberately leave invoicing and marketing where they already are.

CopyThat is one example of SMS dispatch software built specifically for shops running two to ten trucks. Jobs go on a board, you drag one onto a technician's column and that tech gets a text with the job, address and notes. They reply OTW when rolling, HERE on arrival and DONE at completion, and the board updates itself. Anything else they type is saved as a note on the job.

Pricing runs on flat monthly tiers of $49, $99 and $149, covering up to five, seven and ten technicians, with no per-user charge, no SMS overage fee and no contract. A launch promotion halves the first month on every tier at the time of writing. Each tier carries a published fair-use job ceiling of 900, 2,100 and 3,000 jobs per month.

The company states plainly that shops larger than ten trucks have outgrown the product, which is a more useful thing to hear before you buy than after.

The trade-off is scope. There is no invoicing, no marketing and no GPS fleet tracking, on purpose. If you need photographs attached line by line or custom field forms, an app-based platform will serve you better and will cost more.

Staying on the whiteboard

This is a legitimate answer for a two-truck shop with steady repeat work and a dispatcher who never takes a day off. It stops being legitimate the moment that dispatcher is unavailable and the schedule lives nowhere anyone else can read it.

Per-seat pricing

Charging per technician aligns the vendor's revenue with your headcount, which means the software gets more expensive precisely when you are growing and cash is tight. Some owners respond by sharing logins, which defeats the audit trail they bought the software for.

Flat pricing removes that pressure. When you compare quotes, calculate the cost per job rather than the cost per month, and run the number at both your current volume and your busiest month.

Technician adoption

The best board in the world fails if the crew will not use it. App-based tools ask every technician to install software, create a login, keep the app updated and remember a password in a parking lot in February.

Some shops manage that easily. Others have technicians on older phones, crews who change frequently or subcontractors who will not install a company app on a personal device. For those shops, a text-based workflow removes the entire adoption question, because everyone already knows how to reply to a text.

Ask your crew before you decide. They will tell you in one conversation what a three-month rollout would teach you the hard way.

If you plan to send text messages to customers from software, US carriers require the sending business to be registered through a framework called A2P 10DLC. It stands for application-to-person messaging on ten-digit long codes, and it exists so carriers can identify who is actually sending a message.

The detail that surprises people is whose name has to be on the registration. A message that says a technician from your company is on the way has to go out under your company's registration, not under the software vendor's. That means supplying your legal business name, EIN and address, and waiting for carrier approval.

Approval commonly takes up to two weeks. Some vendors file the paperwork on your behalf, and some leave it to you. CopyThat files it for shops on its Growth and Fleet tiers and keeps customer texting switched off in the product until approval clears, rather than letting messages fail silently at the carrier.

Registration is not the same as consent. You still need permission to message customers, accurate sender identification and a working way for people to stop receiving messages. Build that into your process before your first live day.

Do not start during your busiest week, and do not start with the whole crew.

Pick two technicians and run one full week of real jobs through the board. Watch for the things that only show up under load: schedule changes mid-morning, a job that runs long and pushes everything back, a customer who calls the office instead of the tech.

Check three specific things before the trial ends. Confirm that a job note typed by a technician actually lands on the job record and stays there. Confirm the board reflects reality at four in the afternoon without anyone having tidied it. And export your data, because a vendor that makes export difficult during a trial will not make it easier once you are a customer.

Ask the two technicians one question at the end: was this less annoying than the group text? If the answer is no, the rollout will fail no matter what the board can do.

• What happens to the price when I add a technician?

• Are there message fees, setup fees or overage charges on top of the plan?

• Can I export customers and job history, including notes, as a CSV?

• Who files the carrier registration for customer texting, and how long does approval take?

• What does a technician need on their phone for this to work?

• Is there a contract, or can I cancel the product?

An honest vendor will answer all six without a discovery call. If the pricing question needs a meeting, you have learned something about the product's fit for a shop your size.

Dispatch software does not have to be a project. The shops that get value from it start narrow, fix the assignment and status problem first and leave the systems that already work alone.

Software will not fix unclear job notes, missing addresses or a schedule nobody owns. It will stop those problems from hiding in a group text, which is usually enough to see what is actually broken.

Start with one week, two technicians and real jobs. You will know by Friday.

1. Is dispatch software overkill for a three-truck shop?

Not usually. The question is not how many trucks you run but how much time the desk spends coordinating them. If you are calling technicians for status updates several times a day, a board pays for itself quickly at small-shop pricing.

2. Can technicians use dispatch software without installing an app?

Yes. Text-based tools send the job to a technician's phone and accept short replies to update status, so no app, login or data plan is required. This suits crews on older phones, frequent staff changes and subcontractors who will not install company software on a personal device.

3. What is A2P 10DLC and do I need it?

A2P 10DLC is the registration system US carriers use for business text messages sent through an application. You need it if you plan to text customers under your business name. Some vendors file it for you, and approval commonly takes up to two weeks, so start early.

4. Should I replace my invoicing when I buy dispatch software?

Only if your invoicing is actually broken. Replacing a working accounting process as a side effect of fixing dispatch adds weeks to a rollout and gives you two problems to debug instead of one.