Dispatch Rate Explained: Formula, Benchmarks and Fixes

Dispatch rate equals jobs dispatched divided by the chosen denominator, multiplied by 100, and you must name that denominator before comparing results. It measures how often requests become assigned work, not merely how often someone answers the phone.

Your phone's been busy, the office has been returning messages, and the calendar looks full. Yet a technician still has a gap tomorrow, while another is driving across town to squeeze in a low-value call. A useful dispatch rate helps you separate capturing demand from dispatching profitable work.

Table of Contents

• What Dispatch Rate Measures for a Trade Business
  • Separate answering from assigning work
  • Define the opportunity you're measuring
• How to Calculate Dispatch Rate Without Fooling Yourself
  • Build a repeatable counting rule
  • Keep channel comparisons honest
• Dispatch Rate Benchmarks for HVAC, Plumbing and Electrical
  • Measure productive time and unnecessary visits
  • Read the measures together
• Why Dispatch Rate Drives Revenue and Response Time
  • Translate conversion into booked value
  • Make speed useful to the customer
• When a Higher Dispatch Rate Hurts Margin
  • Account for the paid day
  • Give dispatchers an acceptance rule
• How to Raise Dispatch Rate With Faster Answers and Booking
  • Build a complete intake procedure
  • Match each leak to a specific capability
• Start a Two-Week Dispatch Rate Baseline
  • Keep a paired weekly dashboard
  • Test the largest recoverable loss

What Dispatch Rate Measures for a Trade Business

For a trade business, dispatch rate = jobs dispatched ÷ chosen denominator × 100. Say, hypothetically, two HVAC shops each receive 100 calls in a week. Shop A dispatches 70 jobs and Shop B dispatches 40, even though both answered every call.

That difference doesn't automatically mean Shop B has worse dispatchers. Its callers might include more billing questions, duplicate contacts, requests outside its service area, or customers who won't accept its diagnostic fee. Without knowing which requests count, you can't judge the result.

Separate answering from assigning work

Answer rate measures whether someone handled the contact. Dispatch rate measures whether an eligible request became an operational assignment, such as a technician assignment or a confirmed calendar slot.

Use this funnel to keep the stages distinct:

• Received contacts: Calls, messages, and other inquiries reach the business.
• Qualified requests: Staff establish that the customer needs a service the shop provides.
• Booked or dispatched jobs: The request receives a confirmed slot or technician assignment.
• Completed visits: The technician performs the scheduled work.

Choose whether your dispatch event is booking or technician assignment, then stick to it. Don't count an unconfirmed message as dispatched work, and don't switch definitions without notice when the calendar gets crowded.

Define the opportunity you're measuring

The numerator is the count of qualifying dispatch events. The denominator is the opportunity set, such as all inbound contacts or unique qualified requests.

A qualified request that never becomes work represents a potential sale, but not necessarily a sale you should accept. A distant job with poor access and no suitable technician may be better referred elsewhere than forced onto the board.

A dispatch rate is meaningful only when its label tells you what became work and which opportunities were counted.

The useful question isn't just whether the percentage increased. It's whether the shop converted suitable demand into work it could complete well.

How to Calculate Dispatch Rate Without Fooling Yourself

Dispatch rate = jobs dispatched ÷ chosen denominator × 100. The arithmetic is straightforward. Most reporting mistakes come from inconsistent counting.

Build a repeatable counting rule

1. Set a fixed reporting period. Use a calendar month or another consistent interval. For request-conversion reporting, follow requests received during that period and give them a consistent time to become booked work.

2. Define the denominator. Choose all inbound contacts, qualified service requests, or unique job opportunities. Write down what qualifies so different employees classify the same request consistently.

3. Clean the records. Remove spam, robocalls, tests, and duplicate contacts under a documented rule. A customer calling again about the same fault shouldn't become another unique opportunity.

4. Count requests that became dispatched jobs. Use the booking or assignment event your shop selected. Match each successful request to its job record rather than relying on a dispatcher's recollection.

5. Divide and multiply by 100. Keep the raw counts beside the percentage. They make changes in volume visible and help you spot classification errors.

6. Split by channel and job type. Separate phone, web chat, SMS, email, and missed-call callbacks. Then distinguish emergency, diagnostic, maintenance, and estimate requests.

For a hypothetical worked example, suppose the shop receives 200 inbound contacts, identifies 120 qualified requests, and dispatches 84 jobs. Its qualified dispatch rate is 70%, while its all-contact dispatch rate is 42%.

Dispatch rate variants with example results

The hypothetical phone and chat results show why an overall percentage can hide a weak intake channel. They're illustrative channel results, not a breakdown that reconciles to the total without additional counts.

Use this process graphic as a counting checklist.

Keep channel comparisons honest

