Assurance Wireless: muy buenservicio, estoy muy agradecido con el s...
A Assurance Wireless customer review by GetHuman user ~pedro Cortes from November 17th, 2017
Background on ~pedro Cortes's case
GetHuman: ~pedro Cortes - can you tell our other Assurance Wireless customers when your case took place?
~pedro Cortes: Yes. It was morning, on November 8th.
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 ~pedro Cortes a list of common Assurance Wireless problems)
~pedro Cortes: "Service problem" was why I was trying to call.
~pedro Cortes'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.
~pedro Cortes: muy buenservicio, estoy muy agradecido con el servicio gracias,piensoque todo el quelo nescesite debe solitarlo.cioheld
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?
~pedro Cortes: I'd give them a three 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?
~pedro Cortes: I'd give them a two out of five on communication.
GetHuman: And what about Assurance Wireless's ability to quickly and effectively address your problem?
~pedro Cortes: For that I would say one out of five.
GetHuman: And finally- any advice for other Assurance Wireless customers?
~pedro Cortes: 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 ~pedro Cortes taken from his Assurance Wireless customer service problem that occurred on November 8th, 2017.