Quaker Oats Company: I called this number at *:** PM (MST) on a Mond...
A Quaker Oats Company customer review by GetHuman user ~nanaz2mars from November 27th, 2017
Background on ~nanaz2mars's case
GetHuman: ~nanaz2mars - can you tell our other Quaker Oats Company customers when your case took place?
~nanaz2mars: Yes. It was afternoon, on November 25th.
GetHuman: Did you reach out to Quaker Oats Company, and if so, how?
GetHuman: And which of these common Quaker Oats Company customer issues best describes the reason you wanted to talk to them?
(Shows ~nanaz2mars a list of common Quaker Oats Company problems)
~nanaz2mars: "Returns" was why I was trying to call.
~nanaz2mars's review of Quaker Oats Company customer service
GetHuman: So how would you sum up your experience for GetHuman's Quaker Oats Company 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.
~nanaz2mars: I called this number at *:** PM (MST) on a Monday. Got a recording that told me the offices were closed and to call back during normal office hours.
GetHuman: Let's quantify your experience contacting Quaker Oats Company. On a scale of 1 to 5, how easy is it go get help on a Quaker Oats Company problem?
~nanaz2mars: 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?
~nanaz2mars: I'd give them a two out of five on communication.
GetHuman: And what about Quaker Oats Company's ability to quickly and effectively address your problem?
~nanaz2mars: For that I would say five out of five.
GetHuman: And finally- any advice for other Quaker Oats Company customers?
~nanaz2mars: Call them early in the day or late. Don't forget any personal or account information you might need for Quaker Oats Company to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~nanaz2mars taken from his Quaker Oats Company customer service problem that occurred on November 25th, 2017.