Service Dispatch Software: Buyer's Guide for Small Crews

Service dispatch software helps a business coordinate customer requests, appointments, technician assignments and field updates. Some products extend that workflow into estimates, invoices and payments; others focus on scheduling and connect to separate systems. The category name does not guarantee that every step is included.

For a one-to-ten-technician HVAC, plumbing, electrical or other service crew, the useful question is practical: can the people doing the work keep the schedule and job records current from their phones, without rebuilding the day in the office?

The loop: booking, assignment, field updates and billing

Start with a customer request, confirm the appointment, assign an appropriately qualified technician, record progress and prepare an invoice from reviewed job details. Routing, customer messages and payment collection may sit alongside that loop. Ask which steps are native, which need an add-on and which remain manual at your quoted plan.

A saved draft is not a confirmed appointment. An invoice that has been sent is not a collected payment. Keep those states distinct when a vendor demonstrates an apparently seamless flow.

Look at the last 30 days before opening another feature comparison. Count missed visits, overlapping assignments, customer calls asking for an arrival time and hours spent retyping job notes. Record what actually happened, not just what felt frustrating.

These are potential costs and test ideas, not promises that a feature will eliminate a problem. Reminders cannot guarantee attendance, conflict warnings depend on accurate availability, and location tracking cannot guarantee an arrival time.

Keep lost revenue separate from lost contribution. If an empty slot could have produced a $400 job, the entire $400 is not necessarily lost profit: materials, labor and other relevant costs still matter.

Calendar changes and conflict detection

Give one technician two overlapping appointments, including travel time. Then move a visit and check who is notified. A drag-and-drop calendar can be convenient, but the important behavior is whether the tool exposes conflicts, qualifications, availability and the consequences of a change.

Customer ETA notifications and optional GPS

Delay a morning appointment and ask the vendor to show what the afternoon customer receives. Is the arrival update automatic, manually sent or dependent on a separate service? Confirm messaging charges, consent requirements and what happens when the technician's phone loses signal.

If location tracking is proposed, ask about working-hours controls, access permissions, retention and employee privacy. Do not assume a route planner provides live tracking or sends customer ETA texts.

Mobile job updates

Have a technician—not only the owner—open a job, find the relevant equipment history, add notes and a photo, and update the job status. Try the actual phones and browser the crew will use. Ask explicitly about offline behavior; a mobile-friendly screen is not evidence that records will save without connectivity.

Voice capture and reviewed invoicing

Dictate a realistic repair with quantities, parts, labor and a customer name. Correct a mistaken part or price, then prepare the invoice. Check how the team reviews the draft before sending, requests a signature and offers an authorized payment method. A signature or payment should never be assumed to appear simply because someone dictated notes.

Choose three problems and give each an importance weight from 1 to 10. During every demo, score how well the product handles your scenario from 0 to 10. Record the plan, add-ons, limits and evidence alongside each score.

Weighted score out of 10 = sum of (importance weight × demo score) ÷ sum of importance weights. Use the same weights for every candidate. This is a decision aid, not a scientific product rating.

The example earns 134 weighted points across 20 importance points: 134 ÷ 20 = 6.7 out of 10. The weights do not have to total ten; normalizing by their sum makes the result comparable.

• Use a double-booked Tuesday, a delayed technician and a completed job with a corrected invoice—not just the vendor's prepared example.
• For a required capability that cannot be demonstrated, mark it unverified. Award no credit until you see evidence; do not present the missing demonstration as proof the feature never exists.
• Write down whether an automation needs setup, customer permission, another integration or a higher tier.
• Set a pass/fail requirement for critical behavior such as data export or invoice approval, so a high average cannot hide a deal-breaker.

Red flags worth resolving before purchase

Pause if the demonstration avoids your scenario, quoted features change between plans, export rights are unclear or no one will confirm the complete price in writing. Sales-assisted pricing is not itself a fault; an incomplete quote is a reason to wait.

Jobber, Housecall Pro, Workiz, FieldEdge and ServiceTitan are names you may encounter in a field-service software search. This guide does not verify their current pricing, specific capabilities, plan restrictions or crew-size fit. Check current vendor information and request a demonstration of your actual work.

Do not choose a product because a guide declares it the default for five technicians or “overkill” below ten trucks. A small shop with complex reporting or service agreements may have different needs from a larger crew doing straightforward repeat work.

• If the schedule is the bottleneck: prioritize assignment changes, conflict handling, travel allowances and customer communication.
• If phone tag dominates: test call handling and messaging, including which tasks involve a person, automation or a separate provider.
• If paperwork dominates: test mobile capture, review and invoice preparation against real completed jobs.
• If reporting drives the decision: bring a report you actually need and verify its inputs, permissions and export format.

