Ride-Hailing Driver-Placed Orders: Grab Mode and Long-Distance Carpool Only

A driver already standing next to a passenger is not a broken dispatch story. Treating every curb conversation like a random street skim is how you either ban a useful button or let it leak into every vehicle type. On Ptaxi’s ride-hailing platform, driver-placed orders let a driver book quickly on a passenger’s behalf. The documented limit is narrow: the action is only active in Instant Grab mode and long-distance carpool mode, and it applies only to long-distance carpool orders. Finance gets a second switch: commission-free driver-placed orders, which skip platform commission while tax is still calculated.

This piece is about training that box. It is not a rewrite of passenger book for someone else, passenger QR scan, or admin manual dispatch. It does not turn driver-placed booking into a general express or airport product.

Why curb-side booking gets over-sold

Long-distance carpool work often starts with a conversation the platform never saw: a passenger at a station, a driver already heading that corridor, a verbal “can you take me?” If the product cannot digitize that job, cash walks away and the hall never learns the trip happened. If the product lets every driver mint any order type for anyone, you have built a skimming tool and called it convenience.

Typical pains the documented limit is meant to blunt:

1. Drivers hunt a place-order button while they are in Smart Dispatch mode and decide the app is broken.
2. Supervisors hear “drivers can create orders” and assume that includes Standard Express, Premium, or Airport Car.
3. Finance expects a normal commission on a driver-placed carpool job after someone enabled the commission-free switch.
4. Support mixes driver-placed orders with book-for-someone-else and with scanning the driver’s QR code.

Driver-placed orders answer *how a driver turns a long-distance carpool passenger they already have into a platform job*. Mode settings answer *whether that driver is even in Instant Grab, and whether they opted into long-distance carpool*. Commission-free answers *whether the platform takes a cut*. Keep the three cards separate.

What the documented driver-placed path includes

Confirmed driver surfaces describe driver-placed order in plain language: drivers can place an order on a passenger’s behalf and order quickly for themselves. The same line adds the fence: only active in Instant Grab mode and long-distance carpool mode; applies only to long-distance carpool orders.

Say those clauses in launch workshops. Do not invent “any grab-mode vehicle type,” “smart-dispatch fallback,” or “airport car exception.” If a lead wants driver-created express trips, that is a product-policy conversation—not a reason to pretend the list already allows it.

Mode settings sit right next to this button. Drivers choose Smart Dispatch or Instant Grab. In Smart Dispatch they can choose whether to accept airport and train-station orders. In Instant Grab they can choose whether to accept long-distance carpool orders. A driver who never opted into long-distance carpool is not a driver-placed-order story. A driver sitting in Smart Dispatch is not either. Walk both toggles before you demo the create-order action.

Long-distance carpool already has other special rules. Transfer order is documented only for long-distance carpool, and the backend can limit how many transfers a driver may make per day. That is useful context, not a substitute. Transferring an accepted carpool job is not the same as creating one from the curb.

Once the trip runs, confirm-bill still follows the documented payment methods: passenger pay, driver advance payment, offline payment, and driver-collected payment. Describe those for overseas buyers as passenger-pay, driver-advance from in-app balance, offline collection with no recorded transfer, and driver-collected with a collection record. Do not invent card rails. Carpool itself is always prepaid on the passenger side regardless of the backend prepayment toggle—that passenger rule does not rewrite the driver-placed fence.

Admin switches: enable the button, then talk about commission

Admin business modules include an explicit driver-placed order switch: drivers can place orders on a passenger’s behalf. They also include commission-free driver-placed orders: those jobs are not subject to platform commission, with a note that tax is still calculated.

Treat that pair as two decisions:

• Enable driver-placed orders when your corridors actually start with driver-found carpool passengers and you would rather see the trip on the platform than lose it.
• Enable commission-free only after finance agrees that take-rate will drop on those jobs while tax still appears in the calculation.
• Do not enable commission-free “to make the demo friendlier” if your contracts still promise a cut on every completed carpool.

