SafeLink Wireless: I submitted an email and tried to talk to a sup...
A SafeLink Wireless customer review by GetHuman user ~Linda husvar from November 14th, 2017
Background on ~Linda husvar's case
GetHuman: ~Linda husvar - can you tell our other SafeLink Wireless customers when your case took place?
~Linda husvar: Yes. It was late at night, on November 5th.
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 ~Linda husvar a list of common SafeLink Wireless problems)
~Linda husvar: "Device Support" was why I was trying to call.
~Linda husvar'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.
~Linda husvar: I submitted an email and tried to talk to a supervisor via this number. i finally reqwuested that my emails be sent to administation.
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?
~Linda husvar: I'd give them a four 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?
~Linda husvar: I'd give them a five out of five on communication.
GetHuman: And what about SafeLink Wireless's ability to quickly and effectively address your problem?
~Linda husvar: For that I would say one out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~Linda husvar: 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 ~Linda husvar taken from his SafeLink Wireless customer service problem that occurred on November 5th, 2017.