The phone got a little wet and now the screen is messed up

GetHuman819760's customer service issue with SafeLink from June 2018

1 view
 | 
3112 similar
 | 
0 following
Help with my SafeLink issue
First: share to improve GetHuman819760's odds
Strength in numbers! Companies respond better when others are watching.
GetHuman819760's next move: talk to SafeLink when they open (we'll send a reminder).
SafeLink's call center is closed now. We will text or email GetHuman819760 when they open and confirm it's a good time for a rep to call. In the meantime, read below to see how other customers resolved the same issue. Many customers describe what they said and did so that other customers like GetHuman819760 can follow if useful. Now is a good time to read up on techniques that worked to resolve the issue quickly and effectively.
Before contacting them, items GetHuman819760 may need:
Phone number, Address on account, and Name on account
The issue in GetHuman819760's own words
The problem: The phone got a little wet and now the screen is messed up
GetHuman819760 did not yet indicate what SafeLink should do to make this right.
I have an issue with SafeLink too
How GetHuman819760 fixed the problem
We are waiting for GetHuman819760 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 SafeLink's attention and get better help faster. Tap below to get started.
Having SafeLink issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
How would SafeLink email you?
This email address isn't valid
Follow this issue
See how GetHuman819760 fixes it.
This email address isn't valid

SafeLink

Customer service issue
Reported by GetHuman819760
Jun 26th, 2018 - 4 mons ago
I have an issue with SafeLink too
Not resolved
Seen by 1 customer so far
Similar issue to 3112 others
0 customers following this
Follow this issue to see how it gets fixed
Timeline
GetHuman819760 started working on this issue
Jun 26th 2:13am