I took lyft on Friday Aug **th shortly before noontime. Was picked up from **** Via Mar...

GetHuman-gsquare_'s customer service issue with Lyft from August 2018

Help with my Lyft issue
The issue in GetHuman-gsquare_'s own words
I took lyft on Friday Aug **th shortly before noontime. Was picked up from **** Via Mariposa West, laguna Woods, CA. Was dropped off at ***** Via Fabricante, Mission Viejo, CA. When I booked this ride the cost was supposedly $*.** with the **% discount applied.**Got an e mail about an hour later supposedly for my receipt. When I looked at it, the pick up point was correct but the destination showed an address in Costa Mesa, CA To my advantage, the card I had on file did not go through as I'm being charged incorrectly. I would like to pay the driver but with the correct amount. Please look into how this thing came about and make the necessary changes. I assure you that the charge will go through if it is only $*-*.**Looking forward to a speedy resolution of this case. Thank you
GetHuman-gsquare_ did not yet indicate what Lyft should do to make this right.
I have an issue with Lyft too
How GetHuman-gsquare_ fixed the problem
Ay lyft customer help, you can email them
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 GetHuman-gsquare_
Aug 12th, 2018 - 7 mons ago
I have an issue with Lyft too
Fixed
Seen by 4 customers so far
Similar issue to 15445 others
0 customers following this
Items needed
Account holder name
Email address on account
Phone number on account
Date of birth
Timeline
GetHuman-gsquare_ started working on this issue
Aug 12th, 2018 11:17pm
GetHuman-gsquare_ confirmed the issue is fixed. Hooray!
Aug 14th, 2018 12:36am
GetHuman-gsquare_ confirmed the issue is fixed. Hooray!
Aug 16th, 2018 1:38am