OfficeMax: I SPENT SEVEN HOURS TRYING TO TALK TO A CSR AND...
A OfficeMax customer review by GetHuman user ~MAD MATT from November 8th, 2017
Background on ~MAD MATT's case
GetHuman: ~MAD MATT - can you tell our other OfficeMax customers when your case took place?
~MAD MATT: Yeah. It was afternoon, on October 30th.
GetHuman: Did you reach out to OfficeMax, and if so, how?
GetHuman: And which of these common OfficeMax customer issues best describes the reason you wanted to talk to them?
(Shows ~MAD MATT a list of common OfficeMax problems)
~MAD MATT: "Change order" was why I was trying to call.
~MAD MATT's review of OfficeMax customer service
GetHuman: So how would you sum up your experience for GetHuman's OfficeMax 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.
~MAD MATT: I SPENT SEVEN HOURS TRYING TO TALK TO A CSR AND NEVER HAD A CALL ANSWERED! I WAS ** YEAR REGULAR CUSTOMER. I THINK IT IS TME TO GO TO STAPLES FRM NOW ON. THERE IS ASOLUTELY NO REASON FOR NOT SERVING CLIENTS. IN ADDITION, I SENT * E-MAILS THROUGH MAXPERKS IN THE PAST MONTH AND NEVER WAS SENT ANY REPLIES!
GetHuman: Let's quantify your experience contacting OfficeMax. On a scale of 1 to 5, how easy is it go get help on a OfficeMax problem?
~MAD MATT: 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?
~MAD MATT: I'd give them a one out of five on communication.
GetHuman: And what about OfficeMax's ability to quickly and effectively address your problem?
~MAD MATT: For that I would say two out of five.
GetHuman: And finally- any advice for other OfficeMax customers?
~MAD MATT: Call them early in the day or late. Don't forget any personal or account information you might need for OfficeMax to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~MAD MATT taken from his OfficeMax customer service problem that occurred on October 30th, 2017.