SafeLink Wireless: I was able to call back gat get through to a re...
A SafeLink Wireless customer review by GetHuman user ~kac50 from November 28th, 2017
Background on ~kac50's case
GetHuman: ~kac50 - can you tell our other SafeLink Wireless customers when your case took place?
~kac50: Yup. It was morning, on November 22nd.
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 ~kac50 a list of common SafeLink Wireless problems)
~kac50: "Technical Support" was why I was trying to call.
~kac50'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.
~kac50: I was able to call back gat get through to a real person quickly- then get transferred to tech. services and resolve the problem, I made sure the woman who transferred me stayed on the phone until the tech service picked up.
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?
~kac50: 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?
~kac50: I'd give them a one out of five on communication.
GetHuman: And what about SafeLink Wireless's ability to quickly and effectively address your problem?
~kac50: For that I would say four out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~kac50: 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 ~kac50 taken from his SafeLink Wireless customer service problem that occurred on November 22nd, 2017.