Carsharing System

Carsharing Safety Settings: Emergency Contacts and Identity Verification

A carsharing trip puts a renter in someone else’s vehicle, often alone, sometimes in a city the operator does not staff on the street. Buyers will ask how a passenger records a person to call, and how identity is checked before the keys come out. If the brief blends that question with ride qualification and the violation deposit, the demo gets muddy. Ptaxi’s carsharing system documents safety settings in the passenger personal center: emergency contacts and personal identity verification.

This is not a qualification article, and it is not a deposit article. Carsharing driver qualification review and the passenger ride-qualification plus violation prepaid deposit posts already cover those gates. Today’s card is the safety-settings pair, and the need to confirm whether identity here is the same screen as qualification.

Emergency contacts are a setting, not an automatic alert

The passenger can set emergency contacts under safety settings. That is the documented fact.

The buyer will push past it. They will ask whether those contacts get a message when the trip starts, whether they can see the car, and whether the desk is copied. The list does not say any of that. It does not name a maximum number of contacts, a required phone format, or an in-trip button that calls the first contact.

So the honest brief stays narrow. Passengers can add emergency contacts. Anything those contacts receive has to be proven in a demo. Start a test trip, leave the contacts in place, and write down whether they are notified with no further tap from the passenger. If they are not, say so in the launch brief. Do not sell an automatic family alert on the strength of this line alone.

In-trip contacts already have a walkthrough on this line. That post is about contacting people during the trip. This card is the safety-settings list. Keep the two rehearsals separate so a sales deck does not merge them into one “contacts” feature.

Do not fold a public emergency-call path into this section. If the product line has an alarm-management screen for in-trip alerts, that is a different tool and is not the subject here. An overseas brief should not lead with a country-specific emergency number.

Identity verification, and the overlap with ride qualification

Safety settings also include personal identity verification.

Ride qualification is documented separately: a passenger must complete use-of-vehicle qualification with personal information and driver’s license information before renting, then pay a violation prepaid deposit used for later violations or overtime issues. That is a booking gate, and it already has its own posts.

The naming overlap is the risk. “Personal identity verification” in safety settings and “personal information plus driver’s license” in qualification may be one screen in the build, or two. The list does not say they are the same, and it does not say they are different. In a demo, open safety settings and start a qualification on the same test passenger. Write down whether you are sent to one flow or two, and whether finishing qualification marks identity as complete in safety settings.

Do not invent a face scan, a device bind, or a government ID-network check. Those are not in the docs. Copy the fields you see. If an unverified passenger can still search cars and is only blocked at checkout, write that down. If they cannot search at all, write that down too. The list tells you qualification is required to rent. It does not describe the safety-settings identity fields.

That uncertainty is the tradeoff you should put in the sales note. A single flow is easier for the renter and easier to support. Two flows mean a renter can finish qualification and still see an incomplete identity item, or the other way around, and the desk will take the ticket. You will not know which shape you have until the demo is walked once, on one account, start to finish.

Driver qualification on the driver app — personal information and driver’s license, reviewed by the platform — is a third path. Staff already have a review queue for driver applications. Do not mix a driver’s certification into this passenger safety card.

What admin configuration actually names

System configuration includes payment-method switches, privacy settings, share-content settings, download settings, and safety settings.

That is a useful map for a buyer who asks “where do we turn this on.” It is not a license to invent the toggles.

Safety settings in admin are named, not specified. Do not brief a required-identity switch or a required-emergency-contact switch unless the demo shows them.

Privacy settings are also named and not specified. On other product lines, passenger safety settings include private number protection. This carsharing list does not use that wording in the passenger safety settings. Do not import a privacy-number product into this brief. If the admin privacy screen turns out to contain a number-protection switch, copy it from the demo and label it as what you saw, not as a documented passenger-setting on this line.

