OvernightPrints.com: was on hold for * minutes before I had a live r...
A OvernightPrints.com customer review by GetHuman user ~bobkat from November 17th, 2017
Background on ~bobkat's case
GetHuman: ~bobkat - can you tell our other OvernightPrints.com customers when your case took place?
~bobkat: Yeah. It was afternoon, on November 7th.
GetHuman: Did you reach out to OvernightPrints.com, and if so, how?
GetHuman: And which of these common OvernightPrints.com customer issues best describes the reason you wanted to talk to them?
(Shows ~bobkat a list of common OvernightPrints.com problems)
~bobkat: "Warranty claim" was why I was trying to contact.
~bobkat's review of OvernightPrints.com customer service
GetHuman: So how would you sum up your experience for GetHuman's OvernightPrints.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.
~bobkat: was on hold for * minutes before I had a live response. Listened to my request, and had to have a supervisor fix the issue. That hold time was * minutes, but issue was resolved.
GetHuman: Let's quantify your experience contacting OvernightPrints.com. On a scale of 1 to 5, how easy is it go get help on a OvernightPrints.com problem?
~bobkat: 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?
~bobkat: I'd give them a two out of five on communication.
GetHuman: And what about OvernightPrints.com's ability to quickly and effectively address your problem?
~bobkat: For that I would say three out of five.
GetHuman: And finally- any advice for other OvernightPrints.com customers?
~bobkat: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for OvernightPrints.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~bobkat taken from his OvernightPrints.com customer service problem that occurred on November 7th, 2017.