How to Select Taxi Dispatch Software: App and Phone Jobs on One Desk
Taxi operators shopping for dispatch software often start with one question: can passengers book by phone as well as in an app? That question is too thin. A phone line that leaves a note in a side spreadsheet is not the same as a phone job that appears on the same dispatch desk, on the same driver app, next to an app-booked trip. The selection test is whether both channels land in one ledger, and whether the desk can tell a meter trip from a simple phone job.
Ptaxi's taxi dispatch software documents passenger booking from the app, phone bookings that staff can place or that arrive as a voice message, a driver app on Android and iOS, and a PC dispatch desk. Meter taxi orders use onboard meter pricing and bill confirm. Phone-booked dial-a-ride orders use a simplified flow with no in-app navigation and offline collection at the curb. Those two paths are not interchangeable. How the simple flow runs after accept is already covered in the dial-a-ride simple flow article. This piece is about what a buyer should force into one demo.
One desk, not two ledgers
Start the meeting with a written list of the channels you actually use: the passenger app, a staff-placed phone booking, and a voice-message booking if your desk still takes recorded requests. Then run one test job through each channel you intend to buy. The point is not to watch a polished app tour. The point is to see whether the jobs show up in the same admin order list and can be offered to the same logged-in driver.
If a phone job only lives in a call log, your night supervisor will still be reconciling two systems at close. If an app job never appears on the same screen as the phone work, you do not have a dispatch platform. You have two intake tools. Real-time vehicle location and trip track playback can help a supervisor find a car after the job is live, and that desk view is already described in the real-time location and track playback article. Use it as a follow-on check, not as a substitute for seeing the booking land in the order list first.
Ptaxi taxi software can be measured against that test because the documented user side includes the app and phone booking, and the documented admin side is a single PC desk. Do not treat a slide that lists phone and app support as proof. Watch the records appear.
Proxy booking belongs on the same idea, not as a second product. The passenger app can book a taxi for someone else by collecting a name and phone number. That path is already described in book a taxi for someone else. In a selection demo, one proxy job is enough: confirm it is a normal taxi order on the desk, not a hidden side process. This article will not walk through proxy booking step by step.
Meter settlement and simple phone jobs are different acceptances
A common failure in vendor meetings is to run one happy-path app trip and then say phone is supported too. If your company still takes street or meter work and also takes phone bookings, you need both playbooks on the day.
On a documented meter taxi order, the trip follows the full flow and ends at bill confirm. The passenger can pay through the configured in-app payment methods and account balance, or pay cash, in which case platform commission is deducted from the driver wallet. Do not name a card rail or a payment provider. Keep the wording to those configured methods, account balance, and cash.
On a documented phone-booked dial-a-ride order, the path is a simplified process: no in-app navigation, and collection happens offline at the curb. The driver must finish the voice-message broadcast before treating the offer as understood work. Admin business settings include an order simple-flow switch. It is not stated whether that switch is global or can be applied per order type. In the demo, ask the vendor to show how a meter job and a phone job are distinguished, and write down what you see. Do not assume that turning on phone intake automatically applies meter pricing to those jobs.
This is a tradeoff you should say out loud. One desk is simpler for supervisors. Two settlement paths are more honest for the curb. If you collapse them in training, drivers invent their own habits, and finance starts auditing phone work as if every trip must leave the same passenger-pay receipt as a meter job.
What belongs in the contract, not on the scorecard as proven
The product documents system-side phone intake and device configuration for those booking lines. That is not the same as a promise that the vendor will procure a local phone number, a carrier contract, or a staffed call center for you. Those items belong in the commercial schedule. "Supports phone booking" is not the same sentence as "we will stand up your telephony."
The driver app is documented as Android and iOS. There is no documented driver mini-program. If a salesperson promises a third driver client, mark it as unconfirmed and ask for a build you can open, or leave it out of the scorecard.
Keep this brief on the documented split: app and phone intake, one desk, meter flow versus simple flow. Do not import unused regional channels into an overseas brief unless you have a written, market-specific agreement.
Performance claims, certification badges, and a named map provider are also not proven product facts in the available lists. Do not put them in a scoring sheet as if they were already shown. The desk test still comes first.
A buyer checklist you can run in one sitting
Keep this to one pass, and do not substitute a slide deck.
- Write down the channels you will operate: passenger app, staff-placed phone booking, and voice-message booking if you need it. Leave unused channels out of the contract.
- Place one test job through each chosen channel. Confirm each job is visible on the same dispatch desk and can reach the same driver login.
- Run a meter taxi trip through bill confirm, once with in-app or balance payment and once with cash, and confirm the driver wallet can cover the commission on the cash job.
- Run a phone-booked simple-flow job. Confirm there is no in-app navigation requirement, that curb collection is offline, and that the driver must finish the voice message. Ask how the simple-flow switch behaves, and record the answer as a demo result, not as a brochure line.
- Open the driver app on iOS and on Android. Do not assume a second driver channel exists.
- Write telephony provisioning, call-center staffing, unused channels, performance, and certifications as open questions. Do not file them under "already included."
If you are evaluating Ptaxi, bring that script to the walkthrough and stay on it. The earlier simple-flow article is the training card for how a phone job runs after accept. This checklist is the purchase test for whether those jobs share a desk with app work.
FAQ
If the vendor says it supports phone booking, is that enough? No. Support can mean a call center note that never reaches the driver app. Ask for one app booking and one phone booking in the same demo, then confirm both jobs appear on the same dispatch desk and the same driver app. Write the channels you actually need into the contract.
Are meter trips and phone-booked jobs the same workflow? No. Documented meter taxi orders use a full trip flow plus bill confirm, with passenger payment or cash settlement that deducts platform commission from the driver wallet. Phone-booked dial-a-ride orders use a simplified flow with no in-app navigation and offline collection at the curb. Demo both if your fleet runs both.
Do drivers need a separate app for phone jobs? The documented driver app is Android and iOS. The list does not describe a separate driver mini-program. In a demo, open both mobile systems and confirm a phone-origin job and an app-origin job can be received on the same driver login. Do not assume a second driver channel exists.
Should every taxi company turn on every booking channel? No. Multi-channel booking is a documented capability, not a requirement to enable every entry point in every contract. List the channels you will actually operate, write those into the agreement, and accept only those paths in the demo.
Close
Taxi dispatch software should not be chosen on a yes-or-no answer about phone booking. Confirm that app jobs and phone jobs enter the same dispatch desk and the same driver app, and accept meter trips separately from simple phone-booked jobs. Put the channels you will actually use in the contract, and keep number provisioning and call-center staffing as commercial items.
Look at the same split on the taxi dispatch software product page. If you want a walkthrough, ask for a demo of Ptaxi taxi software with one app job and one phone job, then watch both records on the desk before you talk about a total price.
Frequently asked questions
If the vendor says it supports phone booking, is that enough?
No. Support can mean a call center note that never reaches the driver app. Ask for one app booking and one phone booking in the same demo, then confirm both jobs appear on the same dispatch desk and the same driver app. Write the channels you actually need into the contract.
Are meter trips and phone-booked jobs the same workflow?
No. Documented meter taxi orders use a full trip flow plus bill confirm, with passenger payment or cash settlement that deducts platform commission from the driver wallet. Phone-booked dial-a-ride orders use a simplified flow with no in-app navigation and offline collection at the curb. Demo both if your fleet runs both.
Do drivers need a separate app for phone jobs?
The documented driver app is Android and iOS. The list does not describe a separate driver mini-program. In a demo, open both mobile systems and confirm a phone-origin job and an app-origin job can be received on the same driver login. Do not assume a second driver channel exists.
Should every taxi company turn on every booking channel?
No. Multi-channel booking is a documented capability, not a requirement to enable every entry point in every contract. List the channels you will actually operate, write those into the agreement, and accept only those paths in the demo.