I have tried to get Assurance Wireless forr som...
A Assurance Wireless customer review by GetHuman user ~jim from November 16th, 2017
Background on ~jim's case
GetHuman: ~jim - can you tell our other Assurance Wireless customers when your case took place?
~jim: Yeah. It was middle of the night, on November 9th.
GetHuman: Did you reach out to Assurance Wireless, and if so, how?
GetHuman: And which of these common Assurance Wireless customer issues best describes the reason you wanted to talk to them?
(Shows ~jim a list of common Assurance Wireless problems)
~jim: "Lower my bill" was why I was trying to call.
~jim's review of Assurance Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Assurance 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.
~jim: I have tried to get Assurance Wireless forr some time now.... I always get someone on the phone who claims the problem is solved.... and the problem is not solved...If they were a pay service I think they would have been out of business long ago...
GetHuman: Let's quantify your experience contacting Assurance Wireless. On a scale of 1 to 5, how easy is it go get help on a Assurance Wireless problem?
~jim: 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?
~jim: I'd give them a three out of five on communication.
GetHuman: And what about Assurance Wireless's ability to quickly and effectively address your problem?
~jim: For that I would say five out of five.
GetHuman: And finally- any advice for other Assurance Wireless customers?
~jim: Call them early in the day or late. Don't forget any personal or account information you might need for Assurance Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jim taken from his Assurance Wireless customer service problem that occurred on November 9th, 2017.