Dunkin: My experience with your customer service number...
A Dunkin customer review by GetHuman user ~Fleming3601 from November 25th, 2017
Background on ~Fleming3601's case
GetHuman: ~Fleming3601 - can you tell our other Dunkin customers when your case took place?
~Fleming3601: Sure. It was morning, on November 24th.
GetHuman: Did you reach out to Dunkin, and if so, how?
GetHuman: And which of these common Dunkin customer issues best describes the reason you wanted to talk to them?
(Shows ~Fleming3601 a list of common Dunkin problems)
~Fleming3601: "Complaint" was why I was trying to call.
~Fleming3601's review of Dunkin customer service
GetHuman: So how would you sum up your experience for GetHuman's Dunkin 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.
~Fleming3601: My experience with your customer service numbers has been very poor Waited on * occasion *** minutes and more than ** on several occasions. Read several chapters in a book while waiting and checked all my email. So i am really disappointed in the customer service but not the coffee at this point.
GetHuman: Let's quantify your experience contacting Dunkin. On a scale of 1 to 5, how easy is it go get help on a Dunkin problem?
~Fleming3601: 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?
~Fleming3601: I'd give them a one out of five on communication.
GetHuman: And what about Dunkin's ability to quickly and effectively address your problem?
~Fleming3601: For that I would say one out of five.
GetHuman: And finally- any advice for other Dunkin customers?
~Fleming3601: Call them early in the day or late. Don't forget any personal or account information you might need for Dunkin to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Fleming3601 taken from his Dunkin customer service problem that occurred on November 24th, 2017.