Dairy Queen: I guess I am the lucky one. Didn't have a long...
A Dairy Queen customer review by GetHuman user ~kryssya from November 17th, 2017
Background on ~kryssya's case
GetHuman: ~kryssya - can you tell our other Dairy Queen customers when your case took place?
~kryssya: Yes I can. It was afternoon, on November 14th.
GetHuman: Did you reach out to Dairy Queen, and if so, how?
GetHuman: And which of these common Dairy Queen customer issues best describes the reason you wanted to talk to them?
(Shows ~kryssya a list of common Dairy Queen problems)
~kryssya: "Overcharge/Strange charge" was why I was trying to call.
~kryssya's review of Dairy Queen customer service
GetHuman: So how would you sum up your experience for GetHuman's Dairy Queen 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.
~kryssya: I guess I am the lucky one. Didn't have a long wait time also, the rep whom I spoke with was fine. My only issue is this: If you are calling customer service to complain about your experience, an apology would be nice. My rep took my info and that's about it
GetHuman: Let's quantify your experience contacting Dairy Queen. On a scale of 1 to 5, how easy is it go get help on a Dairy Queen problem?
~kryssya: 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?
~kryssya: I'd give them a three out of five on communication.
GetHuman: And what about Dairy Queen's ability to quickly and effectively address your problem?
~kryssya: For that I would say two out of five.
GetHuman: And finally- any advice for other Dairy Queen customers?
~kryssya: Call them early in the day or late. Don't forget any personal or account information you might need for Dairy Queen to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~kryssya taken from his Dairy Queen customer service problem that occurred on November 14th, 2017.