I lost my phone in a lyft car last night

GetHuman1273655's customer service issue with Lyft from October 2018

5 views
 | 
25033 similar
 | 
0 following
Help with my Lyft issue
First: share to improve GetHuman1273655's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman1273655's next move: go to the Lyft help center.
Lyft doesn't have a customer phone number that is answered by an agent. Instead, GetHuman1273655 will want to follow the link below to head to their help center. We will check on GetHuman1273655 later to make sure it's all set or try to help escalate.
Before contacting them, items GetHuman1273655 may need:
Account holder name, Email address on account, Phone number on account, and Date of birth
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 GetHuman1273655's own words
The problem: I lost my phone in a lyft car last night
GetHuman1273655 did not yet indicate what Lyft should do to make this right.
I have an issue with Lyft too
How GetHuman1273655 fixed the problem
We are waiting for GetHuman1273655 to fix the problem and share the solution with the rest of us customers.
Follow this to see how it gets fixed
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
Follow this issue
See how GetHuman1273655 fixes it.
This email address isn't valid

Lyft

Customer service issue
Reported by GetHuman1273655
Oct 6th, 2018 - 2 mons ago
I have an issue with Lyft too
Not resolved
Seen by 5 customers so far
Similar issue to 25033 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman1273655 started working on this issue
Oct 6th 1:48pm