my safelink phone was burnt in a fire. i have c...
A SafeLink customer review by GetHuman user ~irvbow from November 24th, 2017
Background on ~irvbow's case
GetHuman: ~irvbow - can you tell our other SafeLink customers when your case took place?
~irvbow: Yeah. It was morning, on November 16th.
GetHuman: Did you reach out to SafeLink, and if so, how?
GetHuman: And which of these common SafeLink customer issues best describes the reason you wanted to talk to them?
(Shows ~irvbow a list of common SafeLink problems)
~irvbow: "Change plan" was why I was trying to call.
~irvbow's review of SafeLink customer service
GetHuman: So how would you sum up your experience for GetHuman's SafeLink customer community? We'll censor any IDs, numbers, or codes and any inappropriate words here out of respect to the millions of other customers using this resource.
~irvbow: my safelink phone was burnt in a fire. i have called *-***-***-**** * times and still got no where, and also can not understand the people because of there english very poor gov. run buisness. I need my phone replaced there telling me to make * call a month i can not do this my phone is a pile of plastic, I can be reached at *****@***.com E-mail.
GetHuman: Let's quantify your experience contacting SafeLink. On a scale of 1 to 5, how easy is it go get help on a SafeLink problem?
~irvbow: I'd give them a two out of five for ease of finding your way to help.
GetHuman: What about quality of communication. How would you rate that on a 1 to 5 scale?
~irvbow: I'd give them a three out of five on communication.
GetHuman: And what about SafeLink's ability to quickly and effectively address your problem?
~irvbow: For that I would say one out of five.
GetHuman: And finally- any advice for other SafeLink customers?
~irvbow: Call them early in the day or late. Don't forget any personal or account information you might need for SafeLink to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~irvbow taken from his SafeLink customer service problem that occurred on November 16th, 2017.