One branded mobile app for passengers and drivers, quick permission-aware operations inside the app, and a full web admin panel for your team. Modernize the fleet without asking everyone to juggle separate apps.
Many taxi fleets still combine phone bookings, dispatcher knowledge, and manual coordination. Those practices may work locally, but customers increasingly expect a fare estimate, a visible driver location, clear payment choices, and support through a mobile experience.
Modernizing a fleet is not just a matter of replacing the booking screen. The operator also needs driver onboarding, dispatch, phone-booking support, permissions, settlement records, Arabic content, and reporting that match the way the business actually runs.
Waslni is the white-label taxi platform for the middle path: keep the dispatchers who know your city, keep cash as a primary payment method, and add one modern mobile app that switches between passenger and driver modes. Permission-aware operational tools are available inside the app for quick action, while the full web admin panel handles configuration, reporting, roles, and day-to-day control.
Passengers and drivers use the same branded mobile app in different modes. Your team gets quick operational controls in-app and the full administration workspace on the web.
Passengers book from the same iOS and Android app your drivers use. It supports address search, fare estimates, cash and configured digital payment methods, in-app chat, safety tools, ratings, and favourite places in Arabic or English.
A driver signs in to the same app and sees the driver experience: online status, trip requests, navigation, earnings, and the admin-composed registration and document flow. No second app to install or maintain.
Authorized staff can reach quick operational tools from inside the app. The web admin panel provides the full workspace for fleet activity, requests, reports, settlements, service types, permissions, and business configuration.
The product fits the way MENA fleets actually run, not the way a Silicon Valley startup imagined fleets run.
The phone-booking workflow can preserve a familiar dispatcher role while app-based records are introduced. Measure booking time, errors, missed work, and support load in the fleet’s pilot instead of assuming a universal speed gain.
Waslni records cash trips in the driver wallet so the operator can reconcile collected cash against the chosen settlement cycle. Card and wallet methods can be enabled through a supported integration after the merchant account and tenant are configured.
The same tenant configuration supports an operator starting in one service area and expanding its team, services, and operating rules over time.
Admins compose registration sections, required fields, and document requests by service type. Your team reviews submissions from the admin panel; local licensing and regulatory approval remain the operator’s responsibility.
The operator console is designed to make frequent dispatch tasks quick while keeping the complete configuration and reporting workspace on the web.
A dispatcher records the caller and pickup, then follows the configured assignment workflow. Demonstrate the exact steps and exception handling with your own operating roles.
Configure operating geography and city pricing rules, then test boundary pickup, destination, assignment, and fallback behaviour in the deployed setup.
Review the cash, commission, digital-payment, adjustment, and payable data available in the configured deployment. Finance should approve the reconciliation and export process actually demonstrated.
Configure surge multipliers per day-of-week, per time-of-day, per service type. Friday-evening Cairo is not the same as Tuesday-morning Ramallah.
Wallet visibility and payment providers depend on configuration. Test top-up or cash-out only where implemented, and verify gateway reconciliation and adjustment audit evidence with finance.
The mobile experience supports Arabic right-to-left (RTL) layouts alongside the platform’s other bundled languages. Customer-facing content can be localized for the market you operate in.
The honest comparison.
Use these scenarios in a controlled shift and attach the booking ID, evidence, result, owner, and blocking decision.
Create equivalent bookings through every retained channel; verify identity, pickup, service type, fare rule, assignment, notifications, cancellation, and support hand-off.
Test registration fields, document review, service eligibility, availability, offer acceptance, navigation hand-off, completion, earnings display, and suspension.
Test only configured methods. Trace cash and digital records through success, failure, cancellation, adjustment, refund where supported, and the finance reconciliation evidence actually available.
Compare old and new records, assign every mismatch, confirm support and incident contacts, and rehearse how the fleet returns to the fallback workflow.
A staged process shaped around your fleet, market, approvals, and operating readiness.
Share the brand kit and target service areas. We provision the tenant, subdomain, admin access, and initial geographic configuration.
Your operations lead configures the fleet’s service types, fare formulas, commissions, peak windows, and the App Experience that customers see.
Invite a pilot group sized for your service area. Drivers sign in through the same app, submit the configured fields and documents, and your team reviews them from the operational tools or web admin panel.
Submit the branded app through your developer accounts, validate dispatch and support workflows, and move to public launch after operational checks and store approval.
“White-label” means the product is presented under your fleet’s identity rather than the software vendor’s. Waslni provides one branded iOS and Android app with passenger and driver modes, plus permission-aware in-app operations and a full web admin panel.
Yes. App Experience settings let the operator choose a rides-first, delivery-first, rides-only, delivery-only, or combined experience. This keeps the same platform useful for a taxi fleet, a delivery business, or a super-app combining transport and marketplace services.
Yes, and it is one of the most common starting points. The operator console has a phone-booking shortcut: dispatcher types name + phone + pickup address, the system finds the nearest driver, the ride starts. Your dispatchers transition from radio to console without retraining.
Yes. Cash is a first-class payment method. The app calculates the fare; the driver collects cash; the platform records it in the driver wallet; at end-of-shift or end-of-week the settlement run reconciles cash collected against platform commission owed. Cards and wallets process through your gateway in parallel.
Timing depends on brand assets, developer accounts, gateway approval, local licences, data preparation, testing, and store review. We confirm the timeline after those dependencies are scoped.
The current platform integrations include Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Availability depends on the operator’s merchant account and configuration; gateways for another country require a separate technical and commercial review.
The platform helps you collect driver registration data, request documents, and keep operational records. The operator remains responsible for local transport licences, data-protection obligations, and advice from the relevant authorities; Waslni is a software provider, not a transport regulator or legal adviser.
Explore the unified mobile app, permission-aware operational tools, and the full web admin panel in the demo environment.