Designated Driver Apps

Designated Driver Order Pool: Find Unclaimed Jobs by Destination

A driver heading home, or toward a venue, keeps getting jobs that end in the opposite direction, while unclaimed jobs sit in a flat list. Ptaxi’s designated driver app documents an order pool of passenger-placed jobs that no driver has accepted yet, plus an address search that finds orders whose destination is near that address.

This article stays on that pool and that destination search. It is not a taxi order-pool post. The taxi list uses a different timer shape, and those numbers are not designated-driver facts.

What the order pool actually shows

In the driver app, the order pool shows passenger-placed orders that no driver has accepted yet. That is the documented contents of the list: unclaimed jobs. The list does not describe a sort order, map pins, or an auto-refresh interval. Do not brief those as product facts. Open the pool in a demo, watch how new jobs appear, and write down what you see. Until then, train it as a list of unclaimed passenger orders.

When a passenger places an order, it is pushed to drivers according to the configured dispatch range. The backend can set that system push distance. The list does not name a default distance. Confirm the configured range in a demo, then return to the pool. This is not a dispatch-range article. The push explains why some jobs reach a driver automatically. The pool is the place to look at jobs that still have no driver.

A driver who only waits for a push will see work inside that range. A driver who opens the pool can also look at unclaimed jobs and choose one. Keep those two paths distinct in a briefing. Push is the system sending the job out. The pool is the unclaimed list the driver can inspect, including with a destination search.

The pain the search is meant to address is directional, not just volume. A driver finishing a job across town does not want the next unclaimed order to end even farther away if a job ending near home is sitting in the same pool. The list does not say the pool ranks jobs by how convenient the destination is. It says the driver can search an address and query orders whose destination is near that address. The driver has to make that query. Brief it as a tool the driver uses, not as an automatic routing preference.

Destination search is the hook

Drivers can search an address and query orders whose destination is near that address. Keep this wording exact. It is a destination-nearby search, not a pickup-radius search, unless a later list says otherwise — this one does not.

That is the capability a driver actually needs when the next useful job is the one that ends near home, or near the next venue. A destination filter helps the driver plan the next leg. It does not, on the documented facts, also filter by pickup. Do not sell a guaranteed empty-back-haul matcher. Do not invent a control that saves this destination filter. If a buyer asks whether the search can be saved, or whether pickup is also filtered, confirm that in a demo and keep the brief to a destination-nearby query until you have seen more.

The tradeoff is straightforward. Without a destination filter, the pool is a flat list of unclaimed jobs, and a driver heading one way has to read every row. With the filter, the driver can look for work that ends in a neighborhood they already want to reach. The list still does not say the search also narrows by pickup, and it does not document taxi-style auto-cancel timers for this pool. A job can sit until a driver takes it, or until a dispatcher steps in. Do not invent a timeout and call it a designated-driver fact.

Be careful with the word “nearby.” The list uses that idea — orders whose destination is near the searched address — but it does not define the radius. Do not invent a distance and call it a product default. In a demo, search a precise address, then see how wide the results run, and write that down. Until you have that note, keep the language at “destination near that address.”

Also keep the audience of the pool clear. The driver-app pool is for drivers. The admin order-dispatch screen is the desk path for orders with no driver. Mixing those in a briefing confuses who is supposed to act. A driver searches a destination to choose a job. A dispatcher opens the admin screen to assign a driver when a job is not moving. Train both, and keep the live time on the driver-app search.

Use a concrete demo, not a slogan. Pick an address the test driver actually wants to end near. Search it. Confirm the results are destination-nearby jobs, then accept one and see that it leaves the unclaimed pool. If a result looks like a pickup match instead, write that down as something to re-check. Do not change the brief on a hunch.

The desk path is a neighboring dispatch screen

On the admin order-dispatch screen, staff can view orders with no driver and dispatch a driver. Treat this as a desk backup path, not the main walkthrough. If an unclaimed job needs a person assigned, the desk can do that from this screen. Then return to the driver-app pool. This article’s hook is the pool plus the destination search, not a full dispatch training.

