CafePress: I was told to use the website as they were not...
A CafePress customer review by GetHuman user GetHuman-190384 from November 19th, 2017
Background on GetHuman-190384's case
GetHuman: GetHuman-190384 - can you tell our other CafePress customers when your case took place?
GetHuman-190384: Yes. It was middle of the night, on November 17th.
GetHuman: Did you reach out to CafePress, and if so, how?
GetHuman: And which of these common CafePress customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-190384 a list of common CafePress problems)
GetHuman-190384: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-190384's review of CafePress customer service
GetHuman: So how would you sum up your experience for GetHuman's CafePress 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-190384: I was told to use the website as they were not answering phones. I need help NOW! They have no record of my customer order, which I received due to an error in my original order. I need these items NOW*.!
GetHuman: Let's quantify your experience contacting CafePress. On a scale of 1 to 5, how easy is it go get help on a CafePress problem?
GetHuman-190384: I'd give them a four 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-190384: I'd give them a five out of five on communication.
GetHuman: And what about CafePress's ability to quickly and effectively address your problem?
GetHuman-190384: For that I would say five out of five.
GetHuman: And finally- any advice for other CafePress customers?
GetHuman-190384: Call them early in the day or late. Don't forget any personal or account information you might need for CafePress to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-190384 taken from his CafePress customer service problem that occurred on November 17th, 2017.