Zazzle: They shipped me someone else's mug and now I ca...
A Zazzle customer review by GetHuman user ~wrongmug from November 19th, 2017
Background on ~wrongmug's case
GetHuman: ~wrongmug - can you tell our other Zazzle customers when your case took place?
~wrongmug: Yes I can. It was late at night, on November 15th.
GetHuman: Did you reach out to Zazzle, and if so, how?
GetHuman: And which of these common Zazzle customer issues best describes the reason you wanted to talk to them?
(Shows ~wrongmug a list of common Zazzle problems)
~wrongmug: "Return an Order" was why I was trying to call.
~wrongmug's review of Zazzle customer service
GetHuman: So how would you sum up your experience for GetHuman's Zazzle 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.
~wrongmug: They shipped me someone else's mug and now I can't get a hold of them to get it corrected. It was supposed to be a Christmas gift but now two people are disappointed. They obviously don't want to talk to their customers as there is no way they have high call volume all day. If they do that tells you something about their service.
GetHuman: Let's quantify your experience contacting Zazzle. On a scale of 1 to 5, how easy is it go get help on a Zazzle problem?
~wrongmug: 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?
~wrongmug: I'd give them a four out of five on communication.
GetHuman: And what about Zazzle's ability to quickly and effectively address your problem?
~wrongmug: For that I would say one out of five.
GetHuman: And finally- any advice for other Zazzle customers?
~wrongmug: Call them early in the day or late. Don't forget any personal or account information you might need for Zazzle to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~wrongmug taken from his Zazzle customer service problem that occurred on November 15th, 2017.