Asurion: Finally getting to talk to a person was key. W...
A Asurion customer review by GetHuman user ~Tom A from November 22nd, 2017
Background on ~Tom A's case
GetHuman: ~Tom A - can you tell our other Asurion customers when your case took place?
~Tom A: Yes I can. It was morning, on November 13th.
GetHuman: Did you reach out to Asurion, and if so, how?
GetHuman: And which of these common Asurion customer issues best describes the reason you wanted to talk to them?
(Shows ~Tom A a list of common Asurion problems)
~Tom A: "Complaint" was why I was trying to call.
~Tom A's review of Asurion customer service
GetHuman: So how would you sum up your experience for GetHuman's Asurion 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.
~Tom A: Finally getting to talk to a person was key. Website kept asking for my cell number, but the cell number was not correct as someone entered in a claim for cell phone replacement using my number, but the claim number was from different cell provider. So website was not going to work as had to enter cell number and then it took to service provider (which was the wrong one).
GetHuman: Let's quantify your experience contacting Asurion. On a scale of 1 to 5, how easy is it go get help on a Asurion problem?
~Tom A: 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?
~Tom A: I'd give them a five out of five on communication.
GetHuman: And what about Asurion's ability to quickly and effectively address your problem?
~Tom A: For that I would say four out of five.
GetHuman: And finally- any advice for other Asurion customers?
~Tom A: Call them early in the day or late. Don't forget any personal or account information you might need for Asurion to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Tom A taken from his Asurion customer service problem that occurred on November 13th, 2017.