Switching
Leaving a shared app, step by step
If part of your bookings comes through a shared taxi app such as taxi.eu or Taxi Deutschland, you do not have to give those orders up on day one. Where it is appropriate, your current system keeps receiving them while your customers move to your own branded app. How shared-app orders are handled after cutover depends on that network's terms and is planned in discovery.
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. 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
- Keep the orders flowing. During the switch, your current system stays live and keeps receiving shared-app orders.
- 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.
- Decide the end point. You choose when, or whether, to stop taking shared-app orders.
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 or Taxi Deutschland straight away?
No. Your current dispatch system keeps running in parallel during the switch, so orders from a shared app keep reaching you through it. Your customers move to your own branded app at the pace you choose, and you decide when, or whether, to stop taking shared-app orders.
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, 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
A no-commitment conversation about how your operation works today, and a technical session for your IT lead if that helps. We will tell you honestly what we know, what we would need to find out, and whether a migration makes sense.
- A migration blueprint built around your operation
- Your current system keeps running while each step is tested
- Honest answers, including what we need to find out first