In public-safety call handling, a study of telephone reporting methods found that approximately 52% of call records were dispatched overall, compared with 63% of non-emergency-number records and 41% of 911 records. Those are public-safety findings, not trade-business benchmarks, but they illustrate how channel mix changes an overall result.

Comparison rule: Never compare dispatch rates until the denominator, dispatch event, exclusions, and reporting period match.

Dispatch Rate Benchmarks for HVAC, Plumbing and Electrical

There isn't a defensible universal percentage that tells every HVAC, plumbing, or electrical shop how many inquiries should become dispatches. Separate conversion performance from productive utilization and avoidable dispatches before setting targets.

Measure productive time and unnecessary visits

Productive utilization equals billable or productive technician hours divided by total available hours, multiplied by 100. Define productive time carefully, especially when maintenance agreements, warranty work, and paid diagnostics have different billing arrangements.

The FieldPulse field-service KPI guide provides utilization references of 65–80%, with above 85% warranting attention to overload; the accompanying 2025 benchmark cited by VSight places avoidable dispatches at 14% median, 3% for the top quintile, and 24% for the bottom quintile.

Avoidable dispatch rate equals dispatches that didn't require an on-site visit divided by total dispatches, multiplied by 100. Don't classify a necessary diagnostic visit as avoidable merely because the technician couldn't finish the repair.

For missed calls, Ask Claire's review of the home-services call-to-job gap identifies no independent public HVAC benchmark and describes vendor figures of 14% and 27% drawn from different populations and definitions.

Dispatch benchmarks and how to read them

Read the measures together

Low utilization alongside high avoidable dispatches should prompt a triage review. Technicians may be busy traveling without enough productive work. Low utilization with few avoidable visits instead calls for checking demand, cancellations, scheduling gaps, and skills coverage.

Don't assume plumbing and electrical shops should inherit an HVAC conversion target. Build a trailing operating baseline from your own board, separating trade, season, job type, and service area.

Reconcile job records with financial records before treating bookings as revenue. Book Tech's HVAC bookkeeping checklist is a useful companion for organizing that financial review.

If unanswered calls appear to be the constraint, evaluate an HVAC answering service against your own qualified-request conversion, rather than against an unrelated vendor percentage.

Why Dispatch Rate Drives Revenue and Response Time

An undispatched qualified request resembles an empty restaurant table after an interested guest leaves. You had potential demand, but the business didn't turn it into a transaction.

The analogy is useful because filling every table isn't the only objective. You also need enough staff to serve the customers you accept.

Translate conversion into booked value

Consider a hypothetical scenario, not a revenue benchmark. Assume a shop receives 100 qualified requests per month, has an average booked ticket of $450, and raises its dispatch rate from 60% to 70%.

That produces 10 additional booked jobs and $4,500 in potential monthly work, assuming the ticket value stays unchanged. It isn't $4,500 in profit, and it isn't collected revenue until the jobs proceed and customers pay.

Materials, labor, cancellations, and any added overtime determine what the shop keeps. If accepting those jobs displaces better work, the apparent gain can overstate the benefit.

Make speed useful to the customer

During a storm-driven surge, a caller waiting for a callback may continue contacting other contractors. Intake speed matters because the request can disappear before a dispatcher assesses the job.

A useful response gives the caller something concrete: a confirmed service window, the applicable diagnostic or dispatch fee, and clear instructions about access. Don't promise a precise arrival time unless the schedule supports it.

An after-hours answering service can support this process when the office is closed. Its value depends on whether it can qualify and schedule suitable work, not merely acknowledge that someone called.

Keep the operational review focused on outcomes:

• Weekly booked revenue: Separate estimated job value from completed and collected revenue.
• Time to first meaningful response: Measure when the customer receives help, not just an automated acknowledgment.
• Rebooking or review rate: Look for signs that customers valued the service after the appointment.

Office staff also need a usable handoff. When intake creates a complete appointment rather than a vague message, they can resolve exceptions instead of repeatedly reconstructing what the customer wanted.

When a Higher Dispatch Rate Hurts Margin

Pushing dispatch rate higher without acceptance rules can lower profit. A booking can look successful in the office while creating expensive travel, overtime, or an avoidable return visit in the field.

The technician's route is part of the job's cost, not an administrative detail.

Account for the paid day

An industry analysis from Built on Tenth citing ServiceTitan operational data estimates that HVAC technicians spend 28% of the working day in transit, approximately 2.2 hours in an eight-hour day, leaving 5.76 hours for other activities; it also describes well-dispatched technicians completing 3–5 calls daily, with average inter-call transit below 20 minutes and parts runs less than once weekly.

That remaining time isn't all billable repair time. Technicians still need to document work, load equipment, communicate with customers, and handle other non-billable tasks.

Route compression means grouping geographically compatible work while preserving suitable appointment durations. An unplanned booking across town can force a dispatcher to move a nearby emergency, extend another technician's day, or break a promised window.

