2017-05-22

notmypresident: (Angry Daffy)
You'll have to forgive me for ranting. I had to do battle with an Uber driver this morning, and I'm still fuming. Now, I know that no company is perfect, but I have to say that this was the worst experience I've yet had with the car-driving app. And yes, I know that in the scheme of things, it wasn't all that terrible. But still...

My dialysis clinic is located near the San Leandro Hospital. The current GPS function of the Uber app will often flag the hospital or one of its satellite buildings for my location, so I always send a text message to let a driver know exactly where I'll be. And then I always follow that up with a voice call. But this morning's driver didn't respond to my initial messages, and when he finally answered my call it was immediately clear that his speaker phone was a hot static mess. I couldn't understand anything through the noise. I called twice more (in addition to my text messages) and finally left a voice mail — again, with my exact location. Nothing. It was clear to me from checking his real-time location on the app that he was ignoring my messages. And then I watched him drive straight past me on his way to (I presume) San Leandro Hospital.

I canceled the trip and was told that a $5.00 cancellation fee would apply. When I got home, I went into the app to request a refund. Like other companies, Uber limits your "reasons for requesting a refund" to a simple drop-down menu. After about five minutes, I was finally able to send off a message detailing what had happened. I got a response a short time later, saying that the reason for the charge was because I had canceled the ride. Which, I mean... duh! So I wrote back to say that a driver being out of a communication with a defective phone should raise policy issues with Uber.

Not long after that, the company wrote to say that I would receive a credit on my next trip. And it only took 45 minutes of carping!

Quick, let's just cut to Another Hot Guy.