Trucking dispatch service calling playbook: call blocks, cadence and KPIs

What this playbook covers

A dispatch service signs carriers one at a time, keeps them hauling with freight that fits their lanes, and loses them quietly when nobody calls. This playbook structures the calling week around all three motions, with the list hygiene and cadence rules that keep owner-operators answering. It assumes a three-line browser dialer on your own Telnyx numbers, a rep doing the talking on every answered call, and recordings with after-call AI summaries.

List hygiene for a carrier book

The carrier list imports as a CSV with company, contact, phone, equipment and home base on every row, because the opener proves you know the difference between a dry van on the Laredo corridor and a reefer in the upper Midwest. Equipment rows the office cannot serve, oversize without escorts, for example, get filtered out before the block so they stop wasting dials. Dedupe across directory sources, apply your internal DNC list, and set attempt caps per list: a discouraged carrier called twice for the same week is a block candidate.

Most dispatch calls go to a business, and most B2B calls fall outside the FTC Telemarketing Sales Rule under 16 CFR 310.6. The edges stay sharp: owner-operators answer on personal cells, and the TCPA’s restrictions on autodialed and prerecorded wireless calls can still apply under 47 CFR 64.1200. Human-dialed lines with a rep talking are the design. Solicitation calls stay inside 8 a.m. to 9 p.m. local at the called party’s location, and stop requests are permanent.

The calling week in blocks

Carrier sign-up block, morning, two hours. The cold list in equipment order, three lines. The opener confirms equipment and home base; the middle asks who dispatches now and what is not working; the close sends the proof-first packet, agreement plus last month’s actual load rates, and books the walkthrough call. Rate expectations get logged, not argued.

Onboarding block, same day as the yes. Carriers who agreed get called for documents, insurance certificates and the first load, with the original summary on screen. These calls are administrative and fast, and mixing them into sales reporting is how offices lose track of who already agreed. Onboarding verifies authority and insurance before any load is offered; FMCSA minimum financial responsibility under 49 CFR 387.303 is a real requirement with real dollar amounts.

Dormant block, weekly, 45 minutes. Carriers who stopped hauling or went quiet get a short check-in before their contract renews elsewhere. The original summary says what mattered to them, the lanes, the home time, the rate floor, so the call opens with their own context. The weekly export shows who has not hauled in 30 days; the block works that list.

Capacity and shipper calls, separate by nature. Carrier sign-up, capacity check-ins and shipper or broker calls are three lists with three disposition sets. A rep asking a carrier about a load board rate and a broker about tractor registration in the same block does both badly.

Attempt cadence and the carrier’s clock

Cold list: two attempts a week apart at different hours, then a dated re-entry, quarterly at most. Drivers run on load schedules, not office schedules, so varied hours are not a trick, they are the only way to find the truck parked. Already-dispatched carriers: a long callback, because “already dispatched” is a policy, not a mood, and the re-entry lands when contracts renew. Dormant carriers: one check-in per quarter. Nobody gets a second call the same day across lists; attempt caps and dedupe handle it.

Dispositions in dispatch terms

Wants agreement, send packet, already dispatched, equipment mismatch, not hauling now, callback requested, unreachable, left voicemail, do not call. “Equipment mismatch” removes the row for a reason, which keeps the list honest. “Not hauling now” is a dated revisit, not a dead end, because trucks come back on the road. “Wants agreement” without a task is how offices lose carriers to the faster service, so every agreement disposition carries a due date.

Three lines and the AI summary workflow

Three lines mean the rep spends the block in conversations instead of rings, and voicemail drops carry the callback number slowly. After each connect, the AI writes the transcript and pulls the fields: equipment, home base, lanes, current setup, rate expectation, objection, next step. The rep verifies rates and dates against the recording before anything goes in the packet, because a misheard rate expectation poisons the follow-up call.

The onboarding queue reads the same summaries, so the documents call opens with the carrier’s lanes and schedule already known. And the weekly report builds itself from dispositions: agreed, onboarded, hauling, quiet. For an office running on a load board and a spreadsheet, that report is the difference between a book and a pile of numbers.

KPI ranges and the production benchmark

• Dials per active calling hour: 70 to 100, median near 85 in DialBreeze production use, 3-line sessions, 90 days.
• Dials per rep day: 400 to 700 for a full day of blocks; most dispatch offices run two to three focused blocks, landing 200 to 400.
• Person-connect rate: 12 to 22 percent planned, 17.8 percent production median. Evening windows connect differently; measure them apart.
• Agreements sent per week: your own baseline from the first month; equipment mix and territory decide the honest number.
• Onboarding completed within 3 days of the yes: 100 percent. Interest decays fast, and the first load cements the relationship.

The production figures come from 37,411 dials over 90 days to 2026-09-26 in DialBreeze operation, aggregate activity, not customer results and not a promise about your list.

Compliance checklist for the dispatch office

Human-dialed calls to personal cells, stop requests honored and logged, calling hours respected, recording disclosure for all-party states. The B2B exemption is partial: keep the wireless rules in view for every cell on the list. Verify authority and insurance at onboarding under the FMCSA requirements. Keep list provenance documented, because a purchased file with no source record is a problem before the first call. Nothing here is legal advice; run the list policy past counsel where your calling territories are strict.