Taxi Dispatch Software

Book a Taxi for Someone Else: Name, Phone, and Proxy Booking

The person who needs the taxi is not always the person holding the phone. A parent books for a teenager leaving school. An assistant books for a visitor who has just landed. If your taxi app can only book for the logged-in account, those jobs leak into a texted pin and a wrong-number call. Ptaxi’s taxi dispatch software documents booking for someone else: the booker sets the rider’s name and phone number, chosen from the phone’s contacts or typed manually, and then places a normal taxi order.

This is a contact layer on a metered taxi job. It is not a second product, and it is not a fixed-price ride-hailing flow. Pickup, destination, now or schedule, and confirm still follow the path you already use.

What proxy booking actually adds

The useful work is identity at the curb. The driver needs a name and a reachable number for the person standing outside, not only for the account that placed the order. The booker needs a way to request the car without handing over a login.

The documented fields are small on purpose. You set a name, written in the list as a form of address, and a phone number. You can pick those from contacts, or type them. That is the whole data contract for this toggle. It is enough to put the right person in the driver’s call path. It is not a family account, a shared wallet, or a KYC pack for the rider.

Light fields are easy to finish and weak against a mistyped number. If your compliance team wants ID photos for every proxy rider, that is a process you write on top. Do not pretend the feature list already ships it.

The rest of the booking path does not change

Walk the passenger path in the same order the list uses. The booker still sets a pickup, which defaults to the current location and can be changed by search, and a destination the same way.

The booker still chooses now or schedule. Now means use the taxi immediately. A scheduled job uses the documented window: the earliest time is the current time moved forward 30 minutes and rounded in 10-minute units, and the latest is within three days, including today. Booking for someone else does not get a private scheduling window. The earlier note on scheduled order acceptance still applies.

When the details are confirmed, the booker taps the control to call a vehicle. The order is pushed to drivers according to the configured dispatch settings, including the documented diffusion setup. Taxi orders on this path use metered, in-vehicle fare calculation. A proxy field does not rewrite the fare method, and this is not a fixed-price ride-hailing product.

Do not invent a “family booking” radius, or a rule that only nearby drivers may take these jobs. Origin and destination can still classify a job as urban or intercity, with different commission schemes, but that is ordinary confirm-and-dispatch, not a proxy rule.

Cancellation still follows the passenger cancel rules you already configured. If a driver has accepted and the rule conditions are met, canceling can require a fee on the account that placed the order. Tell bookers that canceling “for someone else” is not a free undo.

Contacts versus typing the number

Contacts save typing when the rider is already in the phone book. Manual entry covers a number on a paper note, a hotel desk, or a rider the booker does not want stored as a full contact. Both paths feed the same name and phone fields.

Do not train contacts access as a requirement. The list says you may choose from contacts or type the fields. If a phone declines the contacts permission, manual entry is still a documented path. In field training, show both: one job from a contact, and one job typed by hand.

Who the driver calls, and who still pays

After the driver accepts a taxi job, the in-trip screen shows passenger, order, and amount information. The driver can tap a phone icon to call the passenger.

The reason you collected a rider phone is so the person at the curb can be called, instead of the booker three neighborhoods away. The list does not spell out a two-number call tree, and it does not say the phone icon is guaranteed to prefer the proxy number over the account number. In a demo, enter a rider number that is not the booker’s, accept the job, and confirm which number the call action uses. Do not sell a dual-line feature the list does not describe.

Payment stays on the account that places the order. Documented taxi payment includes configured in-app payment methods and balance. Cash settlement is also a documented taxi option: the passenger can pay offline, and the platform commission is deducted from the driver’s wallet. Book-for-someone-else adds name and phone. It does not document a payer switch to the rider, and it does not say the rider inherits the booker’s coupons, wallet balance, or invoice requests. If a buyer needs the rider to pay later, say that this is not written as a product switch, and confirm the payment screen in a demo.

Privacy-number protection exists on the account’s safety settings. Do not claim it automatically wraps the rider’s phone. Trip sharing is a separate passenger action; the list does not say a proxy order automatically shares the trip back to the booker. If the booker needs to follow the car, train a manual share after the driver accepts.

Neighboring taxi paths to keep off this card

One-tap booking is a different passenger path. It confirms a pickup and calls a car quickly; the destination is entered later, after the driver confirms the passenger is on board. Do not train one-tap as the way you attach a third-party name and phone.

