The one-client-per-city policy, explained

Here is a question almost nobody asks a call center before signing: who else in my city do you answer for? It is an uncomfortable question, which is why sales reps are rarely asked it and rarely volunteer the answer. At most providers, the honest answer is that the same agents taking your calls are also taking your competitor’s. This piece explains why we think that is a genuine conflict of interest rather than a theoretical one, how TransportBPO’s one-client-per-city policy works in practice, where its honest limits are, and what to ask any provider — including us — about conflicts before you sign.

Why is a shared desk serving competitors a conflict?

Think through the mechanics of a Saturday-night surge. Two tow companies in the same city, both answered by the same desk, both slammed at once. The desk has finite agents. Whose line gets picked up first? Whose caller waits? Nobody wrote a policy choosing sides — but a choice is being made on every call, and neither client can see it happening.

The quieter problem is knowledge. Agents answering for competing companies learn both operations from the inside: what one charges, which accounts it serves, where its coverage is thin, when its trucks are committed. No individual agent has to act in bad faith for that to matter — the information simply lives in one room, shaping how calls get handled. In any other part of your business you would call a vendor serving both sides of a rivalry what it is: conflicted.

Why do most providers run shared desks anyway?

Economics, not malice. A pool of agents spread across many accounts in the same vertical is cheaper to staff: call scripts overlap, training amortizes, and idle minutes on one account absorb surges on another. That efficiency is real, and for non-competing accounts it is a perfectly legitimate model — it is how most of the industry prices its service.

The problem is that the efficiency is strongest exactly where the conflict is worst: same vertical, same market, same busy hours. Two tow companies in one city are the ideal pairing for the provider’s staffing spreadsheet and the worst pairing for the clients. When a provider declines to offer exclusivity, it is usually not hiding anything sinister — it is telling you its margin depends on pooling you with your rivals. You just want to know that before you sign, and price the trade-off consciously.

How does the one-client-per-city policy work?

TransportBPO takes one client per vertical per city, where the seat is available. Once a tow company in a given city signs with us, we do not take another tow company in that city. A taxi fleet and a tow operator in the same city are not competitors, so both seats can be filled — the policy runs along vertical lines because that is where the actual rivalry runs.

The seat goes to the first client who takes it. If your direct competitor approaches us afterward, we decline the account for that city and vertical — that is the policy working as designed, and it is exactly the protection you signed for. It costs us revenue with every rival we turn away, which is precisely why the policy is credible: exclusivity that costs the provider nothing is marketing, not policy.

What does exclusivity change on the desk, day to day?

More than most operators expect. Agents who answer for one tow company in a city — rather than three — learn one operation deeply: your rates, your regulars, your geography, your trucks and their quirks, the accounts that get white-glove treatment. That depth shows up as faster calls, fewer booking errors, and callers who cannot tell the desk is not in your building.

It also changes what happens under load. In a surge, every agent-hour on your account is yours; there is no rival account silently competing for the same pickup capacity. And the market intelligence that accumulates on the desk — who calls, what they pay, where demand is growing — accumulates for you alone. Your call data never has a competitor reading over its shoulder, and the agent who knows your busiest corridor by heart is not applying that knowledge to anyone else’s trucks.

What are the honest limits of the policy?

Three, and we would rather state them than have you discover them. First, "where available" means exactly that: if your competitor got to us first, the seat in your city and vertical is taken, and we will tell you so rather than quietly stretch the definition. Second, the boundaries require judgment — metro edges, operators who straddle verticals, fleets that run both taxi and NEMT work. We resolve those case by case, in writing, before signing rather than after. Third, this is a service policy, not a legal grant of territory: it binds who we take as clients; it does not stop anyone else from serving your market.

If exclusivity matters to you, get it stated in your agreement — with any provider. A policy on a website is a promise; a clause in a contract is a commitment.

What should you ask any provider about conflicts?

Whether or not you talk to us, put these to every transportation call center on your shortlist — the answers separate exclusivity as policy from exclusivity as sales language:

• Do you currently answer for any company that competes with mine, in my city or metro?
• Will you commit in writing not to take my direct competitors while I am a client?
• What happens when a competitor approaches you after I sign — declined, waitlisted, or accepted?
• How is my account data, pricing and call history walled off from other accounts?
• Are the agents on my account shared with other clients in my vertical, even in other cities?
• Has the exclusivity commitment ever been tested — and how was it handled?

Common questions