Asurion: The rep I talked to on the phone April *th took...
A Asurion customer review by GetHuman user ~Randye30 from November 27th, 2017
Background on ~Randye30's case
GetHuman: ~Randye30 - can you tell our other Asurion customers when your case took place?
~Randye30: Yeah. It was late at night, on November 18th.
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 ~Randye30 a list of common Asurion problems)
~Randye30: "Repairs" was why I was trying to call.
~Randye30'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.
~Randye30: The rep I talked to on the phone April *th took all the information for the claim. Told me I would get an email I could track it and the email was to do the claim all over again so I wont get a replacement phone until the **th or **th and this one is barely usable. Very unsatisfied. Maybe the reason Sprint is switching.
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?
~Randye30: 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?
~Randye30: I'd give them a one out of five on communication.
GetHuman: And what about Asurion's ability to quickly and effectively address your problem?
~Randye30: For that I would say two out of five.
GetHuman: And finally- any advice for other Asurion customers?
~Randye30: 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 ~Randye30 taken from his Asurion customer service problem that occurred on November 18th, 2017.