What to look for in a dispatch outsourcing contract

The sales call tells you what a provider hopes to do. The contract tells you what they are obligated to do — and the gap between the two is where outsourcing deals go wrong. We have covered the questions to ask a provider before signing elsewhere; this piece is the companion for the next stage, when a document lands in your inbox. It walks the agreement clause by clause: what good language looks like, what the red flags are, and where I would push back before signing. I review these agreements from the provider side every week, so consider this the checklist we would want a client to hold us to.

How long is the term — and how do you get out?

Start at the end: the termination clause. Look for the initial term length, the notice period to cancel, whether the agreement auto-renews, and whether leaving early triggers a fee. A 12-month initial term with a 90-day cancellation window and automatic renewal is a structure built to keep you paying after the service has stopped earning it.

A month-to-month term flips the incentive. When the client can leave with 30 days’ notice, the provider has to re-earn the account every month with performance rather than paperwork. That is why TransportBPO runs month-to-month with no setup fees — and why I would treat any provider’s insistence on a long lock-in as a statement about their confidence in their own service. If a provider argues they need a long term to recover onboarding costs, ask them to quantify those costs; the answer is usually revealing.

What should the SLA clause pin down?

A service-level agreement is only as good as its numbers. "Prompt, professional service" is decoration; a real SLA reads like an operating spec. At minimum it should commit, in figures, to: answer speed (rings or seconds, with a service-level percentage), coverage hours (24/7 means holidays too — check), reporting cadence and contents, and staffing continuity on your account.

Then check what happens when the SLA is missed. A commitment without a remedy is a preference. Look for service credits, a cure period, or at minimum a documented escalation and the right to terminate for repeated misses without penalty. If the SLA lives in a marketing PDF rather than the signed agreement, it does not exist.

Who owns the data when you leave?

This is the clause operators skip and regret. The desk answering your phones accumulates your business: customer names and numbers, booking history, call recordings, account notes, motor-club portal activity. The contract should state plainly that all of it is your property, and that you receive a full export in a usable format on termination, at no charge.

The cleanest protection is structural: insist the provider work inside your own dispatch software and phone numbers rather than a proprietary system of theirs. When agents book into your TowBook, your Limo Anywhere, your TMS — as TransportBPO’s agents do — the records never leave your possession in the first place, and switching providers later means changing who logs in, not rebuilding your customer base from an export file. If a provider requires you to move onto their platform and their phone numbers, understand that as a switching cost being installed on day one.

Does the contract address exclusivity and conflicts?

Most transportation call centers serve multiple companies in the same market from the same pool of agents — sometimes direct competitors. If the same desk answers for you and your closest rival, ask who gets priority when a surge hits, and where the line is on market knowledge moving between accounts.

The contract should say, in writing, whether the provider may take on your direct competitors in your market. TransportBPO’s policy is one client per vertical per city, where the seat is available, and we put it on paper. Whatever provider you choose, an exclusivity clause — or at least a disclosed-conflict clause — belongs in the agreement, not in a verbal assurance from the sales rep.

Per-role rates or bundled minutes — which pricing structure is safer?

Pricing structures fail in predictable ways. Per-minute bundles look cheap until a storm month blows through the included minutes and overage rates take over; they also make your bill hardest to predict in exactly the months your revenue is most chaotic. Flat per-role or per-agent pricing costs the same in a quiet month, but it makes the busy months — the ones that matter — predictable, and it removes the provider’s incentive to let calls run long.

Whichever structure you choose, the contract should state the rate, exactly what it includes (hours, call types, portal monitoring, software work), what triggers additional charges, and whether there are setup or onboarding fees. TransportBPO charges flat monthly per-role rates with no setup fees; if a competitor’s bundle prices out better for your call profile, that is a legitimate choice — just model a surge month before you sign, not after.

What about escalation and insurance?

Escalation first: the contract should name how problems get raised and how fast they get answered — a named account contact, a response-time commitment for operational issues, and a defined path for urgent failures like an outage on your line. "Contact support" is not an escalation clause.

Insurance and liability: confirm the provider carries general and professional liability coverage appropriate to taking your calls, and read the limitation-of-liability clause so you know what it caps. Alongside that, look for a confidentiality clause covering your customer data and business information, and — if you run NEMT or medical work — the data-handling language your compliance obligations require. None of this is exotic; a provider that balks at putting it in writing is telling you something.

• Red-flag recap: initial terms over a few months with auto-renewal and long notice windows
• SLAs described in adjectives instead of numbers, or living outside the signed agreement
• Customer data, recordings or phone numbers owned by the provider
• Silence on serving your direct competitors
• Setup fees, unexplained onboarding charges, or overage rates you have not modeled
• No named escalation path and no liability or confidentiality language

Common questions