Designated Driver Trip Sharing, Privacy Numbers, and Emergency Contacts
A designated-driver trip often starts at a restaurant or a late event. The passenger wants someone at home to know the car is on the way, and does not want a personal number sitting in the driver’s call log. If the brief promises a live map link and a masked callback without checking the product, the launch demo falls short. Ptaxi’s designated driver app documents trip sharing — share the order or trip — and safety settings for emergency contacts, real-name verification, and private number protection.
This is not a complaints article, and it is not a booking-for-someone-else walkthrough. Designated-driver complaints and feedback already covered service complaints. Today’s card is how a passenger shares a trip and what the safety settings actually name.
Trip sharing is documented. The share card is not.
The passenger action is short: share the order or trip. That is the whole function line.
It is still worth putting on a sales brief, because the buyer will ask who receives the share and what they see. The list does not name a channel. It does not say the share is a link, a text message, or an in-app card. It does not list pickup, destination, plate, driver name, or a live track as fields on that share. It does not say the share expires when the trip ends, or that it stays open.
So the honest brief is narrow. The passenger can share the trip. Everything about the card itself is a demo item. In a demo, start a test job, tap share, and write down the channel picker (if any), the fields shown, and whether a recipient who is not logged in can open it. If the demo has no live map on the share, do not promise one in a proposal.
Admin share settings sit in system configuration, next to payment-method controls, customer-service link settings, safety settings, withdrawal settings, invoicing, and other switches. The list names share settings. It does not publish the fields inside that screen. Open it and copy what is there. Do not invent a branded domain, a default share sentence, or a toggle that includes the driver’s phone.
That thin documentation is itself a tradeoff. You can still sell the button. You cannot sell a packaged family live-track product on the strength of this line alone. Buyers who need a guaranteed recipient experience should see the share in a demo, on a device that is not already logged in, before the contract annex is written.
Do not turn this section into a marketing-link tool. Refer-and-earn download links are a different share, already out of scope here.
Private number protection, emergency contacts, and real-name verification
Safety settings on the passenger personal center list three items: add emergency contacts, real-name verification, and private number protection.
Private number protection is the item fleets ask about first. Riders do not want the driver keeping a personal number after a night drop-off. The list names the protection. It does not describe a mid-trip proxy number, a one-time mask, a recording of the proxied call, or a rule that protection starts only after accept. In a demo, enable it on a test passenger, have the driver place a call, and write down the number each side sees. If the demo still shows the raw number, do not brief masking as a live behavior for that tenant.
Emergency contacts can be added. The list does not say those contacts automatically receive a trip share, or that they are called if the passenger is late. That auto-notify story is easy to invent and is not in the document. Brief the ability to add contacts. Confirm in a demo whether a contact can be invited to a share, and whether the app does anything with the list during the trip. If it does nothing unless the passenger acts, say that.
Real-name verification is the third item. The list names it. It does not list the documents, a liveness check, or a block on booking until verification is done. Face verification is not in the docs. Do not add it. Open the flow in a demo and copy the fields. If unverified passengers can still complete a booking, write that down so a compliance team is not surprised.
These three settings live together. That is useful. It is also easy to over-pack them into a “safety suite” with automatic alerts the list does not describe. Keep the names, then prove each behavior in a demo.
What admin can actually configure
System configuration includes safety settings and share settings. The list groups them with payment-method controls, customer-service links, withdrawal settings, invoicing, other settings, and the download-address setting.
That is enough to tell a buyer there is an admin place to configure sharing and safety. It is not enough to invent the toggles. Do not brief a required-real-name switch, a forced privacy-number switch, or a share-template editor unless the demo screen shows them.
Role and company permissions on this line already have their own post. Use that walkthrough if you need to know who can open system configuration. This card does not retell the permission tree.
Neighbors to keep off this card
Book for someone else already has a walkthrough. Booking for another person uses a name and phone number. That is not trip sharing, and it is not privacy-number protection, even though a phone number is involved.
Complaints and feedback, order disputes, and scan-to-book at venues are other passenger actions. Mention them only so a sales deck does not dump them into “safety.”
An in-trip emergency-call control exists on this line. It is a different feature. Do not retell it here, and do not describe trip sharing as a substitute for it. Do not name a local emergency number in an overseas brief.
The taxi line has a related trip-sharing and privacy-number article. Do not import wording from that list as if it were this one. Brief only what the designated-driver document names, then confirm the screens in a designated-driver demo.
What not to promise on designated-driver trip sharing
Do not name WhatsApp, SMS, or a specific messenger as the share channel unless the demo shows it.
Do not claim the share includes a live map, an ETA, a plate, or a driver photo. The list only says the trip can be shared.
Do not say emergency contacts automatically receive the share or a late-trip alert.
Do not describe how the privacy number is implemented — proxy, mask, or time-boxed callback — until you have seen a call in a demo.
Do not add face verification, device binding, or a “must verify before booking” gate the list does not name.
Do not treat the privacy policy page, or the login agreement, as this safety-settings card. Those are document links, not the three settings above.
A short ops checklist before you brief the app
Keep this to one page.
- In the passenger app, start a designated-driver trip and use trip sharing. Capture the channel, the fields, and whether an unauthenticated recipient can open the share. Note when the share stops working.
- Open safety settings. Add an emergency contact. Write down what the app asks for, and whether that contact receives anything during the test trip without a manual share.
- Turn on private number protection. Place a call from the driver app to the passenger, and the other way if the app allows it. Record the number each side sees, and whether it still works after the trip ends.
- Walk real-name verification on a fresh test passenger. Copy the fields, and test whether an unverified account can still place an order.
- In admin system configuration, open share settings and safety settings. Copy the visible toggles. Do not add fields you did not see.
- Keep emergency-call behavior off this brief. If a buyer asks, schedule a separate demo of that control instead of folding it into trip sharing.
Close
Designated-driver trip sharing is a passenger action to share the order or trip. Safety settings add emergency contacts, real-name verification, and private number protection. Admin system configuration includes share settings and safety settings. The list does not publish the share card, the privacy-number mechanism, or any automatic notify rule for those contacts.
If you run a designated-driver company and riders keep asking to tell someone they are on the way, without handing over a raw phone number, walk this path in a designated driver app demo. Bring a test passenger, a recipient who is not in the app, and a driver call with privacy protection on. Then decide what you can honestly put in the launch brief. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
Can a passenger share a designated-driver trip?
Yes. The passenger app includes trip sharing, described as sharing the order or trip. The list does not name the share channel, the fields on the share card, or whether the link stays live after the trip ends. Confirm those details in a demo before you brief a specific messenger or a live map for a family member.
What does private number protection do?
Safety settings include private number protection, alongside emergency contacts and real-name verification. The list names the switch. It does not describe a proxy number, a time window, or whether the protection applies only after a driver accepts. Open the setting in a demo and write down what the passenger and the driver actually see when they call.
Is trip sharing the same as an emergency SOS button?
No. Trip sharing and safety settings are the subject of this article. An in-trip emergency-call control is a different feature and is not retold here. Do not brief trip sharing as an automatic alert to police or to the operations desk.
Where does admin configure sharing and safety?
System configuration includes share settings and safety settings, together with payment-method controls, customer-service link settings, invoicing, and other switches. The list names those setting groups. It does not publish the fields inside them. Open both screens in a demo and copy what you actually see.