We Used to Run This on a Notebook

Not that long ago, if you called us to book a cab, someone wrote your details down by hand — pickup point, time, destination — on whatever page of the register was open. Driver assignments went out over a WhatsApp group. Invoices, when someone remembered to make one, were typed up in Word and sent whenever there was time.

It worked, mostly, back when we had a handful of vehicles. It stopped working cleanly somewhere around the point we crossed a dozen cars and were doing airport runs, outstation trips, and local bookings all on the same day.

We're being upfront about this because we think it's relevant. A lot of taxi services in Mangalore — and honestly, across India — still run this way. There's nothing wrong with it at a small scale. But it starts creating real problems the moment volume goes up.

Where the Old System Actually Broke

Double bookings. Two people in the office update the same register or spreadsheet, and somehow the same vehicle ends up promised to two different customers on the same morning. This happened to us more than once, and it's not a great way to lose a customer.

Drivers missing details. A booking gets confirmed, but the driver either doesn't see the WhatsApp broadcast or gets it late. He shows up at the wrong pickup point, or later than expected, and now it's our problem to fix on a call while the customer is standing on the road waiting.

Invoices that took days. For our corporate and travel-agent clients, invoices needed to be accurate — right GST rate, right breakdown, right details. Doing this by hand meant delays, and delays meant slower payments on our end.

Nobody actually knowing where a vehicle was. If a customer called asking where their driver was, the honest answer was often "let me call the driver and find out" — which isn't exactly reassuring when someone's trying to catch a flight.

None of this is unusual. It's basically the standard story for cab operators who started small and grew past what a notebook and a WhatsApp group can reasonably handle. There's a fairly accurate description of this exact pattern here, if you're curious — it's close enough to our own experience that it's a little uncomfortable to read.

What Changed

At some point we moved our bookings, dispatch, invoicing, and driver communication onto a proper system instead of splitting it across a register, a spreadsheet, and three different WhatsApp groups. We didn't build this ourselves — we run on Easy Trip Booking, which is built specifically for cab and travel operators dealing with exactly the mess we were dealing with.

The switch wasn't instant, and we won't pretend it was painless. We had years of booking history sitting in spreadsheets, and moving that across without losing anything was honestly the part we were most nervous about. It turned out to be less of an issue than expected — there's a decent explanation of how that kind of migration typically works, which is roughly the process we went through.

What It Actually Changed for Our Customers

• Bookings don't get lost or double-assigned anymore, because the system blocks a vehicle the moment it's booked.
• Drivers get their trip details automatically, so there's no more relying on someone reading a WhatsApp group message in time.
• Invoices go out the same day, correctly, instead of whenever someone gets around to it.
• If you message us with a question about your booking, whoever's answering can actually see your booking details immediately, instead of asking you to repeat everything while they dig through a register.

We're not going to claim we're the only operator in Mangalore doing this — more cab businesses are moving this direction every year, for pretty obvious reasons. We just got there earlier than most, and it's changed how we operate day to day more than we expected it to.

Why We're Telling You This

Mostly because if you've had a bad experience with a taxi operator before — missed pickups, no idea where your driver is, invoices that take a week — we'd rather you know upfront that we've deliberately tried to fix those exact problems, rather than just saying "we're reliable" and leaving it at that.