VistaPrint: Basically they refuse to address customer servi...
A VistaPrint customer review by GetHuman user ~Margaret from November 15th, 2017
Background on ~Margaret's case
GetHuman: ~Margaret - can you tell our other VistaPrint customers when your case took place?
~Margaret: Yes. It was middle of the night, on November 8th.
GetHuman: Did you reach out to VistaPrint, and if so, how?
GetHuman: And which of these common VistaPrint customer issues best describes the reason you wanted to talk to them?
(Shows ~Margaret a list of common VistaPrint problems)
~Margaret: "Returns" was why I was trying to call.
~Margaret's review of VistaPrint customer service
GetHuman: So how would you sum up your experience for GetHuman's VistaPrint 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.
~Margaret: Basically they refuse to address customer service issues via email at all. If you email them all you get is an "automated reply" insisting that you phone their customer service department during East Coast business hours. Yuck! I'm on the West Coast and really hate wasting time on the phone!
GetHuman: Let's quantify your experience contacting VistaPrint. On a scale of 1 to 5, how easy is it go get help on a VistaPrint problem?
~Margaret: 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?
~Margaret: I'd give them a five out of five on communication.
GetHuman: And what about VistaPrint's ability to quickly and effectively address your problem?
~Margaret: For that I would say five out of five.
GetHuman: And finally- any advice for other VistaPrint customers?
~Margaret: Call them early in the day or late. Don't forget any personal or account information you might need for VistaPrint to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Margaret taken from his VistaPrint customer service problem that occurred on November 8th, 2017.