Taxi Trip Sharing, Privacy Numbers, and Emergency Contacts
A taxi booking often ends with a second phone call that has nothing to do with the fare: “Send me the driver’s number, I want to know where the car is.” If the only answer is a personal mobile number, you have handed a stranger a contact that will outlive the trip. Ptaxi’s taxi dispatch software documents four passenger tools that belong in that moment: trip sharing, emergency contacts, real-name verification, and privacy number protection. Admin share configuration and security settings sit in system configuration.
This is not a dispatch algorithm, and it is not a meter change. Taxi order disputes still handle fare, route, and amount arguments. The useful work here is teaching riders and the desk which safety button does what, and refusing to sell those buttons as one automatic chain.
Why a personal number is a poor safety process
Most “I just need to track the cab” requests are reasonable. A parent wants to know the car left the station. A colleague wants an arrival time. An operations lead wants a record if a late-night job goes quiet.
What is not reasonable is treating the driver’s personal number as the product. That number gets copied into family chats and reused after the trip. Drivers start declining night work. Passengers who do not want their own number passed around stop booking for someone else.
A written path is calmer. The passenger shares the trip with the person who should follow it. Emergency contacts are stored before the night out. Privacy number protection keeps a personal line out of someone else’s phone. Real-name verification sits in the same settings group when you want a clearer identity record. Name the tools correctly in training; you do not need a new call center shift to do it.
Trip sharing is a passenger action, not an auto-alert
Say the feature exactly as the list allows. On a taxi order, the passenger can share the order or trip details. That is a deliberate share. The rider chooses to send the trip to someone.
Do not dress it up as a live operations feed. The list does not say the recipient gets a continuously updating map, an ETA that refreshes on a timer, or a push when the driver confirms boarding. It does not say the share expires at drop-off, and it does not say the desk can retract a link. If those rules matter to you, write them into policy and confirm them in a staging build. In a demo, show the share action on a real taxi order and stop at what the screen actually sends.
Keep share separate from other passenger buttons. One-tap booking is a faster way to start a job. Complaining about the driver is a service report. An order dispute is about money or route. Sharing the trip is how a third person is invited to see that the job exists. If you train all of those as “safety,” supervisors will look for a share record when they should be opening a dispute.
Dial-a-ride simple-flow orders are a caution. Passenger trip history notes that those jobs have no detail data. Do not promise a rich share payload on an order type that may not carry a full detail record. Use a metered taxi order in the walkthrough.
Emergency contacts are stored, not automatically messaged
Safety settings let the passenger add emergency contacts. That is a contact book for a bad moment, not a proof that the system already called someone.
The list does not say a booking, a share, a late arrival, or a route change notifies those contacts. It does not say how many contacts are allowed, whether they must be verified, or whether the driver can see the list. Do not invent an auto-SMS, an auto-call, or a rule that the desk is paged when a contact is missing.
What you can do in ops is simpler. Ask riders who book late airport or night jobs to add a contact before they go out. Teach the call center that “Do you have an emergency contact on the account?” is a setup question, not a promise that the platform already reached that person. If a family member needs to follow the car, the passenger still shares the trip.
Real-name verification and privacy numbers are adjacent, not the same switch
The same safety-settings group includes real-name verification and privacy number protection.
Real-name verification is an identity step. The list does not make it a prerequisite for trip sharing, cash settlement, or invoicing. If your market or insurance partner requires it before certain trips, that is a launch policy you enforce in process. Do not tell a buyer the app will block a share until verification is done unless you have confirmed that gate in your own build.
Privacy number protection is the answer to “I do not want my personal number left in the other party’s phone.” The list names the protection. It does not name a telecom vendor, a number format, a recording rule, or a setting that masks every call by default. In sales conversations, show the setting and explain the problem it is meant to solve. Then be honest about what you will still handle out of band: a lost-and-found call after the trip, a police request, or a staff callback that your policy routes through the desk.
Do not confuse privacy numbers with account login. The passenger still has an account. The driver still has a profile. Protection is about how those parties reach each other during the job, not about hiding the user from admin.
What the admin desk actually configures
System configuration includes share configuration and security settings, in the same area as payment method controls, withdrawal settings, invoicing settings, and other switches. That is the right place to look when a share link looks wrong or a safety setting is missing on a build.
The list does not publish the field-by-field contents of those two groups. It does not promise a branded public tracking page, a custom SMS template, or a country-by-country privacy-number provider. Walk the switches in staging, write down what your operators can change, and keep that sheet next to the launch checklist.
Passenger records still matter for the desk, but account tools — top-up, suspension, coupons, pushes — are not a substitute for trip sharing. If someone calls and says “I cannot see my husband’s taxi,” the first question is whether the rider shared the trip.
Order details for a metered taxi job can include trip track and complaint information. Those are desk tools, not a passenger-facing share. Do not make “admin can just look it up and read it out” your default process. That creates a privacy habit you will regret, and it trains riders not to use the share button.
What not to promise in a safety pitch
Stay inside the list.
Do not sell trip sharing, emergency contacts, and privacy numbers as one automated workflow. They are neighboring tools. The passenger has to use them.
Do not claim a live third-party map, a geofence alert to a contact, or a deadline after which a share expires. The list does not say those things.
Do not claim that real-name verification unlocks sharing, or that a missing emergency contact blocks dispatch. The list does not say that.
Do not import a national emergency-hotline story into this page, and do not package the passenger app around a local messaging channel. Buyers should see share, contacts, identity, and number protection — the tools the list actually names for this job.
Do not invent a recording that starts when a share is opened. Trip audio, where it exists on an order record, is a separate admin surface. It is not documented as a share feature.
A short ops checklist before you brief drivers
Keep a one-page script for the control room and for driver onboarding.
- When a family member asks where the car is, the first instruction is: ask the rider to share the trip.
- Emergency contacts are added in safety settings before the night starts, not during a panic call.
- Privacy number protection is explained as a setting, not as a guarantee that no personal number will ever appear in a later lost-and-found case.
- Real-name verification is requested when your policy needs it, and is not described as a hidden lock on sharing unless you have proven that lock.
- Metered taxi orders are used in demos. Simple-flow dial-a-ride jobs are called out as a thinner record.
- Admin share and security settings are reviewed in staging, and the actual fields are written down.
If that script runs longer than a page, you are adding features the list does not give you. Cut it back.
Close
Taxi safety questions usually start as a phone number request. If you answer with the driver’s personal line, you will spend the next year cleaning up leaked contacts. If you answer with four named tools — trip share, emergency contacts, real-name verification, and privacy number protection — riders have a process, and the desk has a way to talk about it without inventing an automatic alert chain.
Look at how those passenger settings sit in Ptaxi’s taxi dispatch software. If you want a walkthrough on a staging site, ask for a demo and bring one real late-night booking scenario with you. The useful test is not a slogan. It is whether a rider can share the trip, and whether your staff can explain the other three settings without mixing them up.
Frequently asked questions
Does taxi trip sharing automatically notify the passenger’s emergency contacts?
No. Trip sharing lets the passenger share the order or trip details. Emergency contacts are added under safety settings. The feature list does not say that a share, a booking, or an in-trip event automatically messages those contacts. Train riders to share the trip with the person who should follow it, and keep contact records as a separate setup step.
What does privacy number protection actually do?
The passenger safety settings include privacy number protection. The list names the feature; it does not publish the relay vendor, the masking format, or a rule that every call in the trip is masked by default. In a demo, show the toggle or setting that exists, then write your own ops policy for when staff still need a direct number.
Is real-name verification required before a taxi rider can share a trip?
The list places real-name verification in the same safety-settings group as emergency contacts and privacy number protection. It does not say verification is a gate for trip sharing, booking, or payment. Do not invent that dependency in a sales script. If your launch policy requires it, say it is your policy, not a built-in lock.
Where does the admin desk configure sharing and safety?
System configuration includes share configuration and security settings, alongside payment, withdrawal, invoicing, and other switches. The list does not itemize every field inside those two setting groups. Plan a configuration walkthrough in staging, and do not promise a public share page design or a specific SMS template the list never names.