Online interaction with Acedepot.com was really...
A Acedepot.com customer review by GetHuman user ~thom_clark79 from November 10th, 2017
Background on ~thom_clark79's case
GetHuman: ~thom_clark79 - can you tell our other Acedepot.com customers when your case took place?
~thom_clark79: Yes I can. It was middle of the night, on November 1st.
GetHuman: Did you reach out to Acedepot.com, and if so, how?
GetHuman: And which of these common Acedepot.com customer issues best describes the reason you wanted to talk to them?
(Shows ~thom_clark79 a list of common Acedepot.com problems)
~thom_clark79: "Cancel order" was why I was trying to call.
~thom_clark79's review of Acedepot.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Acedepot.com 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.
~thom_clark79: Online interaction with Acedepot.com was really very fine. Customer service representative was very courteous and helpful with addressing my questions and concerns. I would definitely recommend AceDepot.com.
GetHuman: Let's quantify your experience contacting Acedepot.com. On a scale of 1 to 5, how easy is it go get help on a Acedepot.com problem?
~thom_clark79: I'd give them a five 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?
~thom_clark79: I'd give them a five out of five on communication.
GetHuman: And what about Acedepot.com's ability to quickly and effectively address your problem?
~thom_clark79: For that I would say five out of five.
GetHuman: And finally- any advice for other Acedepot.com customers?
~thom_clark79: Call them early in the day or late. Don't forget any personal or account information you might need for Acedepot.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~thom_clark79 taken from his Acedepot.com customer service problem that occurred on November 1st, 2017.