Share-content settings are a neighbor. This article is not a trip-share walkthrough. The carsharing list does not document a passenger “share trip” function in the same words as the taxi or designated-driver lists. Do not invent one to pair with emergency contacts.

Neighbors to keep off this card

Ride qualification and the violation prepaid deposit are booking gates. Link those posts. Do not retell the deposit refund rules here.

In-trip contacts, complaints and feedback, and push notifications already have walkthroughs. A push is not a safety-settings alert. A complaint is not an emergency contact.

Wallet billing and invoices sit in the same personal center and mention the prepaid deposit as a wallet item. That is a finance card, not this one.

Order details include trip track, complaint records, and push logs. Those are investigation tools after a problem. They are not the safety-settings screen.

What not to promise on carsharing safety settings

Do not say emergency contacts automatically receive a trip start, a delay, or a live location.

Do not describe a privacy-number proxy as a documented passenger setting on this line.

Do not assume safety-settings identity is the same as ride qualification, and do not assume it is different, until a demo shows one flow or two.

Do not add face verification, liveness, or a named ID-network vendor.

Do not retell a country-specific emergency number, an official account, or a domestic chat-app customer-service helper in an overseas brief.

Do not claim a packaged “safety suite” with desk notification, recorded calls, and automatic family alerts. The list names two passenger settings and an admin safety-settings group.

A short ops checklist before you brief the app

Keep this to one page.

  • In the passenger app, open safety settings. Add an emergency contact. Copy the fields and any limit on how many contacts you can store.
  • Start a test trip without tapping any share or call control. Ask whether the emergency contact received anything. Record a yes or no, with the timestamp.
  • Open personal identity verification from safety settings, then start ride qualification on the same account. Note whether the flows are the same screen. Complete one and see what the other then shows.
  • Attempt to search and book with identity or qualification incomplete. Write down the first screen that blocks the renter.
  • In admin system configuration, open safety settings, privacy settings, and share-content settings. Copy the visible switches. Do not add a privacy-number claim unless that screen and a live call prove it.
  • Keep driver qualification, the prepaid deposit, and in-trip contacts off this rehearsal. Point to those posts if the buyer asks.

Close

Carsharing safety settings are a passenger place to add emergency contacts and to handle personal identity verification. Ride qualification and the violation prepaid deposit remain the documented booking gates, and they may or may not share a screen with that identity setting. Admin system configuration includes safety settings, privacy settings, and share-content settings, without a published field list. Automatic contact alerts and a privacy-number product are not documented here.

If you run a carsharing or car-plus-driver service and buyers keep asking who gets called, and how identity is checked, walk this path in a carsharing system demo. Bring a test passenger, an emergency contact who will tell you if anything arrives, and a second pass through qualification on the same account. Then write only what the screens actually did. You can also contact Ptaxi when you want that demo scheduled.

Frequently asked questions

What do carsharing safety settings include?

The passenger personal center documents safety settings for emergency contacts and personal identity verification. The list names those two items. It does not describe automatic trip alerts to those contacts, a privacy-number proxy, or a block on booking until identity is complete. Confirm each behavior in a demo.

Is this the same as ride-qualification certification?

Not necessarily. Ride qualification is a separate booking gate: personal information and driver’s license information must be certified before a rental, and a violation prepaid deposit is collected after that certification. Safety settings also mention personal identity verification. Confirm in a demo whether those are the same screen or two different ones.

Do emergency contacts receive the trip automatically?

The list only says emergency contacts can be set. It does not say they are notified when a trip starts, delayed, or ended, and it does not say they receive a live share. Brief the ability to add contacts. Then test a trip in a demo and write down whether those contacts are contacted without a manual action from the passenger.

Where does admin configure safety on this line?

System configuration includes payment-method switches, privacy settings, share-content settings, download settings, and safety settings. The list names those groups. It does not publish the fields inside safety settings or say that privacy settings are a private-number product. Open the screens in a demo and copy what you see.

Related articles

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.