SafeLink Wireless: i sent in all paper work that they ask for but...
A SafeLink Wireless customer review by GetHuman user ~pat beaulieu from November 15th, 2017
Background on ~pat beaulieu's case
GetHuman: ~pat beaulieu - can you tell our other SafeLink Wireless customers when your case took place?
~pat beaulieu: Yup. It was morning, on November 7th.
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 ~pat beaulieu a list of common SafeLink Wireless problems)
~pat beaulieu: "Lower my bill" was why I was trying to call.
~pat beaulieu'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.
~pat beaulieu: i sent in all paper work that they ask for but still not good paper work was sent in three time they want ss letter. an ss num i did that too .
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?
~pat beaulieu: 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?
~pat beaulieu: 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?
~pat beaulieu: For that I would say five out of five.
GetHuman: And finally- any advice for other SafeLink Wireless customers?
~pat beaulieu: 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 ~pat beaulieu taken from his SafeLink Wireless customer service problem that occurred on November 7th, 2017.