Designated Driver Apps

Choosing Designated Driver Software: Booking, Go-Online Gates, and Merchants

People who want to start a designated driver company, or replace a messy stack, often begin with a search for who has good reviews. A reputation list cannot complete a trip. The useful test is narrower: can a rider place a job, can a driver be stopped from going online when a gate is not met, and can a venue request a driver with a commission you can see in the admin? If those three paths fail, the brand name will not help you at 1 a.m.

Ptaxi's designated driver app documentation describes a rider client, a driver app, and a PC admin. Riders can place a job, book more than one driver at a time, and book a driver for someone else. Merchant assist is documented, with merchant management and commission. Drivers must pass verification before they can serve jobs. Go-online can be blocked when the wallet is below a reserved amount, and it can also require a collection QR code to be uploaded first. Payment should be briefed as configured in-app payment methods and account balance, with driver-advance and an offline collection QR as additional bill-confirm options. Do not name a card rail or a payment provider.

This is a selection article, not a replay of earlier how-to posts. Booking a driver for someone else, merchant-assisted booking, and the collection QR go-online gate already explain those flows. What you need in a buying meeting is a script that forces each path to appear once.

Can a rider actually complete a booking?

Early demand often comes from a phone in someone's hand at a venue door. In the documented rider client, the person can confirm a price that shows an estimate, a promotional price when one applies, and a fare breakdown, then place the job. Booking for someone else, and requesting more than one driver on the same request, are variants of that booking, not decorations. In a demo, run a job for the logged-in rider, one job for another person, and one multi-driver request. Do not let a single self-booking stand in for the rest.

If your service should refuse very short trips, ask whether a minimum estimated mileage limit can be turned on, and try it. Hearing a pricing lecture is not the same as seeing a short trip blocked or flagged.

Bill confirm and invoicing have their own articles. For selection, you only need to see one job reach a completed payment: in-app or balance, and, if you will use it, driver-advance or the driver's collection QR for offline settlement. If that last step is delayed until after go-live, you do not yet know whether money can be reconciled.

It also helps to say what this meeting is not. It is not a safety-feature training, even though emergency calling and trip sharing are documented on the rider side and belong in a later operations review. It is not a review of splash screens or in-app ads. Those surfaces exist, and they already have their own post. A company that cannot complete a booking will not be saved by a polished startup screen.

A standalone browser booking page and a driver mini-program are not described as confirmed clients. If your drivers or venues expect those clients, write them as open questions. Accept the documented driver app as the driver surface unless a build is shown.

Test go-online gates and merchant assist separately

Driver verification is a hard gate: the driver cannot serve jobs until the review passes. Which documents are required can be controlled in the admin. Go-online can add two more gates. If the wallet is below a reserved amount, the driver cannot go online. The admin can also require a collection QR to be uploaded first. Those gates do not guarantee driver earnings or that cash will actually arrive. They only block a driver who is not ready under the rules you set.

In the demo, use a test driver who fails one gate: too little reserved balance, or a missing QR. Confirm the app really blocks go-online. Then use a verified driver who passes the gates and complete a job. If you only log in as a perfect driver, you have not tested the policy you will need on a busy night.

Merchant assist is a second demand path, not a button on the same rider screen. The admin has merchant management and commission. Ask to see a venue-placed job and the commission record. Do not print a split percentage in a venue pitch until that screen has been shown. Scan booking at the door is a related intake path and is already covered in the venue scan article. One mention is enough here. Keep the purchase test on whether merchant assist is a real admin object, not a verbal promise.

Documented pricing includes the usual fare components, time-period cycles, a mileage-tier preferential price, and a fixed-price switch. Ask to see those controls against your own policy. Do not assume a local tariff ships preloaded. A free trial is also not a documented item. Asking for test accounts is still the right move.

