Dispatch system
Dispatch workspace
every order in view
Give your team one place to handle bookings, follow routes and resolve exceptions. Keep routine work in the system so dispatchers can focus on the decisions that need a person.
- One order queue
- Automation and manual control
- Routes, history and exports
- Apps, dispatch and management together
The actual product
A working view of your fleet
Move from the order form to its route and event history. Corporate bookings and the order archive are part of the same workflow.
Edit the tariff, pickup, stops, date and time in one form. Scheduled orders remain visible in their own queue.
Open the full screenshot
See the route, distance, current state and event timeline together, without piecing the trip together from separate messages.
Open the full screenshot
Choose the company account and employee when creating a booking. The form shows the company balance and the trip price.
Open the full screenshot
Filter by status, booking source or period. Review routes, payments and vehicles, then export the selected records to CSV or Excel.
Open the full screenshotEvery booking has its place
Phone calls with context
With a telephony integration, the caller card can show trip history and recent addresses before the dispatcher answers. The operator starts with context, not a blank form.
App and web bookings
Orders from connected customer apps and web booking enter the same queue. The team does not need a separate dispatch screen for each source.
Time to prepare the pickup
Scheduled bookings retain their date and time. Advance assignment and pickup buffers are configured around your fleet’s operating rules.
Trips on a company account
Corporate bookings use the company agreement, employee access, limits and cost centres configured for the account. Settlement can be handled by the company without payment at pickup.
People and automation
Routine for the system, decisions for your team
Assignment by fleet rules
The assignment configuration can consider distance, rating, workload and declined orders. In the current driver app, auto-pick proposes a suitable order and the driver confirms acceptance.
Manual control when needed
A regular customer, a special vehicle or a disputed situation may need an operator’s decision. Select a driver manually from the order form when your access rights allow it.
Zones, priorities and restrictions
Agree rules for zones, airports, vehicle suitability and customer restrictions. The assignment logic follows the operating model configured for your fleet.
An agreed order at taxi ranks
Rank and airport queues can use arrival order. Queue policy is agreed for the location rather than left to informal dispatcher preference.
94% of orders without dispatcher intervention is a development target from the product brief, not a measured result or service guarantee.
The operational picture
Understand what is happening during the shift
- Online vehicles, active trips and orders awaiting assignment form the live operational view available in your configuration.
- Assignment reporting can distinguish automatic proposals and manual decisions, including timing and the reason for intervention.
- With the relevant country integration connected, the workspace can show receipt status for each trip, the pending receipt queue and the last successful submission.
Planning continuity
Prepare for the difficult moments
Connection loss, power cuts and peak demand need agreed operating procedures. Confirm the available failover scenarios for your fleet during the demo and setup.
Connection to the data centre
Local shift operation, continued assignment and queued receipts are an offline development scenario. The 36-hour window is a target; availability and limits require separate validation before launch.
Power cuts
Plan which devices and network connections remain available when the office loses power. Continued operation depends on your backup power, connectivity and deployed setup.
A driver is unavailable
Timeout and reassignment rules can return an unanswered order to dispatch. Agree the timeout and exception procedure so the team knows when to intervene.
Peak booking demand
Keep the whole waiting queue visible. Waiting-time indicators and prioritisation rules help the team decide which exceptions need attention first, when enabled for the fleet.
Before you get started
Can a dispatcher choose a driver manually?
A regular customer, a special vehicle or a disputed situation may need an operator’s decision. Select a driver manually from the order form when your access rights allow it.
Can several booking sources work together?
Orders from connected customer apps and web booking enter the same queue. The team does not need a separate dispatch screen for each source.
Is 36-hour offline operation already guaranteed?
Local shift operation, continued assignment and queued receipts are an offline development scenario. The 36-hour window is a target; availability and limits require separate validation before launch.
How can I see it in action?
We can set up a demo fleet with your fares and zones and run a shift together with your dispatcher. We plan one evening for this session and agree the schedule with you.
Additional order network
The network stays under your control
Share an order with connected partners and follow its execution by another fleet’s driver. Participation and settlement rules are managed by the owner.
Pay as your fleet completes orders
When a company creates and completes an order itself, it pays DispHub 1% of the full order value once. When the order is passed to another company and completed by that company, the company that passed it on and the company that completed it each pay DispHub 1% of the full value of that order. No subscription or per-driver fees.
App branding is a one-time payment. Individual development and marketing services are ordered separately.
See pricingSee your city in your app
Explore a demo fleet with your fares and zones alongside your dispatcher. The proposed demo has no obligations; we confirm the conditions when arranging it.