01 /
Do riders and drivers use separate Waslni apps?
No. They use one mobile app, and each account sees the experience that matches its role.
Modernise a taxi business — 7 steps
Upgrade the operation,
keep what works
and test every change.
Move from phone and radio toward a unified app and connected administration without discarding the local knowledge your team already has.
7 steps
A staged path from current operation to launch
One app
Rider and driver experiences by role
Two admin surfaces
In-app operations plus full web control
Flexible scope
Rides only or a broader App Experience
7 steps
A staged path from current operation to launch
One app
Rider and driver experiences by role
Two admin surfaces
In-app operations plus full web control
Flexible scope
Rides only or a broader App Experience
Last updated · July 20268 min readOperator guide
Modernising an established taxi business is different from starting from zero. You already have local knowledge, drivers, customers, and operating habits that should inform the transition.
The technology change is also simpler than the old “customer app plus driver app” model suggests. Waslni uses one mobile app with role-aware experiences, quick administration inside the app, and a full web dashboard.
Use these seven steps as a decision sequence, not as a fixed promise about time, driver counts, conversion rates, or market results.
Seven steps
Move in order,
measure at every stage
Confirm the operating model first, then configure, train, pilot, and expand from observed results.
01 /
Step 01
Define the service and operating area
Choose the city, customer need, service hours, vehicle categories, and coverage. Avoid expanding before the first operation is stable.
02 /
Step 02
Confirm licences and responsibilities
Verify operator, driver, vehicle, tax, insurance, privacy, and app-booking requirements with qualified local advisers. A UK software-company registration does not replace local transport approval.
03 /
Step 03
Assess drivers and vehicles
Check smartphone access, vehicle data, required documents, support needs, and which drivers should join the pilot. Use configurable registration fields instead of a hard-coded document list.
04 /
Step 04
Set the App Experience
For a taxi launch, show rides only. If the business later needs delivery or shops, App Experience can expose those modules without requiring a second customer app.
05 /
Step 05
Prepare the operations team
Map the current phone, radio, support, cash, and escalation procedures. Train staff on quick in-app controls and the full web dashboard, while keeping a tested fallback during the pilot.
06 /
Step 06
Invite existing customers carefully
Explain the practical benefit, provide a trusted download path, and test support messages. Measure adoption rather than publishing a universal conversion-rate promise.
07 /
Step 07
Pilot, review, then expand
Run a limited launch, review trip completion, support cases, driver availability, pricing, and payment records, then expand only after the operation is dependable.
Taxi operator questions
Clear answers
for a safer transition
02 /
Can we keep phone or radio booking during the transition?
Yes. Keep the current workflow available during the pilot if operations depend on it. Any PBX or telephony integration should be confirmed separately.
03 /
Where does the administration happen?
Quick operational tasks can be handled inside the app. The full web dashboard covers broader settings, permissions, review, and reporting.
04 /
Can the customer app show rides only?
Yes. App Experience can be configured around rides only. Delivery and shops can remain hidden unless the operator chooses to offer them.
05 /
How long does modernisation take?
The timeline depends on licensing, configuration, data, training, app-store review, and pilot results. Set milestones from the project plan rather than a universal four-week promise.
Review the transition
Configure a rides-only demo,
with your real roles
Test the unified app, in-app operations, web dashboard, service types, registration fields, and permissions.