Hardee's: Very disrespectful general manager
A Hardee's customer review by GetHuman user GetHuman-denhym from December 8th, 2017
Background on GetHuman-denhym's case
GetHuman: GetHuman-denhym - can you tell our other Hardee's customers when your case took place?
GetHuman-denhym: Yes I can. It was afternoon, on November 29th.
GetHuman: Did you reach out to Hardee's, and if so, how?
GetHuman: And which of these common Hardee's customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-denhym a list of common Hardee's problems)
GetHuman-denhym: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-denhym's review of Hardee's customer service
GetHuman: So how would you sum up your experience for GetHuman's Hardee's 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-denhym: Very disrespectful general manager
GetHuman: Can you tell the rest of us a bit more from what happened on 11/29/17?
GetHuman-denhym: I am an employee one of the best I been sick since last night so I called in and I was told I was fired
GetHuman: Let's quantify your experience contacting Hardee's. On a scale of 1 to 5, how easy is it go get help on a Hardee's problem?
GetHuman-denhym: 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-denhym: I'd give them a five out of five on communication.
GetHuman: And what about Hardee's's ability to quickly and effectively address your problem?
GetHuman-denhym: For that I would say four out of five.
GetHuman: And finally- any advice for other Hardee's customers?
GetHuman-denhym: Call them early in the day or late. Don't forget any personal or account information you might need for Hardee's to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-denhym taken from his Hardee's customer service problem that occurred on November 29th, 2017.