SafeLink Wireless: Very luck-based* some representatives do not ca...
A SafeLink Wireless customer review by GetHuman user ~Mama Luigi from November 25th, 2017
Background on ~Mama Luigi's case
GetHuman: ~Mama Luigi - can you tell our other SafeLink Wireless customers when your case took place?
~Mama Luigi: Yeah. It was afternoon, on November 16th.
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 ~Mama Luigi a list of common SafeLink Wireless problems)
~Mama Luigi: "Overcharge/Strange charge" was why I was trying to call.
~Mama Luigi'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.
~Mama Luigi: Very luck-based* some representatives do not care in the slightest and will give you the runaround, others are just fine. Not the way to run a phone service.
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?
~Mama Luigi: I'd give them a three 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?
~Mama Luigi: I'd give them a two out of five on communication.
GetHuman: And what about SafeLink Wireless's ability to quickly and effectively address your problem?
~Mama Luigi: For that I would say one out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~Mama Luigi: 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 ~Mama Luigi taken from his SafeLink Wireless customer service problem that occurred on November 16th, 2017.