Asurion: Horrible service, They sent my phone * times an...
A Asurion customer review by GetHuman user GetHuman-428304 from November 23rd, 2017
Background on GetHuman-428304's case
GetHuman: GetHuman-428304 - can you tell our other Asurion customers when your case took place?
GetHuman-428304: Yes. It was middle of the night, on November 19th.
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 GetHuman-428304 a list of common Asurion problems)
GetHuman-428304: "Problem with a claim" was why I was trying to call.
GetHuman-428304'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.
GetHuman-428304: Horrible service, They sent my phone * times and it was still never delievered they still charged me a deductible and I never received a phone. NO one followed up ever. When I finally made it through to a representative they hung up on me.
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?
GetHuman-428304: 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?
GetHuman-428304: I'd give them a three out of five on communication.
GetHuman: And what about Asurion's ability to quickly and effectively address your problem?
GetHuman-428304: For that I would say five out of five.
GetHuman: And finally- any advice for other Asurion customers?
GetHuman-428304: 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 GetHuman-428304 taken from his Asurion customer service problem that occurred on November 19th, 2017.