Avanquest: took a long time to reset Power Desk * S*N afte...
A Avanquest customer review by GetHuman user GetHuman-245629 from November 19th, 2017
Background on GetHuman-245629's case
GetHuman: GetHuman-245629 - can you tell our other Avanquest customers when your case took place?
GetHuman-245629: Yes. It was afternoon, on November 15th.
GetHuman: Did you reach out to Avanquest, and if so, how?
GetHuman: And which of these common Avanquest customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-245629 a list of common Avanquest problems)
GetHuman-245629: "None of those really matches why I wanted to call Avanquest that day." was why I was trying to call.
GetHuman-245629's review of Avanquest customer service
GetHuman: So how would you sum up your experience for GetHuman's Avanquest 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-245629: took a long time to reset Power Desk * S*N after reinstalling OS but they did get it done. Avanquest should be retained by the NSA the way they guard their activation codes!
GetHuman: Let's quantify your experience contacting Avanquest. On a scale of 1 to 5, how easy is it go get help on a Avanquest problem?
GetHuman-245629: 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?
GetHuman-245629: I'd give them a two out of five on communication.
GetHuman: And what about Avanquest's ability to quickly and effectively address your problem?
GetHuman-245629: For that I would say three out of five.
GetHuman: And finally- any advice for other Avanquest customers?
GetHuman-245629: Call them early in the day or late. Don't forget any personal or account information you might need for Avanquest to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-245629 taken from his Avanquest customer service problem that occurred on November 15th, 2017.