Designated Driver Appointments: Nearby-Time Locks, Early Start, Reminders

Scheduled designated driving fails before anyone opens the door. A passenger stacks two appointments twenty minutes apart. A driver shows up an hour early and the passenger is still at dinner. Nobody gets a reminder, both sides blame the app, and support spends midnight reconstructing chat screenshots.

Ptaxi’s designated driver app line documents three appointment controls that belong together in launch notes: order placement settings that stop a user with an existing scheduled order from placing another for a nearby time; early-start settings for how early a driver may begin a scheduled job; and scheduled-order reminders by SMS and voice before start. Minimum mileage gates and post-accept reschedule rules are covered elsewhere — see min mileage and reschedule. This piece is the calendar hygiene layer.

Why “just book later” is not a product

Night economies run on appointments: dinners, weddings, corporate events, last trains. If your app allows overlapping scheduled jobs from the same user, you create:

• Two drivers positioning for one passenger.
• Cancel fees fights that are really double-book bugs.
• Heatmaps that look like demand spikes but are duplicate intent.

The documented placement rule is blunt: when a user already has a scheduled order, they cannot place another order for a nearby time. “Nearby” is your configured policy sense — the important part is that the platform can refuse the second booking instead of hoping the passenger notices.

Ops choices:

• Window too tight: legitimate back-to-back legs (venue then hotel) get blocked; users invent workarounds.
• Window too loose: double-books still land.
• No passenger-facing error copy: users think the app is broken rather than protecting the night.

Write the error in human language: “You already have a ride near this time. Change or cancel that one first.”

Early start: how early is early?

Drivers hate sitting on a pin with no permission to begin. Passengers hate a knock while dessert is still on the table. Documented admin control: early-start settings for scheduled orders — how early a driver can begin servicing the appointment.

That setting is commercial and cultural:

• Dense downtown may want a short early window.
• Suburban dinner jobs may need more positioning slack.
• Franchise partners will argue for different windows; company-level discipline beats one global guess if your ops model supports it.

Train drivers that early-start is not “show up whenever.” It is a bounded permission. Train passengers that a driver arriving inside the window is not harassment; it is configured service. If you never publish the window, both sides invent folklore.

Pair early-start with the rest of the trip clock: accept, head to pickup, wait rules, boarding confirm. Early-start without wait-fee literacy just moves the fight from “too early” to “why am I paying for waiting.”

SMS and voice reminders before start

Silent calendars are how no-shows are born. Documented scheduled-order reminder settings send SMS and voice reminders before the appointment begins. Use both channels when your market allows; voice cuts through noisy venues where SMS is ignored.

Reminder design that survives contact with reality:

1. Remind early enough for a passenger to cancel cleanly if plans died.
2. Remind again closer to start if your ops playbook wants a second nudge — only if your configuration actually supports the cadence you promise in training.
3. Keep the message factual: time, pickup area, what to do if they need to change time (and point them at the real reschedule window: after accept, before boarding confirm).
4. Do not stuff marketing into the reminder. Night-of noise kills trust.

Drivers benefit too. A voice/SMS nudge before a scheduled job reduces “I forgot I accepted that” cancels that burn service scores.

How these three settings work as one playbook

Configure them as a set, not as three orphan toggles:

1. Placement lock — stop duplicate nearby appointments at the source.
2. Early-start window — define legal earliness for drivers.
3. SMS + voice reminders — wake both sides before the clock.

Then connect to related tools without conflating them:

• Minimum mileage still gates tiny hops at place time.
• Post-accept reschedule still allows time changes before boarding; cancels after that change go to the appointment-cancel responsibility list.
• Cancel rules and service-score penalties still discipline bad cancels; reminders reduce how often you need the stick.

A demo script that works:

1. Place a scheduled job.
2. Try a second nearby-time job with the same user — show the block.
3. Show the early-start setting value and what the driver app allows inside it.
4. Trigger or describe the SMS/voice reminder path before start.
5. Only then show reschedule-before-boarding if the buyer asks about mid-stream changes.

Failure modes to watch after go-live

• Placement lock on, reminders off → fewer doubles, same no-shows.
• Reminders on, placement lock off → polite no-shows on two cars.
• Early-start generous, wait fees harsh → passengers feel ambushed then billed.
• Early-start zero, traffic heavy → drivers cancel rather than risk lateness.
• Support scripts that say “just book another” → bypass the placement lock socially.

Instrument cancels tagged as “forgot” and “duplicate” for two weeks. If both stay high, your trio is mis-tuned or untrained.

What this is not

• Not merchant-assisted booking or multi-driver-in-one-call (separate features, separate articles).
• Not preferential stage pricing.
• Not a promise of every SMS gateway brand worldwide — the capability is reminder by SMS and voice as documented.
• Not WeChat official-account booking flows for overseas positioning.

Soft next step

If appointment chaos is your night-desk ticket pile, set the nearby-time lock, pick an early-start window your drivers can live with, and turn on SMS plus voice reminders before you rewrite cancel fees again. When that trio matches how your supervisors already run the phone desk, continue on the designated driver app page or request a scheduled-order settings walkthrough with ops and a driver lead together.