SafeLink Wireless: Shocking! They gave me my account number and t...
A SafeLink Wireless customer review by GetHuman user ~daena from November 21st, 2017
Background on ~daena's case
GetHuman: ~daena - can you tell our other SafeLink Wireless customers when your case took place?
~daena: Yes I can. It was afternoon, on November 11th.
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 ~daena a list of common SafeLink Wireless problems)
~daena: "Device Support" was why I was trying to call.
~daena'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.
~daena: Shocking! They gave me my account number and told me to call tech support and then I had to wait about ** minutes but received help. My phone was never getting it's minutes so hopefully all will work fine next month.
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?
~daena: 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?
~daena: I'd give them a three out of five on communication.
GetHuman: And what about SafeLink Wireless's ability to quickly and effectively address your problem?
~daena: For that I would say two out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~daena: 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 ~daena taken from his SafeLink Wireless customer service problem that occurred on November 11th, 2017.