SafeLink Wireless: Phone service is awful always poor reception...
A SafeLink Wireless customer review by GetHuman user ~robert feldman from November 15th, 2017
Background on ~robert feldman's case
GetHuman: ~robert feldman - can you tell our other SafeLink Wireless customers when your case took place?
~robert feldman: Yes. It was evening, on November 9th.
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 ~robert feldman a list of common SafeLink Wireless problems)
~robert feldman: "Technical Support" was why I was trying to call.
~robert feldman'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.
~robert feldman: Phone service is awful always poor reception must go outside most times always om "roam" no speakerphone option im hearing impaired
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?
~robert feldman: I'd give them a two 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?
~robert feldman: 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?
~robert feldman: For that I would say one out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~robert feldman: 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 ~robert feldman taken from his SafeLink Wireless customer service problem that occurred on November 9th, 2017.