Domino's Pizza: I just called in a to go order the guy was very...
A Domino's Pizza customer review by GetHuman user GetHuman-409891 from November 25th, 2017
Background on GetHuman-409891's case
GetHuman: GetHuman-409891 - can you tell our other Domino's Pizza customers when your case took place?
GetHuman-409891: Sure. It was morning, on November 17th.
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 GetHuman-409891 a list of common Domino's Pizza problems)
GetHuman-409891: "Refund a Charge" was why I was trying to call.
GetHuman-409891'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.
GetHuman-409891: I just called in a to go order the guy was very mean when i wanted to specify how I wanted it and he got nasty with me by taking deep breaths like ugh.
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?
GetHuman-409891: 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?
GetHuman-409891: I'd give them a three out of five on communication.
GetHuman: And what about Domino's Pizza's ability to quickly and effectively address your problem?
GetHuman-409891: For that I would say one out of five.
GetHuman: And finally- any advice for other Domino's Pizza customers?
GetHuman-409891: 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 GetHuman-409891 taken from his Domino's Pizza customer service problem that occurred on November 17th, 2017.