What dispatch sales actually sounds like
A dispatch service signs carriers one at a time. The product is a promise: steady freight, decent rates, and someone who answers when a load goes sideways. The phone work that sells it is repetitive: a long list of owner-operators, most of whom are driving, sleeping or already dispatched by someone else.
The two facts that decide the call are equipment and home base. A dry van running the Laredo corridor cares about southbound lanes. A reefer in the upper Midwest cares about produce season. A flatbed owner cares about construction and steel. A rep who asks about those first sounds like a dispatcher instead of a salesperson.
DialBreeze rings up to three numbers for one rep and records every connected call. It does not talk. The rep does.
Three lists that behave differently
Working a dispatch book means keeping three queues apart, because they need different openings and different dispositions.
- Cold carrier list. Directory rows, mostly main numbers. The goal is a name, equipment, home base and permission to send a packet.
- Onboarding queue. Carriers who said yes. These calls are administrative: documents, insurance certificate, first load. They should be fast and they should not be mixed into sales reporting.
- Dormant carriers. Owner-operators who stopped hauling, took a break or went quiet. A short check-in before their contract renews elsewhere is worth more than another cold row.
Mixing those three into one queue is how a dispatch office loses track of who already agreed and who has not been asked.
What belongs in the note
The details that decide whether a carrier signs are the details a hurried note drops:
- Equipment: dry van, reefer, flatbed, step deck, power only, and how many tractors.
- Home base and preferred lanes: where they live, where they want to run, and where they refuse to go.
- Current setup: independent dispatcher, a friend, a carrier they are leased to, or nothing at all.
- Rate expectation: a target per mile or per load, which is the number that kills or closes the deal.
- Objection: usually “how do you source loads” or “what is your percentage.”
- Decision step: send the packet, review the agreement, or call back after a run.
After each recorded call, DialBreeze writes a transcript and then pulls those details into structured fields with a short summary. When the rep follows up two days later, the equipment and home base are on screen instead of in memory. Check rates and dates against the recording before anything goes in the packet.
Dispositions in dispatch terms
Generic outcomes do not tell a dispatch office what to do next. A small set does:
- Wants agreement: the carrier agreed to look at terms. Create the task with a due date.
- Send packet: interested, no commitment. Send it and schedule the follow-up.
- Already dispatched: a policy, not a mood. Set a long callback instead of a daily one.
- Equipment mismatch: we do not serve that freight. Remove it so it stops wasting dials.
- Not hauling now: keep it in a dormant queue with a dated revisit.
- Do not call: the person asked you to stop. It goes on the internal DNC list and leaves every queue.
Measured throughput, stated plainly
Measured in production use, 3-line sessions, 90 days: a median of roughly 85 dials per active calling hour and roughly 600 dials per operator day. A percentile is not a promise, and your list, your equipment mix and your connect rate will move the number. It is useful mainly as a planning figure for how many rows a rep needs to reach a target number of conversations.
Before you call: authority, lists and recording
Dispatch is a business-to-business sale, and most business-to-business calls fall outside the FTC Telemarketing Sales Rule under 16 CFR 310.6(b)(7). That is not a blanket exemption. Owner-operators often answer on a personal cell phone, and TCPA restrictions on autodialed or prerecorded calls to wireless numbers can still apply under 47 CFR 64.1200(a)(1). Honor every stop request, and keep solicitation calls inside 8 a.m. to 9 p.m. local time at the called party’s location.
On the carrier side, verify authority and insurance before onboarding. Operating authority and minimum financial responsibility are FMCSA requirements with real dollar amounts, see 49 CFR 387.303. A dialer does not check any of that.
The after-call AI works from the recording, so the calls you want summarized need to be recorded. Several states require every party to agree before a call is recorded. Use a short disclosure at the start.
What you need to start
- Your own Telnyx account with numbers and caller ID. DialBreeze does not resell minutes.
- A carrier list as a CSV with company, contact, phone, equipment and home base.
- A packet you can send within the hour, because interest decays fast.
- A disposition set the office agrees to before the first block.
The 14-day trial runs in a sandbox with test numbers. Load a sample carrier list, run a three-line block, and read the summaries before you work your real book.
Keeping capacity and freight in the same week
A dispatch service sells two different things at the same time. Carriers want steady lanes and predictable pay. Shippers want trucks on the day the load is ready, at a rate the broker can live with. The phone book for those two jobs is separate, and they should never share a queue.
Carrier sign-up calls are about equipment, home base and rate expectation. Capacity check calls are about where a truck is today and where it can be tomorrow. Shipper or broker calls are about a specific lane. Mixing them into one list means a rep asks a carrier about a load board rate and a broker about tractor registration, and both conversations suffer.
Keep the lists separate and the dispositions separate. A carrier list wants outcomes like “Truck available Tuesday” and “Rate too high.” A shipper list wants “Quote requested” and “Lanes covered.” Reporting only means something if the two do not blur.
What a dispatch agreement conversation sounds like
The signing conversation usually starts with one question: what happens when a load goes wrong. Carriers have been burned by a dispatcher who stopped answering, a rate that changed after the truck was loaded, or a settlement that arrived late. The rep who addresses that directly is more persuasive than one talking about load counts.
The details the carrier gives in that conversation are exactly what the onboarding record needs: percentage or flat fee, how settlement is paid, whether advances are available, what insurance the carrier carries, and when the first load will be offered. Capturing them on the call means the agreement and the first load offer go out with the right numbers, and the follow-up call has a reason to happen.
Reporting a carrier book without a CRM
Most dispatch services run on a load board, a spreadsheet and a phone. That is fine, but it makes carrier count, active capacity and dormant carriers hard to see. A calling workflow that keeps dispositions and summaries per carrier effectively builds that report as a side effect: how many carriers agreed, how many completed onboarding, how many went quiet after a month.
Weekly, the owner can export the list and see who is producing and who has not hauled in 30 days. The value is not the dial count, it is knowing which half of the book needs a check-in call.