SafeLink Wireless: after being on hold, they told me to call the r...
A SafeLink Wireless customer review by GetHuman user ~not happy from November 22nd, 2017
Background on ~not happy's case
GetHuman: ~not happy - can you tell our other SafeLink Wireless customers when your case took place?
~not happy: Yeah. It was morning, on November 16th.
GetHuman: Did you reach out to SafeLink Wireless, and if so, how?
GetHuman: And which of these common SafeLink Wireless customer issues best describes the reason you wanted to talk to them?
(Shows ~not happy a list of common SafeLink Wireless problems)
~not happy: "Check Application Status" was why I was trying to call.
~not happy's review of SafeLink Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's SafeLink Wireless 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.
~not happy: after being on hold, they told me to call the regular safelink number. I told him I had tried that number and could never get a live person and he told me toli listen
GetHuman: Let's quantify your experience contacting SafeLink Wireless. On a scale of 1 to 5, how easy is it go get help on a SafeLink Wireless problem?
~not happy: I'd give them a three 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?
~not happy: I'd give them a four out of five on communication.
GetHuman: And what about SafeLink Wireless's ability to quickly and effectively address your problem?
~not happy: For that I would say five out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~not happy: Call them early in the day or late. Don't forget any personal or account information you might need for SafeLink Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~not happy taken from his SafeLink Wireless customer service problem that occurred on November 16th, 2017.