The same business-module list holds related order settings: one-tap order, prepayment for non-carpool and non-charter work, fixed-price surcharge, offline payment, and driver-collected payment. Those switches change how ordinary passenger jobs start or settle. They do not widen driver-placed orders beyond long-distance carpool. There is also a separate commission-free switch for designated-driver orders; do not borrow it in a ride-hailing workshop.

If nobody accepts a normal passenger request, that is manual dispatch—including the documented rule that scheduled long-distance carpool bookings can only go through dispatch. Driver-placed order is not a back door around that desk path.

Do not confuse three “someone else created this job” stories

Buyers collapse three surfaces into one sentence. Split them on the whiteboard:

Passenger books for someone else. The passenger app collects another rider’s name and phone number, from contacts or by typing. The person paying or placing the order is not necessarily the person at the curb.

Passenger scans the driver’s QR code. The driver displays a code; the passenger scans it to place a face-to-face order. That path starts on the passenger device.

Driver places the order. The driver creates the job for a passenger they are already talking to, inside the Instant Grab plus long-distance carpool box.

Admin backend order creation is a fourth path for staff, not a driver habit. Teaching all four as “proxy booking” guarantees the first incident review will argue about a button that was never supposed to fire.

Smart dispatch versus grab modes is the right companion article for the mode toggle. This piece stays on the create-order action that grab-mode carpool drivers actually get.

Ops tradeoffs to say out loud

• Wide “drivers can create any order” story: faster curb capture, no documented basis, and a night of mystery express jobs that look like skimming.
• Button enabled, mode coaching skipped: drivers in Smart Dispatch call support; grab-mode drivers who declined long-distance carpool do the same.
• Commission-free on, finance unbriefed: drivers like the work, the ledger still calculates tax, and someone asks why platform commission is missing.
• Commission-free off, corridor culture expects a handshake deal: drivers keep the passenger off-platform and you never see the trip.
• Driver-placed + grab + long-distance carpool + honest commission talk: the documented box, taught as a box.

Practical notes that match the surfaces:

• Demo mode settings first. Show Instant Grab, then the long-distance carpool opt-in, then the place-order action.
• Put a passenger QR-scan drill on a different slide so nobody thinks scanning the driver’s code is the same button.
• When an auditor asks about take-rate, open the commission-free switch and say the tax sentence out loud.
• Order pool, broadcast, and destination change remain ordinary trip tools. They do not enlarge who may create a driver-placed job.

What this is not

• Not a general street-hail digitizer for every configured vehicle type.
• Not book-for-someone-else, passenger QR scan, or staff-created backend orders.
• Not a claim that Smart Dispatch can host driver-placed orders.
• Not named map vendors, tips, bank cards, or card processors.
• Not WeChat or official-account packaging for overseas App buyers.
• Not SOS marketing. Keep emergency claims on documented passenger alarm surfaces, separate from this booking path.

Launch sequence sales can repeat

1. Set a driver to Instant Grab and enable long-distance carpool acceptance.
2. Place a driver-created long-distance carpool order and walk it as a normal trip through confirm bill.
3. Switch the same driver to Smart Dispatch and show that this is not the documented home of the button.
4. Open admin business modules. Point at driver-placed order, then at commission-free driver-placed orders, and read the tax note.
5. Contrast the flow with a passenger book-for-someone-else booking and a passenger scan of the driver’s QR code.

If a buyer wants “drivers should be able to open any job they find on the street,” ask who explains the first mystery Airport Car that never went through passenger hail or dispatch. The documented answer is that this button was never that product.

Soft next step

If curb conversations keep disappearing off-platform—or appearing as the wrong order type—enable driver-placed orders, train the Instant Grab plus long-distance carpool limit, and decide the commission-free switch with finance in the room. When a lead can demo that box without inventing extra vehicle types, you are ready to run ride-hailing software corridors without training drivers to guess which “create order” myth is real.