I need some help because all I wanted to do was make sure that the right I requested di...

GetHuman7366588's problema de servicio al cliente con Lyft de abril 2022

Ayuda con mi problema Lyft
First: share to improve GetHuman7366588's odds
Strength in numbers! Companies respond better when others are watching.
Before contacting them, items GetHuman7366588 may need:
Nombre del titular de la cuenta, dirección de correo electrónico en la cuenta, número de teléfono en la cuenta y fecha de nacimiento
The issue in GetHuman7366588's own words
I need some help because all I wanted to do was make sure that the right I requested did not go through and instead I got sent to someplace that said it was $** to do what I need to do and I don’t wanna do anything and I don’t want to pay anything. How can I talk to a live person to make sure nothing has gone through?

GetHuman7366588 did not yet indicate what Lyft should do to make this right.

How GetHuman7366588 fixed the problem

We are waiting for GetHuman7366588 to fix the problem and share the solution with the rest of us customers.

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.
Help from Real People?
If our free tools aren't enough, we partner with a US-based company with live tech support experts available 24/7. Take advantage of a $1 one-week trial membership and chat with an expert now.
Chat with a Live Expert
¿Tienes Lyft problemas también?
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

Problema de servicio al cliente
Reported by GetHuman7366588
abr. 22º, 2022 - hace 2 meses
Not resolved
Visto por 5 clientes hasta ahora
Problema similar a 248 otros
0 clientes que siguen esto

Timeline

GetHuman7366588 comenzó a trabajar en este problema
abr. 22º 4:02pm
GetHuman7366588 indica que el problema aún no se ha solucionado.
abr. 23º 12:34am
GetHuman7366588 indica que el problema aún no se ha solucionado.
abr. 23º 3:02am