SafeLink Wireless: The lady was polite but she could barely speak...
A SafeLink Wireless customer review by GetHuman user ~Diane Morton from November 20th, 2017
Background on ~Diane Morton's case
GetHuman: ~Diane Morton - can you tell our other SafeLink Wireless customers when your case took place?
~Diane Morton: Sure. It was afternoon, on November 14th.
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 ~Diane Morton a list of common SafeLink Wireless problems)
~Diane Morton: "Overcharge/Strange charge" was why I was trying to call.
~Diane Morton'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.
~Diane Morton: The lady was polite but she could barely speak English. I am an American and I speak English well so this was very frustrating.
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?
~Diane Morton: I'd give them a one 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?
~Diane Morton: 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?
~Diane Morton: For that I would say three out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~Diane Morton: 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 ~Diane Morton taken from his SafeLink Wireless customer service problem that occurred on November 14th, 2017.