Taxi Driver Accept Range: Company Territory and Dispatch Diffusion

Taxi dispatch fails in two opposite ways. Push every job to every logged-in driver and the rank fills with noise nobody should have taken. Clamp the circle so tightly that a fare two blocks past a franchise line never rings. Ptaxi’s taxi dispatch software treats that as an operations setting, not a slogan. Admin business settings include a driver accept range switch. The driver home screen adds a harder territorial rule: a driver can only take a job if the pickup address or the drop-off address sits inside the affiliated company’s range. Orders themselves are pushed according to dispatch configuration, and that configuration can set how far the offer diffuses. Mixing those three ideas is how night desks invent a fourth religion.

This piece is about training the contrast. It is not a claim that taxi work uses a company-owned-driver priority switch—that language is not in the confirmed taxi lists. It is not a rewrite of urban-versus-intercity commission, and it does not revive dispatch geofences the taxi list marks as unused.

Why accept range and company territory get confused

Franchise taxi work is rarely one city-wide pool. Companies have territories. Drivers affiliate to a company. Passengers pin a pickup that may sit just inside or just outside that line. The offer that “should have rung” is often an affiliation problem, not a broken radio.

Typical pains this pair is meant to blunt:

1. Drivers accept, or even see, jobs their franchise is not supposed to serve, then argue at the curb about who owns the street.
2. Supervisors widen diffusion to get more rings and accidentally flood drivers who cannot take the offer under the company-range rule.
3. Finance treats a missed airport drop as a supply problem when neither end of the trip sat in the driver’s company.
4. Ops coaches “just take anything nearby” as if nearby and in-company were the same filter.

Accept range answers *how far an offer is allowed to matter*. Company territory answers *whether at least one end of the trip sits inside the company the driver joined*. Diffusion answers *how the desk expands the first push when the inner ring stays quiet*. Keep the three cards separate.

What the documented company-range rule includes

Confirmed taxi driver surfaces say the online home list shows passenger orders that have not been accepted for five minutes. They also say a driver can only accept an order if at least one of the pickup address or the drop-off address is within the affiliated company’s range.

Say that sentence in launch workshops. Do not invent a “both ends must be inside” rule unless your own SOP adds it. The documented filter is pickup or drop-off. A job that starts outside the company and ends inside it can still be eligible. A job that starts inside and ends far outside can still be eligible. A job with neither end in the company is not.

That is why change company on the driver list is not a cosmetic field. Admins can change a driver’s company. When you move a driver, you move the territory that filter uses. Training that ignores company assignment will keep producing “why didn’t this offer show?” tickets that are not dispatch bugs. The five-minute home list and the older order pool sit next to this filter, not instead of it. Offers older than five minutes with no accept move to the pool. Orders still unaccepted after ten minutes auto-cancel. Range does not pause that clock. If you set territory so tightly that nobody eligible is online, the pool and the timeout still run. Pair this coaching with order pool and unaccepted timeout so desks do not treat a silent rank as a single broken slider.

Dispatch diffusion is a different control

When a passenger confirms a taxi request and taps to call a vehicle, the order is pushed to drivers according to dispatch configuration. The backend operations area documents that configuration, and it can set diffusion. Taxi meter orders use onboard meter pricing. That fact does not change who is allowed to hear the offer.

Diffusion is how the desk widens the first push when the inner ring does not accept. It is not a license to ignore company range. A diffused offer that lands on a driver whose company covers neither end of the trip still fails the documented accept filter.

Do not bolt electronic dispatch geofences onto this story. Confirmed taxi geofence types include epidemic-control fences and dispatch fences, with labels such as train station, airport, and epidemic zone. The same list states that the dispatch geofence has no usage scenario for the taxi business. Airport or station labels elsewhere are not a reason to teach taxi drivers that a dispatch fence will save a quiet night. Urban versus intercity commission is also a different card. Taxi orders are classified as urban or intercity by origin and destination. Urban orders are those where both ends sit inside an urban geofence you configure per company. That split changes commission. It does not replace accept range or company territory. Point people at urban vs intercity commission if the argument is about take rates, not about who was allowed to accept.

The admin accept-range switch

Admin business settings list driver accept range among related taxi operating controls: one-tap order, online payment, cash payment, order simple flow, income freeze, scheduled-order acceptance, reminder settings, and service-score rules.

Treat the accept-range control as an intentional ops choice:

• Tighten it when franchise contracts punish out-of-area work and your online list is full of junk rings.
• Loosen it when eligible drivers are too sparse and passengers wait through diffusion plus the five- and ten-minute clocks.
• Do not flip it “to make training shorter” if company maps still say a driver may not serve that street.

The list does not spell out a numeric slider or a grab-mode-only caveat for taxi. Do not invent one. Demo the switch next to the company-range sentence and the dispatch-diffusion setting so buyers see three levers, not one magic radius.

Scheduled-order acceptance and reminder settings sit on the same list. They answer whether scheduled work is allowed and how reminders are configured—not how far a live taxi offer should travel. Simple flow and income freeze already have their own playbooks; point at them, then return to range.

Realtime location still helps supervisors see online drivers by company. It does not invent an accept for a trip with neither end in range.

Ops tradeoffs to say out loud

• City-wide push with no company filter: more rings, more curb fights about franchise lines, more “I took it but dispatch says I shouldn’t have” tickets.
• Company-range filter with diffusion set too wide: drivers hear jobs they cannot accept; listening quality drops; people mute the app.
• Very tight range plus a thin night rank: legally clean, commercially quiet. The five-minute home list stays empty and the ten-minute auto-cancel does the rest.
• Range + company territory + diffusion taught as three sentences: desks can widen a ring without rewriting who is allowed to say yes.

Practical notes that match the surfaces:

• When a driver asks why an offer never appeared, first ask which company they belong to and whether pickup or drop-off sits in that company’s range.
• When a supervisor wants “more rings,” change diffusion or staffing before you tell drivers to ignore territory.
• Use change-company deliberately. Moving a driver is how you move their eligible map.

What this is not

• Not a claim that taxi dispatch includes a company-owned-driver priority switch. That priority-matching language is not in the confirmed taxi lists.
• Not a dispatch-geofence story. The taxi list marks dispatch fences as unused for this business.
• Not urban-versus-intercity commission, monthly cards, or meter bill confirm.
• Not WeChat, official-account, or local short-code packaging for overseas App buyers.
• Not named map vendors, tips, bank cards, or card processors.
• Not permission to skip passenger safety tools you enable elsewhere. Keep emergency claims to documented surfaces, separate from range training.

Launch sequence sales can repeat

1. Pick two sample trips: one with pickup inside company A and drop-off outside, one with neither end in company A.
2. Show a driver affiliated to company A. The first job can be eligible. The second cannot.
3. Open admin business settings and point at driver accept range without inventing extra numeric folklore.
4. Open dispatch configuration and show that diffusion can be set. Then say out loud that diffusion does not override company range.
5. Move the same driver to company B with the documented change-company action and repeat the first pair of trips so the affiliation link is visible.

If a buyer wants “one radius for the whole city,” ask who mediates the first night a franchise partner claims a street the rank just served. The answer is usually the same person who asked for the merge.

Soft next step

If your night desk keeps widening the push and still getting the wrong cars—or no cars—open driver accept range, teach the pickup-or-drop-off company rule, and set dispatch diffusion as a separate lever. When a lead can demo those three without inventing a geofence the taxi product does not use, you are ready to run taxi dispatch software across company lines without training drivers to guess.