Ooshirt.com: Horrible does not begin to describe! * Emails...
A Ooshirt.com customer review by GetHuman user ~pissedoff from November 21st, 2017
Background on ~pissedoff's case
GetHuman: ~pissedoff - can you tell our other Ooshirt.com customers when your case took place?
~pissedoff: Yeah. It was afternoon, on November 18th.
GetHuman: Did you reach out to Ooshirt.com, and if so, how?
GetHuman: And which of these common Ooshirt.com customer issues best describes the reason you wanted to talk to them?
(Shows ~pissedoff a list of common Ooshirt.com problems)
~pissedoff: "Change order" was why I was trying to call.
~pissedoff's review of Ooshirt.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Ooshirt.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.
~pissedoff: Horrible does not begin to describe! * Emails, no reply, * phone calls... no human answer or they just have a recording that says "we are sorry but all are busy" and then they just hang up!! Got a live chat but that was pretty much a computer reply!! UGGGHHHH!!
GetHuman: Let's quantify your experience contacting Ooshirt.com. On a scale of 1 to 5, how easy is it go get help on a Ooshirt.com problem?
~pissedoff: 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?
~pissedoff: I'd give them a two out of five on communication.
GetHuman: And what about Ooshirt.com's ability to quickly and effectively address your problem?
~pissedoff: For that I would say one out of five.
GetHuman: And finally- any advice for other Ooshirt.com customers?
~pissedoff: Call them early in the day or late. Don't forget any personal or account information you might need for Ooshirt.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~pissedoff taken from his Ooshirt.com customer service problem that occurred on November 18th, 2017.