Assurance Wireless: NO HELP WEST OF TIME BURNED MIN.THEY CALLED ME...
A Assurance Wireless customer review by GetHuman user ~OLDGUY from November 24th, 2017
Background on ~OLDGUY's case
GetHuman: ~OLDGUY - can you tell our other Assurance Wireless customers when your case took place?
~OLDGUY: Sure. It was morning, on November 22nd.
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 ~OLDGUY a list of common Assurance Wireless problems)
~OLDGUY: "Setup service" was why I was trying to call.
~OLDGUY'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.
~OLDGUY: NO HELP WEST OF TIME BURNED MIN.THEY CALLED ME THEN HAD ME CALL BACK THEN PASSED ME OFF AND HAD ME CALL OTHER NO. AFTER WAITING FOR *O MIN GOT SENT TO ANOTHER NO TO FIND THAT THEY CAN'T HELP ME EATHER .
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?
~OLDGUY: I'd give them a four 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?
~OLDGUY: I'd give them a one out of five on communication.
GetHuman: And what about Assurance Wireless's ability to quickly and effectively address your problem?
~OLDGUY: For that I would say five out of five.
GetHuman: And finally- any advice for other Assurance Wireless customers?
~OLDGUY: 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 ~OLDGUY taken from his Assurance Wireless customer service problem that occurred on November 22nd, 2017.