Use the following video as an additional discussion resource while reviewing your dispatch workflow.

Give dispatchers an acceptance rule

Missing equipment details, access restrictions, or parts requirements can also turn an apparently successful booking into a repeat trip. Ask whether the technician can arrive prepared, not merely whether a slot is empty.

1. Dispatch suitable work. Accept the job when it fits the route, technician skill, response radius, and margin floor. Escalate genuine emergencies under a separate safety and on-call procedure.
2. Offer an alternative for unsuitable work. Reschedule, refer, or decline requests that can't be served economically or competently. Explain the available options rather than promising an appointment the team can't deliver.

For Australian contractors connecting operational reporting with financial administration, Nexist's guide to tracking construction KPIs and BAS obligations provides a useful accounting companion.

Margin check: Track contribution margin per dispatched job alongside conversion. More answered calls don't prove that the shop accepted better work.

Use a consistent contribution-margin definition that includes the direct job costs your accountant identifies. Otherwise, dispatchers can improve the percentage while the owner absorbs the extra cost.

How to Raise Dispatch Rate With Faster Answers and Booking

Fix intake in the order the customer experiences it. A perfect routing board can't recover a request that nobody captured, and a fast answer won't produce a useful assignment if the job details are missing.

Build a complete intake procedure

1. Answer promptly across supported channels. Arrange coverage for evenings, weekends, and simultaneous calls. Use a staffed office, an answering service, or an automated receptionist according to the complexity of the work.

2. Qualify before offering a slot. Capture the symptom, equipment type, urgency, address, access restrictions, and customer availability. For electrical hazards or other safety-sensitive situations, use approved escalation instructions rather than improvising remote repair advice.

3. Quote from the shop's price book. Explain diagnostic fees and applicable after-hours charges. Distinguish a fixed service fee from an estimate that requires inspection, so customers don't mistake preliminary pricing for a guaranteed repair total.

4. Write the booking directly to the calendar or board. Reserve the correct job duration and type. A message asking the office to call someone back isn't a confirmed appointment.

5. Send the technician a usable handoff. Include contact details, symptoms, equipment information, access notes, agreed charges, and the conversation record. Flag uncertainty rather than filling missing fields with guesses.

6. Apply routing and capacity rules. Assign urgent work by skill and response radius. Place flexible maintenance and estimates into suitable geographic gaps, without consuming protected emergency capacity.

Match each leak to a specific capability

Mercateer is one option alongside human receptionists and existing dispatch-software workflows: its AI receptionist for contractors handles intake, price-book quoting, and direct booking according to the shop's configured rules.

Dispatch leaks, fixes and the lever that addresses each

For a broader evaluation of where automation belongs, Prometheus Agency's home services AI guide is a useful companion. Compare tools against actual intake tasks and escalation needs rather than a generic list of AI features.

Forwarding-based setups can retain the existing carrier, phone number, and operating tools. Confirm calendar permissions, fallback handling, and what happens when no suitable appointment exists before switching live traffic.

Capacity still decides the outcome. Intake can capture and qualify demand, but the system should offer a later appointment or escalate when the board has no appropriate opening.

Start a Two-Week Dispatch Rate Baseline

Run a two-week measurement exercise before changing your intake process. Record every qualified request by channel and job type, match it to its booking or assignment, and give unsuccessful requests a clear reason code.

Include productive utilization and avoidable dispatches, but don't treat this short window as a permanent seasonal benchmark. Its purpose is to reveal where to investigate first.

Keep a paired weekly dashboard

Use the job board as the source of truth for dispatch events, with financial records supporting margin calculations.

• Conversion and retention: Booked-and-dispatched rate, cancellations, and no-shows.
• Service quality: First-time-fix rate and late-arrival rate.
• Field capacity: Average transit minutes and jobs completed per technician-day.
• Economics: Contribution margin per dispatched job and the estimated value of qualified requests lost.

Break results down by source, time of day, and job type. Review technician-level patterns with context, since specialist assignments and difficult territories can make direct comparisons unfair.

Test the largest recoverable loss

If missed or after-hours contacts dominate the losses, test a forwarding-based receptionist layer for another two weeks. Keep the qualification rules, service area, and pricing consistent so the comparison reflects the intake change rather than a different sales policy.

Compare answer rate, jobs booked, after-hours volume, and completed-job outcomes. Review transcripts and unsuccessful requests as well as the totals, especially where the system escalated or declined work.

Choose the leak with the largest recoverable weekly revenue impact, not the largest contact count alone. Assign an owner to fix that leak first, then check whether the additional work meets the shop's margin and service standards.

---

Mercateer offers around-the-clock answering, quotes from your own price book, and direct calendar booking alongside your existing phone setup. Visit Mercateer to evaluate an intake test against your dispatch baseline, with qualified bookings, technician readiness, and job margin as the measures of success.