Switching
Leaving a shared app, step by step
If part of your bookings comes through a shared taxi app such as taxi.eu, plan the move with care. Where it is appropriate, your current system keeps receiving those orders during the switch while your customers get to know your own branded app. As part of migration planning, we review your booking channels and identify which can be supported after migration; continued access to the shared app is not guaranteed.
Why it matters
A shared app gives a central reach, but the app brand, the app-store listing and the customer relationship belong to the network. Shared-app orders also depend on the network: they reach your central through your current dispatch system and do not automatically move with you to a new one. Moving to your own app puts your name on the customer’s phone and keeps the relationship, and the data, with you.
How the move works
- Plan for the orders. During the switch, where it is appropriate, your current system stays live and keeps receiving shared-app orders until cutover. Continued access to the shared app after cutover is not guaranteed, so we review together which booking channels can be supported after migration.
- Launch your own app when you are ready. Your branded passenger app goes live once drivers, dispatch and support are ready for public demand.
- Bring customers across. Tell existing customers by message, in your vehicles and on your website; regular and corporate customers keep their details.
- Agree the cutover. The cutover date is agreed in advance, with a plan for the customers who reach you through the shared app today.
Keep your phone number
Your phone numbers and call handling are planned as their own step, so the customers who still phone are looked after throughout.
See also: your own branded passenger app and two systems side by side.
FAQ
Questions operators ask
Do we have to leave taxi.eu straight away?
Not on day one. Where it is appropriate, your current dispatch system keeps running during the switch, so orders from a shared app such as taxi.eu can still reach you through it until cutover. Continued access after cutover is not guaranteed: as part of migration planning, we review your booking channels, identify which can be supported after migration and plan how your customers move to your own branded app.
How do we avoid double bookings while two systems run?
Before the pilot, we agree exactly which bookings and which drivers each system handles, how availability is shared, and what the fallback and escalation steps are at each stage.
Will we lose phone calls on the day we switch?
No. Phone numbers and call handling are planned as their own step, and your current system keeps taking calls until the agreed cutover. Phone bookings then run in the same dispatch as app and web orders.
Proof
Operators who made the switch
Keep reading
How the switch works
Our migration framework runs from understanding your operation to hypercare after go-live.
Read more →Your data comes with you
We import the customer, account, address, booking-history, driver data, vehicle, zone and tariff data you can lawfully and practically export from your current system.
Read more →Two systems side by side
Where it is appropriate, your current system and eCabs Technologies run in parallel during the migration.
Read more →Next step
Talk to us about your operation
Bring us your operation, your rules and your requirements, and we’ll work through how to deliver the solution with you: what is available today, what we configure and what we build before your launch. No technical background needed, and no commitment.
- A plan built around how you work, not a one-size-fits-all package
- Your current way of working keeps running while each step is tested
- Honest answers, including what we need to find out first