Printerpix: on order paper below they write:*"Email:contact...
A Printerpix customer review by GetHuman user ~kiL from November 25th, 2017
Background on ~kiL's case
GetHuman: ~kiL - can you tell our other Printerpix customers when your case took place?
~kiL: Yes I can. It was evening, on November 19th.
GetHuman: Did you reach out to Printerpix, and if so, how?
GetHuman: And which of these common Printerpix customer issues best describes the reason you wanted to talk to them?
(Shows ~kiL a list of common Printerpix problems)
~kiL: "Track order" was why I was trying to contact.
~kiL's review of Printerpix customer service
GetHuman: So how would you sum up your experience for GetHuman's Printerpix 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.
~kiL: on order paper below they write:*"Email:contactus@PrinterPix.com ******* Customer services: **** *** ****" don't believed, it totally didn't work. fux*, even phone:***-***-**** it cut out by itself, and I call again again....*Finally on it, but waited ** mins. you better have time to wait, not everytime is same. thanks gethuman help.
GetHuman: Let's quantify your experience contacting Printerpix. On a scale of 1 to 5, how easy is it go get help on a Printerpix problem?
~kiL: 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?
~kiL: I'd give them a three out of five on communication.
GetHuman: And what about Printerpix's ability to quickly and effectively address your problem?
~kiL: For that I would say two out of five.
GetHuman: And finally- any advice for other Printerpix customers?
~kiL: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Printerpix to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~kiL taken from his Printerpix customer service problem that occurred on November 19th, 2017.