Carsharing Push Notifications: Admin Records, Roster Sends, and Order Push Logs
A car-plus-driver hire has more than one person who may need a notice: the passenger who booked, the driver who collects the car, and staff who have to prove a message went out. If the only record is someone’s memory of a text, you will not be able to say later what was sent, or on which order. Ptaxi’s carsharing system documents push notifications as an admin send to passengers or drivers, a content record of those sends, batch push from each roster, and a push log on the order details screen.
This is not an ads article, not a coupons article, and not an in-trip contacts article. Those tools already have their own posts. Today’s card is the push itself, the record, and the log on the order.
Why a car-plus-driver hire needs a send record
Carsharing on this line is not keyless self-drive. A verified driver collects a car, serves the passenger, and returns the vehicle. Notices can matter at more than one step: a reminder to a passenger, a notice to drivers, a follow-up after a failed pickup. Without a content record, support has to guess.
The documented admin screen is push messages, under operations. Staff can view the push content record and can send push notifications to drivers and to passengers. That pairing is the hook: a send, plus a record of what was sent.
Do not treat this as an in-trip phone call. In-trip contacts — owner, driver, passenger, customer service — already have a walkthrough. A call is not a push log. A push is an admin notification with a record you can reopen.
The list does not name the push vendor, a delivery receipt, a click-through report, or a time-zone scheduler. It does not document templates with merge fields, or a preview on a specific phone model. Open the compose screen in a demo and copy the fields you actually see. Train those fields. Do not brief an engagement dashboard as a product fact.
The operations screen, and the log on the order
Use the push-messages screen when you are sending or when you are asking “what did we send?” The content record is the audit trail for the notification itself.
Use the order details screen when you are looking at one hire. Order details include a push log, together with basic order information, the order log, fee details, the trip track, and complaint records. Orders belong to the company that owns the vehicle. The push log is one field among those, not a second broadcast tool.
That split is worth saying out loud. A platform-wide send is not always about one order. An order-level question — “did this job get a notice?” — belongs on the push log of that order. The list does not say every send appears in both places. In a demo, send a notice tied to a test hire if the compose form lets you, then open the order’s push log and the content record and write down what each one shows. If a general roster send does not appear on an order, do not invent a link.
The tradeoff is coverage versus noise. Logging every send against every related order would make the order screen harder to read. Logging nothing on the order leaves support blind when the question is about one hire. The list gives you both a content record and an order push log. It does not define the join. Confirm it in the demo before you write a process.
Batch push from the passenger list and the driver list
The rosters have their own send actions.
On the passenger list, staff can look up passengers, open details, suspend an account, view related orders, and batch-issue coupons and push messages. Coupon issuance already has its own post. On this card, the fact is that staff can batch-push passengers from the roster, not only from the operations screen.
On the driver list, staff can look up drivers, open details and orders, apply a short- or long-term ban for a violating driver, and batch-push messages.
The list says batch push. It does not describe the picker: all passengers, a filtered city, a saved segment, or a pasted list. It does not say a batch of one is the official one-person path. In a demo, open both rosters, start a batch push, and copy the recipient controls. If you can send to one test passenger and one test driver, record how you selected them. Do not brief a tag-based audience or a CSV upload unless that form shows it.
The tradeoff is reach versus precision. A batch to the whole passenger roster is fast and easy to overuse. A smaller batch takes more care and is easier to defend when someone asks why they were notified. The list does not document frequency caps, quiet hours, or an opt-out switch. If the demo or your market’s rules require those, treat them as an operations policy, not as a documented product toggle, unless the settings screen actually has them.
System configuration on this line includes payment-method switches, privacy settings, share-content settings, download settings, and security settings. It does not, in the list, name a push-provider toggle. Do not invent one.
What a push is not
Keep neighboring tools off this card after one pointer each.
Passenger coupons, and admin coupon create/edit/delete, already have a walkthrough. A batch coupon grant on the passenger list is not a push.
Referral and sign-up rewards, and the admin stats for those campaigns, already have their own posts. A push is not a reward grant.
In-trip contacts and complaints are about a hire in progress, or a report and reply. A push log on the order is only the notification history for that job. Do not file a complaint by sending a push, and do not treat a contact call as a recorded notification.
The list does not document in-app splash or popup ads as a passenger-app module on this card. If you later brief ads, use the ads-and-copy screen, not the push-messages screen.
What not to promise on carsharing push notifications
Do not invent delivery receipts, click reports, scheduled sends, or template merge fields. Confirm the compose fields in a demo.
Do not claim a passenger-to-driver chat, a driver broadcast to all riders, or an automatic push when an order changes status. The documented senders are admin staff, to passengers or drivers.
Do not name a push vendor. The list does not.
Do not import another product line’s “Aliyun push” wording, or a China-channel customer-service label, into this brief. On this line, the fact is that staff can send push notifications and view the content record.
Do not say a batch push from the roster always writes a line on every related order. Confirm what the order push log actually shows.
A short ops checklist before you brief the apps
Keep this to one page.
- In admin, open the push-messages screen. Send one notification to a test passenger and one to a test driver. Open the content record and copy the columns you see.
- Open a test order’s details. Find the push log next to the order log, fee details, trip track, and complaint records. Note whether your test sends appear there, and under what label.
- From the passenger list, start a batch push. Copy the recipient picker. Do not run batch coupon issuance on this card.
- From the driver list, start a batch push. Copy the recipient picker. Leave short- and long-term bans for a different rehearsal.
- Open a passenger device and a driver device, if the demo includes both apps, and write down whether the notification arrived and how it is displayed. The list does not describe the in-app presentation. Record demo behavior as demo behavior.
- Do not rehearse in-trip contacts, coupons, or campaign rewards as part of this card. Point at those posts and return to the send record.
Close
Carsharing push notifications are an admin tool for talking to passengers or drivers, with a content record you can reopen, batch sends from both rosters, and a push log on the order. They are not a chat, not a coupon, and not an in-trip phone call. The useful work is deciding which questions belong on the operations send record and which belong on a single hire’s push log, and confirming that split in a demo.
If you run a car-plus-driver carsharing platform and cannot prove a notice went out, walk this path in a carsharing system demo. Send one roster batch, send one tighter test, and open both the content record and the order push log. Then decide who is allowed to send before launch. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
Who can send a carsharing push notification, and to whom?
On the admin push-messages screen, staff can send push notifications to drivers and to passengers, and can view the record of what was sent. The passenger list also supports batch push messages, and the driver list supports batch push messages. The list does not document a passenger-to-driver chat, or a driver-originated broadcast to all riders.
Where can staff see whether a push was sent on a job?
Order details include a push log, alongside basic order information, the order log, fee details, the trip track, and complaint records. Use that log when you are looking at one hire. The push-messages screen is the place to view the content record of sends, not the same thing as the order log.
Can staff push to one person from the roster?
The passenger list supports batch push messages, along with neighboring actions such as account suspension, related orders, and batch coupon issuance. The driver list supports batch push messages, along with short- or long-term bans for a violating driver. Confirm in a demo whether a batch of one is the one-person path, and write down the recipient picker you actually see. The list does not name a one-to-one chat.
Is a push the same as an in-app ad, a coupon, or an in-trip contact?
No. Ads, coupons, and in-trip contacts already have their own cards. A push is an admin notification to passengers or drivers, with a send record and an order-level push log. Do not use the push screen as a coupon grant, and do not treat an in-trip phone contact as a recorded push.