The desk path matters when a job has been sitting and no driver has taken it. It does not replace the pool. Drivers still have a list of unclaimed passenger orders they can search by destination. Staff still have a way to assign a driver when the list is not moving. Keep both paths in the briefing, and keep the demo time on the driver-app search.

If you show the desk path, keep the walkthrough short. Open an order with no driver, dispatch a driver, and stop. Do not turn that click into a full dispatch-range or assignment-rules training. The configured push distance already explains how a new passenger order is offered to drivers. The pool and the destination search explain how a driver finds work that is still unclaimed. The desk is the backup when neither path has taken the job.

Do not import taxi pool timers

The taxi order pool has its own post, including a five-minute pool split and a ten-minute unaccepted auto-cancel. That is a different product list. The designated-driver list does not document those timers. Do not write them as designated-driver facts. If a brief contrast helps a buyer who has read both posts, say the taxi timers belong to taxi, then come back to this pool: unclaimed passenger jobs, and a search by destination neighborhood.

What not to promise on the designated-driver pool

Do not invent a default dispatch distance. Do not invent sort order, map pins, auto-refresh, or a saved destination filter. Do not describe the search as a pickup-radius tool. Do not promise a guaranteed return-trip matcher. Do not import taxi auto-cancel minutes into this product.

A short ops checklist before you brief the app

Keep this to one page.

  • In the driver app, open the order pool. Confirm it shows passenger-placed orders that no driver has accepted yet.
  • Search an address and confirm the results are orders whose destination is near that address. Note that the list does not document a pickup filter.
  • Place a test order and confirm it is pushed according to the configured dispatch range. Write down the distance you see in the backend. Do not brief a default.
  • On the admin order-dispatch screen, open an order with no driver and dispatch a driver as a desk backup path. Then leave that screen.
  • If a buyer brings up taxi pool timers, point at the taxi post as a different system and do not quote those minutes here.

If a script starts promising a back-haul matcher or a saved destination filter, cut it back to an unclaimed-order pool and a search for destinations near an address.

Close

The designated-driver order pool is a list of unclaimed passenger jobs, with an address search that finds orders whose destination is nearby. Dispatch range is configured in the backend, and the desk can still assign a driver on the order-dispatch screen. The list does not document taxi-style auto-cancel timers for this pool, and it does not say the search also filters by pickup.

That is enough to brief a driver who wants the next job to end toward home. It is not enough to sell a back-haul matcher or a saved filter the list does not describe. Look at the order pool on the designated driver app product page. If you want a walkthrough, ask for a demo and bring one unclaimed job and one destination address the driver actually wants to end near.

Frequently asked questions

What does the designated-driver order pool show?

In the driver app, the order pool shows passenger-placed orders that no driver has accepted yet. The list does not describe a sort order, map pins, or an auto-refresh interval. Open the pool in a demo and write down how new jobs appear. Until then, train it as a list of unclaimed passenger orders.

Can a driver search the pool by pickup location?

The documented search is by destination, not by pickup. Drivers can search an address and query orders whose destination is near that address. The list does not say the search also filters by pickup. Do not brief a pickup-radius tool, and do not sell a guaranteed empty-back-haul matcher. Confirm any extra filters in a demo.

How do unclaimed jobs get to drivers in the first place?

When a passenger places an order, it is pushed to drivers according to the configured dispatch range. The backend can set that system push distance. The list does not name a default distance. Confirm the configured range in a demo. This article does not turn that setting into a full dispatch-range walkthrough.

Does the designated-driver pool auto-cancel unclaimed jobs after 10 minutes, like the taxi pool?

The designated-driver list does not document those timers. The five-minute pool split and the 10-minute unaccepted auto-cancel belong to the taxi product list and its own post. Do not write them as designated-driver facts. On the admin side, staff can view orders with no driver and dispatch a driver as a desk backup path.

Related articles

Talk to our team about your platform

Tell us your market and business model. We will reply with a feature plan, a demo of the apps and a quote.