TeamExpress.com: Worse I've ever seen. You hold on for hours and...
A TeamExpress.com customer review by GetHuman user ~Caprice Landing from November 27th, 2017
Background on ~Caprice Landing's case
GetHuman: ~Caprice Landing - can you tell our other TeamExpress.com customers when your case took place?
~Caprice Landing: Yup. It was afternoon, on November 20th.
GetHuman: Did you reach out to TeamExpress.com, and if so, how?
GetHuman: And which of these common TeamExpress.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Caprice Landing a list of common TeamExpress.com problems)
~Caprice Landing: "Returns" was why I was trying to call.
~Caprice Landing's review of TeamExpress.com customer service
GetHuman: So how would you sum up your experience for GetHuman's TeamExpress.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.
~Caprice Landing: Worse I've ever seen. You hold on for hours and they still get your order wrong plus they stealing your credit card number and use it.
GetHuman: Let's quantify your experience contacting TeamExpress.com. On a scale of 1 to 5, how easy is it go get help on a TeamExpress.com problem?
~Caprice Landing: I'd give them a one 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?
~Caprice Landing: I'd give them a four out of five on communication.
GetHuman: And what about TeamExpress.com's ability to quickly and effectively address your problem?
~Caprice Landing: For that I would say one out of five.
GetHuman: And finally- any advice for other TeamExpress.com customers?
~Caprice Landing: Call them early in the day or late. Don't forget any personal or account information you might need for TeamExpress.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Caprice Landing taken from his TeamExpress.com customer service problem that occurred on November 20th, 2017.