Alright so, I ordered a Lyft home tonight to my default home address and when the drive...

GetHuman1021783's customer service issue with Lyft from August 2018

Help with my Lyft issue
Tip from another customer
If you are having technical issues with your Sprint device then I suggest bringing the device into a store near you. You can use this locator to find the store - http://storelocator.sprint.com/locator/
The issue in GetHuman1021783's own words
Alright so, I ordered a Lyft home tonight to my default home address and when the driver arrived he even confirmed the correct address, however while he was driving the destination somehow changed and it took us the complete opposite way and ended up charging me twice the amount. I did not at any point change the address on the app. The driver was very kind and said he would try to get the issue resolved and I ask that you please do. I was supposed to be charged $** but ended up paying $** and in the complete opposite way. I really hope to hear from you soon, thank you.
GetHuman1021783 did not yet indicate what Lyft should do to make this right.
I have an issue with Lyft too
How GetHuman1021783 fixed the problem
We are waiting for GetHuman1021783 to fix the problem and share the solution with the rest of us customers.
Please help with my Lyft issue
Do you have a customer issue as well?
We can help you get Lyft's attention and get better help faster. Tap below to get started.
Having Lyft issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would Lyft email you?
This email address isn't valid

Lyft

Customer service issue
Reported by GetHuman1021783
Aug 22nd, 2018 - 4 mons ago
I have an issue with Lyft too
Fixed
Seen by 2 customers so far
Similar issue to 16745 others
0 customers following this
Items needed
Account holder name
Email address on account
Phone number on account
Date of birth
Timeline
GetHuman1021783 started working on this issue
Aug 22nd 4:04am
GetHuman1021783 indicated the issue is not fixed yet.
Aug 22nd 1:11pm