4 ms·
Why should a customer pay for bad app design? The app allowed the code to be applied to that specific restaurant. Then backend refused it and customer pays the
by BossingAround 5y ago
Why should a customer pay for bad app design? The app allowed the code to be applied to that specific restaurant. Then backend refused it and customer pays the difference. In what world is that acceptable?
- berberous 5y agoThis is so bad I can’t imagine even Uber Eats really thinks it’s acceptable. Probably a bug. The problem is that tech support are useless automatons and there is no way to really escalate to those that can see it clearly should be fixed other than shouting on Twitter. Very frustrating when there’s no avenue for real review and redress other than chargebacks.
- jcheng 5y agoAfter seeing https://www.reddit.com/r/assholedesign/comments/rj0a19/made_sure_i_wasnt_ordering_near_closing_time_now/ https://www.reddit.com/r/assholedesign/comments/rj0a19/made_..., I don’t think Uber Eats deserves the benefit of the doubt.
- paulgb 5y agoI recently(ish) discovered a legitimate billing error with Lyft/Bay Wheels that caused a few bucks of overage[1]. It wasn’t a lot of money to me, but I pointed it out to them as it was an obvious error. To their credit, they refunded several entire trips, not just the disparity, and I believe they refunded others’ affected rides as well. I think that’s a satisfactory approach: mistakes happen, but companies should make an effort to ensure that they don’t benefit if they make an accident that favors themselves. [1] https://twitter.com/paulgb/status/1449779457200300033?s=21 https://twitter.com/paulgb/status/1449779457200300033?s=21