App Cabs woes in Bangalore

While we talk about, how App Cabs have made our life easier, there are 2 sides to this coin. For instance, today it took me more than 75 minutes of wait time (from first booking confirmation), 3 bookings, and almost 2 kms. of walking, to get into a cab.
Today, after seeing a traffic jam outside my apartment, I decided to hail a cab, instead of driving. Booked first cab through TFS. As he was taking time, to help save it for both of us, started walking to meet him on the way. Decided to check on status before our rendezvous point. To my surprise, he has taken some other route, and is now further away from me. On being called, our language skills aren't a good match, and I am better off cancelling it.
Tried Ola, as in my mind TFS sucks now. It showed cab 2 minutes away, which I happily booked, only to be confirmed that my cab is now 7 minutes away. Looking at cab's location, I know it can't reach me in less than 15 minutes. Cancelled it.
Being stranded away from my house, and exhausted, tried Uber, which was showing 'No Cabs' all this while, booked a cab, showing 5 minutes away. The cab came in almost 15 minutes.

Two important lessons learnt
  1. Stay put after booking where you are. Let cab come to you, instead of otherwise 
  2. Should not plan time constrained trips on app cabs. My new worst case delay (booking to getting in) now stands at 75 minutes, from 45 minutes I earlier had

Comments

Popular posts from this blog

504 Gateway Timeout on Amazon AWS ELB (Elastic Load Balancer)

AWS RDS incompatible-parameters solved

Sone ke gahno ki Bangalore mein adla badli (exchange)