Steak and Shake: Very responsible and efficient communication...
A Steak and Shake customer review by GetHuman user GetHuman-46867 from November 24th, 2017
Background on GetHuman-46867's case
GetHuman: GetHuman-46867 - can you tell our other Steak and Shake customers when your case took place?
GetHuman-46867: Yeah. It was middle of the night, on November 19th.
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 GetHuman-46867 a list of common Steak and Shake problems)
GetHuman-46867: "Delivery problem" was why I was trying to call.
GetHuman-46867'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.
GetHuman-46867: Very responsible and efficient communication. Let's see if they can justify why they changed their large drink size from ** oz. to less than ** oz.
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?
GetHuman-46867: 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-46867: I'd give them a five out of five on communication.
GetHuman: And what about Steak and Shake's ability to quickly and effectively address your problem?
GetHuman-46867: For that I would say four out of five.
GetHuman: And finally- any advice for other Steak and Shake customers?
GetHuman-46867: 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 GetHuman-46867 taken from his Steak and Shake customer service problem that occurred on November 19th, 2017.