Assurance Wireless: They told me I did not have an assurance phone...
A Assurance Wireless customer review by GetHuman user ~Anonymous from November 23rd, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Assurance Wireless customers when your case took place?
~Anonymous: Yes. It was late at night, on November 16th.
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 ~Anonymous a list of common Assurance Wireless problems)
~Anonymous: "Technical support" was why I was trying to call.
~Anonymous'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.
~Anonymous: They told me I did not have an assurance phone because I was trying to cancel my account. They did not cancel a friends account either!!! They are a fraud.
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?
~Anonymous: I'd give them a five 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?
~Anonymous: I'd give them a five out of five on communication.
GetHuman: And what about Assurance Wireless's ability to quickly and effectively address your problem?
~Anonymous: For that I would say five out of five.
GetHuman: And finally- any advice for other Assurance Wireless customers?
~Anonymous: 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 ~Anonymous taken from his Assurance Wireless customer service problem that occurred on November 16th, 2017.