Designated Driver Waiting Fees: Pricing the Curb After Arrival

Night designated driver work dies on the sidewalk, not on the highway. The driver is at the pin. The passenger is still closing the tab. If your app only prices distance, every minute of curb delay is either unpaid labor or a fistfight about “extra.” Waiting fees exist so that delay is a configured line, not a verbal tax.

On Ptaxi’s designated driver app, the pricing plan’s price components include base fare, distance fee, time fee, long-distance fee, and waiting fee. Waiting fee is documented as the rule for billing after the driver arrives at the pickup point. Estimates show estimated and preferential options with rule details. This piece stays on waiting — not wallet top-up bonuses, not go-online balance reserve, not appointment early-start (those have their own posts).

The curb is a product surface

Driver trip flow includes a clear waiting for passenger to board stage: the driver has arrived; the passenger is not yet confirmed onboard; the driver swipes when boarding is real. Waiting fee policy should match that stage in training language.

Without a waiting rule, fleets pick a bad default:

• Drivers leave after five unpaid minutes → no-shows spike.
• Drivers wait forever unpaid → supply flees Friday nights.
• Drivers invent “service fees” in chat → brand damage.

A documented waiting component lets you price the delay and show it in rule details before the passenger confirms.

How waiting sits beside the other lines

Keep the components distinct in ops docs:

1. Base fare — starting fee or base fee patterns as configured.
2. Distance fee — per kilometer.
3. Time fee — per minute while the trip is moving under time pricing.
4. Long-distance fee — range-based remote segments.
5. Waiting fee — post-arrival wait at pickup.

Mixing “time” and “waiting” in driver scripts creates refund theater. Say: time is movement; waiting is curb after arrival.

You can also set different unit prices for different time periods, and bind plans to weekdays, weekends, holidays, or custom cycles. Friday 23:00 curb waits are not Tuesday 14:00 curb waits. Price them like different products if your city behaves that way.

Preferential (特惠) pricing remains a separate switch with mileage-stage rules and caps — useful for short hops, dangerous if you hide wait policy inside a “discount” story. Preferential was covered with multi-driver calling elsewhere; here, just do not let a promo erase wait transparency.

Estimates that do not lie

After origin and destination are set, passengers see estimated and preferential choices plus pricing rule details. Waiting is hardest to estimate perfectly because passenger delay is behavioral. Still:

• Show that a waiting rule exists in the detail breakdown.
• Teach drivers not to promise “I’ll wait free” against a configured fee.
• Teach support to read the same detail screen the passenger saw.

If minimum estimated mileage gates apply in your city, say that at booking — wait fees on trips that should never have been placed only multiply anger. Minimum mileage configuration is documented; pair it with wait policy in launch workshops when short fake pins are a local problem.

Driver habits that keep waiting fees collectible

Waiting fees fail when drivers skip arrival confirmation. If the app never records “arrived,” your wait clock has nothing honest to bill.

Handbook lines that match the flow:

• Mark arrival when you are actually at a usable pickup point, not two blocks away “to save time.”
• Use the boarding swipe only when the passenger is in the car.
• At bill confirm, keep highway / bridge / parking add-ons for real road costs — do not smuggle curb wait into “parking” because the wait line was misconfigured.

Bill confirm still supports passenger pay, driver advance pay, and offline collection via driver QR when those business switches are on. Waiting fee honesty matters on all three paths; offline collection without a clear wait line is how QR nights become argument nights.

Tradeoffs to put on the pricing whiteboard

• Zero waiting fee: simple marketing; night drivers vanish from slow venues.
• Aggressive wait fee with no free minutes: passengers cancel at the pin; completion rate drops.
• Short free wait, then clear per-minute wait: usually the workable middle — publish the free window in passenger FAQ.

Also decide whether weekend/holiday cycles carry higher wait rates. Document the choice in the plan cycle, not in a side spreadsheet drivers never see.

Heatmap and online/accepted/pending driver counts help supervisors see whether slow venues need more supply or clearer wait rules. Heatmap does not replace pricing; it tells you where wait fights cluster.

Waiting fees and multi-driver calls

Passengers can request more than one driver on a designated driver order when that capability is enabled. Waiting math gets messier when two drivers arrive and only one passenger walks out. Ops policy should say who accrues wait: each arrived driver under their own arrival mark, or a lead driver only. The software prices waiting from arrival rules you configure; your handbook must say how multi-driver arrivals are treated so support does not invent case law at 01:00.

Merchant-assisted booking adds another stakeholder who may promise “the driver will wait.” Merchant commission does not erase wait fees. Put wait policy in merchant onboarding the same way you put it in passenger FAQ.

Bill confirm add-ons are not waiting fees

At destination, drivers confirm the bill and may fill highway, bridge/road, and parking add-ons. Those are trip road costs. Waiting fees are pickup curb time. If drivers dump wait into parking because wait was never configured, you will “fix” night complaints by breaking parking trust. Configure wait properly; keep add-ons for asphalt and lots.

Payment path after confirm still follows your switches: push bill to passenger, driver advance, or offline QR collection. Waiting line items must survive all three or finance will not reconcile venue nights.

Measuring whether wait pricing worked

After two weekends, look at:

• Cancel rate after driver arrival (passengers who refuse wait fees).
• Driver acceptance on known slow venues.
• Support tickets mentioning “wait” or “extra minutes.”

If cancels spike, your free window is too short or the rate is too loud relative to base fare. If drivers still refuse slow pins, wait revenue is not compensating them — raise wait, shorten free window, or stop promising those venues in sales.

What this is not

• Not a claim of companion or follow-car product modes beyond what your confirmed lists describe for this line.
• Not WeChat-only packaging for overseas pages; describe passenger and driver apps plus admin pricing.
• Not national emergency-number marketing from China-only SOS copy.
• Not tips or card rails the feature lists do not confirm.

Soft next step

If Friday venues burn your designated drivers on the curb, open the pricing plan and configure a real waiting fee with a published free window, bind a weekend cycle if needed, then walk one estimate screen so the wait rule appears in pricing details. Finish with a driver who marks arrival, waits on purpose, and completes bill confirm. When passenger, driver, and finance describe the same curb minutes, you are ready to tune the rest of designated driver pricing — base, distance, and preferential — without using wait as a hidden patch.