Assurance Wireless: I HAD A GREAT GUY NAMED ALLESON WHO HELPED ME...
Una recensione del cliente Assurance Wireless da parte dell'utente GetHuman ~LEE DEE da novembre 26º, 2017
Background on ~LEE DEE's case
GetHuman: ~LEE DEE - can you tell our other Assurance Wireless customers when your case took place?
~LEE DEE: Yeah. It was middle of the night, on novembre 20º.
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 ~LEE DEE a list of common Assurance Wireless problems)
~LEE DEE: "Lower my bill" was why I was trying to call.
~LEE DEE'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.
~LEE DEE: I HAD A GREAT GUY NAMED ALLESON WHO HELPED ME. I HAD A PROBLEM WITH A TEXT I KEPT GETTING. IT WAS THE NUMBERS ****.HE STOPPED THE PROBLEM. THANK YOU, ALLESON
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?
~LEE DEE: 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?
~LEE DEE: 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?
~LEE DEE: For that I would say two out of five.
GetHuman: And finally- any advice for other Assurance Wireless customers?
~LEE DEE: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Assurance Wireless sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~LEE DEE taken from his Assurance Wireless customer service problem that occurred on novembre 20º, 2017.