Checkers: We waited for about * min on the drive Thursday...
A Checkers customer review by GetHuman user ~Nash8288@aol.com from November 26th, 2017
Background on ~Nash8288@aol.com's case
GetHuman: ~Nash8288@aol.com - can you tell our other Checkers customers when your case took place?
~Nash8288@aol.com: Yup. It was late at night, on November 21st.
GetHuman: Did you reach out to Checkers, and if so, how?
GetHuman: And which of these common Checkers customer issues best describes the reason you wanted to talk to them?
(Shows ~Nash8288@aol.com a list of common Checkers problems)
~Nash8288@aol.com: "Cancel a reservation" was why I was trying to call.
~Nash8288@aol.com's review of Checkers customer service
GetHuman: So how would you sum up your experience for GetHuman's Checkers 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.
~Nash8288@aol.com: We waited for about * min on the drive Thursday only for a worker to tell us they were closed it was only *:** a.m. But your sign states, u close at *:** a.m. On Thursday. It would of been ok if the worker was polite.
GetHuman: Let's quantify your experience contacting Checkers. On a scale of 1 to 5, how easy is it go get help on a Checkers problem?
~Nash8288@aol.com: I'd give them a two 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?
~Nash8288@aol.com: I'd give them a three out of five on communication.
GetHuman: And what about Checkers's ability to quickly and effectively address your problem?
~Nash8288@aol.com: For that I would say two out of five.
GetHuman: And finally- any advice for other Checkers customers?
~Nash8288@aol.com: Call them early in the day or late. Don't forget any personal or account information you might need for Checkers to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Nash8288@aol.com taken from his Checkers customer service problem that occurred on November 21st, 2017.