Office Depot: agent didn't understand my problem and passed m...
A Office Depot customer review by GetHuman user ~arlene joy from November 11th, 2017
Background on ~arlene joy's case
GetHuman: ~arlene joy - can you tell our other Office Depot customers when your case took place?
~arlene joy: Yes I can. It was afternoon, on November 2nd.
GetHuman: Did you reach out to Office Depot, and if so, how?
GetHuman: And which of these common Office Depot customer issues best describes the reason you wanted to talk to them?
(Shows ~arlene joy a list of common Office Depot problems)
~arlene joy: "Change order" was why I was trying to call.
~arlene joy's review of Office Depot customer service
GetHuman: So how would you sum up your experience for GetHuman's Office Depot 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.
~arlene joy: agent didn't understand my problem and passed me on to her supervisor who tried to resolve the problem by calling the store in question.*It will partly satisfy me but I will have to consider if I want to shop at Office Depot again
GetHuman: Let's quantify your experience contacting Office Depot. On a scale of 1 to 5, how easy is it go get help on a Office Depot problem?
~arlene joy: I'd give them a three 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?
~arlene joy: I'd give them a two out of five on communication.
GetHuman: And what about Office Depot's ability to quickly and effectively address your problem?
~arlene joy: For that I would say one out of five.
GetHuman: And finally- any advice for other Office Depot customers?
~arlene joy: Call them early in the day or late. Don't forget any personal or account information you might need for Office Depot to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~arlene joy taken from his Office Depot customer service problem that occurred on November 2nd, 2017.