SafeLink Wireless: Your company ***** ,your company needs to honor...
A SafeLink Wireless customer review by GetHuman user GetHuman-426049 from November 22nd, 2017
Background on GetHuman-426049's case
GetHuman: GetHuman-426049 - can you tell our other SafeLink Wireless customers when your case took place?
GetHuman-426049: Yes. It was morning, on November 13th.
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 GetHuman-426049 a list of common SafeLink Wireless problems)
GetHuman-426049: "Service problem" was why I was trying to call.
GetHuman-426049'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.
GetHuman-426049: Your company ***** ,your company needs to honor it's customers contracts ,not cheat them out their minutes .
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?
GetHuman-426049: 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?
GetHuman-426049: 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?
GetHuman-426049: For that I would say four out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
GetHuman-426049: 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 GetHuman-426049 taken from his SafeLink Wireless customer service problem that occurred on November 13th, 2017.