Kraft Foods: There was no communication - unless you call an...
A Kraft Foods customer review by GetHuman user GetHuman-83042 from November 28th, 2017
Background on GetHuman-83042's case
GetHuman: GetHuman-83042 - can you tell our other Kraft Foods customers when your case took place?
GetHuman-83042: Yeah. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Kraft Foods, and if so, how?
GetHuman: And which of these common Kraft Foods customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-83042 a list of common Kraft Foods problems)
GetHuman-83042: "Complaint" was why I was trying to call.
GetHuman-83042's review of Kraft Foods customer service
GetHuman: So how would you sum up your experience for GetHuman's Kraft Foods 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.
GetHuman-83042: There was no communication - unless you call an automated message communication. Nobody picked up the phone* message said "all representatives are busy, please continue to hold," but that never happened.
GetHuman: Let's quantify your experience contacting Kraft Foods. On a scale of 1 to 5, how easy is it go get help on a Kraft Foods problem?
GetHuman-83042: 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?
GetHuman-83042: I'd give them a one out of five on communication.
GetHuman: And what about Kraft Foods's ability to quickly and effectively address your problem?
GetHuman-83042: For that I would say two out of five.
GetHuman: And finally- any advice for other Kraft Foods customers?
GetHuman-83042: Call them early in the day or late. Don't forget any personal or account information you might need for Kraft Foods to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-83042 taken from his Kraft Foods customer service problem that occurred on November 19th, 2017.