01 /
What is taxi dispatch software?
It is the operational layer that connects bookings, drivers, active rides, support, and administration. In Waslni it works with the unified rider-and-driver app and the web dashboard.
Taxi dispatch software
Modern dispatch,
with a practical
path from phone and radio.
Give operations teams clear visibility without forcing riders and drivers into separate apps. Waslni combines one role-aware mobile app with quick in-app administration and a full web dashboard, while App Experience selects rides, shops and delivery, or both.
One app
Rider and driver experiences by role
Live visibility
Follow active drivers and rides
Cash records
Keep trip and wallet activity visible
Role-based
Control which staff can take each action
One app
Rider and driver experiences by role
Live visibility
Follow active drivers and rides
Cash records
Keep trip and wallet activity visible
Role-based
Control which staff can take each action
Last updated · July 20266 min readDispatch · Operations
A taxi fleet moving away from radio and paper needs a clear operating transition, not dramatic claims about instant productivity. The goal is to place bookings, active rides, drivers, and permissions in a system the team can learn safely.
Waslni supports a unified mobile app for riders and drivers. Operations staff can handle quick administrative work from the app, while the web dashboard provides the broader view for settings, reviews, permissions, and reporting.
Keep the existing phone or radio workflow available during a pilot if your operation depends on it. Migration time, training needs, and fallback duration vary by fleet; they should be agreed from observed use rather than fixed four-week or percentage promises.
Operational foundation
Useful dispatch controls,
described accurately
Bookings
Support staff-assisted booking
Operations teams can enter supported booking details for customers who contact the business instead of using self-service.
Visibility
See active drivers and rides
Use the operational view to follow live activity and investigate a trip when support needs context.
Intervention
Controlled operational actions
Authorised staff can use the actions exposed by the platform. Avoid promising unsupported two-click reassignment or automation.
Reporting
Trip and finance visibility
Review the reports and exports that the deployed configuration actually provides. Bank-file exports or tax readiness require separate verification.
Cash
Cash-aware records
Cash trips and driver balances remain visible in the platform so the operator can reconcile them using its approved accounting process.
Permissions
Role-based access
Use the permission system to separate operational, support, and administrative responsibilities.
Dispatch questions
Clear answers
for fleet teams
02 /
Do riders and drivers need different apps?
No. They use one mobile app, and each account sees the experience appropriate to its role.
03 /
Can staff administer the service from a phone?
Quick operational administration is available inside the app. The full web dashboard remains the main surface for broader configuration, permissions, review, and reporting.
04 /
Does Waslni replace our PBX or integrate with it automatically?
Do not assume so. Your existing telephony can remain part of the workflow, while any CTI or PBX integration must be confirmed and scoped separately.
05 /
How long does migration take?
It depends on data preparation, configuration, staff training, pilot results, and local operations. A staged rollout with a tested fallback is safer than a fixed universal promise.
Review the workflow
Test dispatch with your team,
before changing the operation
Use the demo to review booking, live visibility, the unified app, permissions, and administration surfaces.