This article also stays off phone-dispatch and message-based booking channels. Those are separate intake paths. Booking for someone else is a field pair on the ordinary app booking path. A similar name-and-phone pattern can exist on other mobility lines, but this taxi job still settles on the meter.

What not to promise on a proxy taxi job

Do not promise a separate login for the rider, a family account, or an approved-contact list the booker must pick from. Do not say contacts access is required; manual entry is allowed. Do not promise automatic coupon inheritance, a documented payer switch to the rider, or a rule that the rider’s wallet is charged. Do not brief the fare as a fixed price; taxi orders on this path use metered, in-vehicle fare calculation. Do not invent a verification text the rider must approve before the job can be placed. Do not claim automatic trip share to the booker, and do not describe privacy-number protection as a guaranteed wrapper on the rider’s phone unless you have confirmed that in the build. Do not fold phone-dispatch intake into this toggle.

A short ops checklist before you brief the app

Keep this to one page.

  • Choose book for someone else. Enter a rider name and phone from contacts, then place a second job by typing the fields by hand.
  • Confirm that pickup, destination, and now-versus-schedule still apply, including the documented schedule window.
  • Place the job with the same confirm-and-dispatch path you use for ordinary taxi work. Say out loud that the fare method is metered.
  • After accept, open the driver trip screen and use the phone icon. Confirm which number is called when the rider phone is not the booker’s account phone.
  • Open payment on the account that placed the order. Show configured in-app methods and balance, and show cash settlement as a taxi option if you use it. Do not describe a payer switch to the rider.
  • Write a one-line support note: canceling this job can still follow the same passenger cancel rules, including a possible fee after accept.
  • Keep one-tap booking and phone-dispatch intake off this training card.

If a script starts promising a family account or a rider-pays switch, cut it back to the two fields you can actually fill.

Close

A taxi booked for someone else is a small change with a practical purpose. The booker still sets pickup and destination, chooses now or schedule, and confirms a metered taxi job. The extra work is a name and a phone, from contacts or typed in, so the driver can reach the actual rider.

That is enough to stop a wrong-number call at the curb, if you train the fields as they are. It is not enough to sell a second login, a family plan, or a fare method this product does not use here. Look at booking for someone else on the taxi dispatch software product page. If you want a walkthrough, ask for a demo and bring one job where the rider’s number is not the booker’s, then watch the phone call and the payment screen on the account that placed the order.

Frequently asked questions

What do you enter to book a taxi for someone else?

The booker sets the rider’s name and phone number. Those fields can be chosen from the phone’s contacts or typed manually. Pickup, destination, now or schedule, and confirm still follow the normal taxi booking path. The list does not add a second login, a family account, or a requirement that contacts access is turned on.

Does the rider get a separate login, or pay from their own wallet?

No separate rider login is documented. Book-for-someone-else adds name and phone to the order on the account that places the job. Payment stays on that account: configured in-app payment methods and balance, with cash settlement as a documented taxi option. The list does not describe a payer switch to the rider, and it does not say the rider inherits the booker’s coupons.

Can you schedule a taxi that is booked for someone else?

Yes. Now and schedule sit on the same taxi booking path as the rider fields. A scheduled job uses the documented window: the earliest time is the current time moved forward 30 minutes and rounded in 10-minute units, and you may book up to three days including today. Proxy fields do not replace those timing rules.

How does the driver reach the person who will actually ride?

The rider’s phone is collected so the person at the curb can be reached. After the driver accepts a taxi job, the trip screen lets the driver tap a phone icon to call the passenger. In a demo, confirm that this call uses the rider number you entered, not only the booker’s account phone. Do not assume contacts access is required; manual entry is allowed.

Related articles

Taxi Real-Time Location and Trip Track Playback for the Dispatch Desk

A dispatch desk that cannot tell which cars are actually out, or reconstruct where a finished trip went, ends up arguing from memory. Taxi dispatch software gives the desk a company-filtered location view of online, on-duty drivers and vehicles, plus trip track playback with play, pause, stop, and resume. Those are admin tools. They are not an automatic ETA service, a fuel-saving engine, or the same thing as a passenger sharing the trip.

· 7 min read

Taxi Trip Sharing, Privacy Numbers, and Emergency Contacts

A family member who only has a driver’s personal number is not a safety process. Taxi dispatch software lets the passenger share the trip, store emergency contacts, complete real-name verification, and protect numbers. Those are four separate tools, and none of them should be sold as an automatic alert chain.

· 8 min read

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.