Use the source-backed FieldTech comparison pages as another starting point, not a substitute for verifying current vendor terms. The work order software buyer's guide offers a broader evaluation checklist.

Ask for a written quote covering your current crew and a plausible hiring scenario. Count everyone who needs access, including the owner, dispatcher and office staff—not only the technicians.

First-year cost = subscription + extra seats + required add-ons + usage and processing charges + setup, training and migration costs. Include taxes where applicable, and avoid counting a fee twice if it is already included in the quote.

• Confirm whether the base price is monthly billing or a monthly equivalent of an annual commitment.
• List seat minimums, messaging or call allowances, payment processing rates and any charge for reporting, integrations or support.
• Estimate processing fees using the payment volume and transaction mix you expect to put through that provider.
• Check renewal pricing, cancellation notice, minimum terms, export costs and what happens when a user leaves.

An illustrative cost worksheet

A hypothetical $100 monthly subscription is $1,200 per year. Two extra $20 monthly seats add $480, a $30 monthly add-on adds $360, and $300 of setup brings the subtotal to $2,340 before processing fees and applicable taxes. These are arithmetic examples, not vendor quotes.

For FieldTech's actual published offer, see current pricing and billing terms. Standard is $29.99/month equivalent, billed $359.88 annually, for up to five users. A three-technician business still needs to count its owner and office users against that limit. Review the quoted plan rather than assuming every feature or external service is included.

Repeated rebooking, duplicated entry, unclear arrival updates and a rising bill are reasons to evaluate alternatives. They are not proof that changing software will pay for itself.

Use a consistent time horizon. Annual time value = hours actually saved per week × value per hour × working weeks per year. Compare this with the incremental annual running cost plus one-time switching costs. For a replacement product, subtract costs you will genuinely stop paying; do not count an old subscription as avoided while its contract remains active.

For example, saving three hours a week valued at $40 over 48 working weeks represents $5,760 of annual time value. If incremental annual running costs are $1,200 and migration and training cost $800, the first-year difference is $3,760. At 12 hours saved per four-week working month, time value is $480; after $100 in monthly incremental running costs, recovering the $800 transition cost takes about 2.1 working months.

These are illustrative assumptions, not guaranteed savings. An owner's freed evening has value but is not automatically cash revenue. Count genuinely additional collected work separately, using contribution after relevant costs, and avoid counting the same saved hour twice.

Do not cancel the old account just because the new calendar looks ready. Confirm that you can export and retrieve your own records before making a commitment.

1. Inventory the records. Include customers, equipment, service history, appointments, open estimates, invoices, balances, attachments and relevant permissions.
2. Test an export and import. Check supported formats and fields with both vendors. A CSV of customer names is not a backup of photos, signatures or equipment history.
3. Keep a secure backup. Limit access to authorized staff and verify that files open and representative records are complete.
4. Pilot one crew. Use real but controlled work, confirm the active schedule, and reconcile a sample of records, invoice totals and customer balances.
5. Set a source of truth. If running tools in parallel for roughly two weeks, name which one owns scheduling, customer notifications and invoice sending. Avoid duplicate reminders or payment requests.
6. Reconcile and cut over. Resolve differences, train the remaining users and confirm archive access, notice periods and cancellation dates before closing the old service.

Never assume FieldTech or another product imports every old record, transfers payment authorizations or recreates integrations. Verify those capabilities explicitly and agree a fallback plan for unsupported data.

FieldTech approaches the problem from the paperwork end: capture job details by voice and review the resulting notes and invoice draft. It is worth evaluating when the main frustration is repeatedly typing information the technician already knows.

Review customer details, scope, quantities, labor, parts, prices and totals before sending. Confirm appointments and job decisions through the appropriate approval workflow. Equipment history can provide useful context, but someone still needs to keep the records accurate.

Voice capture does not by itself solve schedule collisions, provide live GPS tracking, send customer ETA notifications or guarantee same-day payment. If a large dispatch board, complex routing, reporting or a particular integration is essential, ask for that precise demonstration instead of assuming the voice workflow covers it.

Similarly, a job total is not verified revenue or proof of profit. Use reviewed job costs and verified revenue before making a margin claim. See the job costing guide for that distinction.

Test with the languages your crew actually uses

FieldTech supports voice capture in 12 languages, including Spanish. Ask a technician to dictate realistic trade terminology in their preferred supported language, then review the output together. Voice-language support is not the same as every interface screen being translated, and accuracy depends on the recording and the job details.

Try the FieldTech demo using the same weighted checklist as every other candidate. Choose it only if the demonstrated workflow addresses your own problems at an acceptable total cost.