Steak and Shake: We visited this resturant in aurora,il. We wait...
A Steak and Shake customer review by GetHuman user ~Shirley from November 28th, 2017
Background on ~Shirley's case
GetHuman: ~Shirley - can you tell our other Steak and Shake customers when your case took place?
~Shirley: Yes I can. It was evening, on November 26th.
GetHuman: Did you reach out to Steak and Shake, and if so, how?
GetHuman: And which of these common Steak and Shake customer issues best describes the reason you wanted to talk to them?
(Shows ~Shirley a list of common Steak and Shake problems)
~Shirley: "Overcharge/Strange charge" was why I was trying to call.
~Shirley's review of Steak and Shake customer service
GetHuman: So how would you sum up your experience for GetHuman's Steak and Shake 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.
~Shirley: We visited this resturant in aurora,il. We waited **min for our meal, burger was cold, resurant stink,seats were nasty with food behind cushion in seats, resturant needed, cleaning, service was terrible, will no return
GetHuman: Let's quantify your experience contacting Steak and Shake. On a scale of 1 to 5, how easy is it go get help on a Steak and Shake problem?
~Shirley: 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?
~Shirley: I'd give them a three out of five on communication.
GetHuman: And what about Steak and Shake's ability to quickly and effectively address your problem?
~Shirley: For that I would say four out of five.
GetHuman: And finally- any advice for other Steak and Shake customers?
~Shirley: Call them early in the day or late. Don't forget any personal or account information you might need for Steak and Shake to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Shirley taken from his Steak and Shake customer service problem that occurred on November 26th, 2017.