Domino's Pizza: I have ordered from dominos for years but after...
A Domino's Pizza customer review by GetHuman user ~That one guy from November 23rd, 2017
Background on ~That one guy's case
GetHuman: ~That one guy - can you tell our other Domino's Pizza customers when your case took place?
~That one guy: Yup. It was evening, on November 16th.
GetHuman: Did you reach out to Domino's Pizza, and if so, how?
GetHuman: And which of these common Domino's Pizza customer issues best describes the reason you wanted to talk to them?
(Shows ~That one guy a list of common Domino's Pizza problems)
~That one guy: "Refund a Charge" was why I was trying to call.
~That one guy's review of Domino's Pizza customer service
GetHuman: So how would you sum up your experience for GetHuman's Domino's Pizza 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.
~That one guy: I have ordered from dominos for years but after the last order I'm never ordering from them again. My food was burnt and my pizza was squashed. I regret ever ordering from dominos.
GetHuman: Let's quantify your experience contacting Domino's Pizza. On a scale of 1 to 5, how easy is it go get help on a Domino's Pizza problem?
~That one guy: 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?
~That one guy: I'd give them a one out of five on communication.
GetHuman: And what about Domino's Pizza's ability to quickly and effectively address your problem?
~That one guy: For that I would say four out of five.
GetHuman: And finally- any advice for other Domino's Pizza customers?
~That one guy: Call them early in the day or late. Don't forget any personal or account information you might need for Domino's Pizza to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~That one guy taken from his Domino's Pizza customer service problem that occurred on November 16th, 2017.