was unjustly denied employment* background check cam back cleared on all accounts was t...

GetHuman660918's Disputes issue with Lyft from May 2018

Help with my Lyft issue
Top Tip from another customer
If you are trying dispute charges that were made against you or trying to a get a refund from Priceline then click here https://priceline.custhelp.com/app/chat/chat_launch_help/.
The issue in GetHuman660918's own words
was unjustly denied employment* background check cam back cleared on all accounts was told by samba safty that if you hadnt driven for one year in the state of california you couldnt be hired but when checked lyft website it stated it was in the united states ive driving commerically in the us since **** class A since **** put in a dispute with samba safty but neber heard back can i deactivate my excisting account and start fresh
GetHuman660918 did not yet indicate what Lyft should do to make this right.
I have an issue with Lyft too
How GetHuman660918 fixed the problem
We are waiting for GetHuman660918 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
This email address isn't valid

Lyft

Disputes issue
Reported by GetHuman660918
May 6th, 2018 - a yr ago
I have an issue with Lyft too
Not resolved
Seen by 9 customers so far
Similar issue to 43068 others
0 customers following this
Items needed
Account holder name
Email address on account
Phone number on account
Date of birth
Timeline
GetHuman660918 started working on this issue
May 6th, 2018 4:18pm
GetHuman660918 shared this issue with friends on Facebook
May 6th, 2018 4:19pm
GetHuman660918 indicated the issue is not fixed yet.
May 7th, 2018 5:33am
GetHuman660918 indicated the issue is not fixed yet.
May 9th, 2018 7:17pm
GetHuman660918 indicated the issue is not fixed yet.
May 12th, 2018 6:40pm