The same honesty applies to growth talk. Account managers, referral codes, and referral rewards are documented, but they are a later commercial layer. If a vendor leads the demo with acquisition tools, steer the meeting back to booking, go-online, and merchant assist. You can inspect referrals after the three paths work. You should not score a referral module as a substitute for a blocked go-online test.

If you are evaluating Ptaxi designated driver software, keep the meeting on these three paths. Performance figures and license-brokerage services are not proven product facts in the available lists. Leave them off the already-included column. The same rule applies to any claim that the vendor will handle local operating permits for you: ask for it in writing, or treat it as work you must do with the local authority.

A three-path checklist

  • In the rider client, log in, view an estimate, place a job, book for someone else, and, if you need it, request more than one driver. Try the minimum-mileage setting if short trips are a problem.
  • On the driver side, confirm verification, then fail a go-online gate with low reserved balance or a missing collection QR, and confirm the block. Complete a later job with a driver who passes.
  • At bill confirm, complete one payment with configured in-app methods or balance, and one offline collection if you will use it.
  • Place one merchant-assist job and find the commission in the admin. Do not combine this with the rider-placed job as a single click.
  • Write permit brokerage, trial length, a driver mini-program, a standalone browser client, and performance claims as unverified.

FAQ

Can I start with the software before I have a local operating permit? A software demo is not a license. Permit or license brokerage is not described as a product service. Confirm operating rules with the authority in your market, and do not treat a completed test trip as proof that you may go live.

Does the system ship with local fare tables already filled in? No. Documented pricing can include a base fare, distance, time, long-distance, and waiting fees, plus time-period cycles and a mileage-tier preferential price. A fixed-price switch is also documented. Ask to see those controls on your own policy. Do not assume a local tariff is preloaded.

Is a free trial a documented feature? No. You can still ask for test accounts and run booking, a blocked go-online attempt, and bill confirm before you sign. Whether a trial is offered, and for how long, is a commercial term.

Should merchant assist be tested on the same click as a rider booking? No. Merchant assist is a separate intake path, with merchant management and commission in the admin. Book one rider job and one merchant-assist job, then confirm the commission appears in the admin. Do not write a commission rate into a venue pitch before you have seen that screen.

Close

Choose designated driver software by accepting three paths: rider booking, driver go-online gates, and merchant assist. A reputation list is not a substitute for that demo. Write what actually ran into the acceptance list, and keep permits, trials, and unshown clients as open items.

Look at the documented clients on the designated driver app product page. If you want a walkthrough of Ptaxi, bring a test rider, a test driver, and a test merchant, and run one job on each path before you compare vendors by name.

Frequently asked questions

Can I start with the software before I have a local operating permit?

A software demo is not a license. The feature lists do not describe permit or license brokerage as a product service. Confirm operating rules with the authority in your market, and do not treat a completed test trip as proof that you may go live.

Does the system ship with local fare tables already filled in?

No. Documented pricing can include a base fare, distance, time, long-distance, and waiting fees, plus time-period cycles and a mileage-tier preferential price. A fixed-price switch is also documented. Ask to see those controls on your own policy. Do not assume a local tariff is preloaded.

Is a free trial a documented feature?

No. You can still ask for test accounts and run booking, a blocked go-online attempt, and bill confirm before you sign. Whether a trial is offered, and for how long, is a commercial term.

Should merchant assist be tested on the same click as a rider booking?

No. Merchant assist is a separate intake path, with merchant management and commission in the admin. Book one rider job and one merchant-assist job, then confirm the commission appears in the admin. Do not write a commission rate into a venue pitch before you have seen that screen.

Related articles

Designated Driver Admin Roles: Own-Company Data vs Subordinate Companies

A group that runs several designated-driver companies cannot give every branch the same back-office view. Admin roles separate data permissions — own company only, or own company and subordinate companies — from operation permissions that control which features a backend administrator can use. Company records and staff accounts sit in the same permission area. This is a procurement question about who sees which books, not a slogan about enterprise access.

· 7 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.