Brinkmann Corporation: I was expecting a long delay and starting to ge...
A Brinkmann Corporation customer review by GetHuman user ~Jason from November 16th, 2017
Background on ~Jason's case
GetHuman: ~Jason - can you tell our other Brinkmann Corporation customers when your case took place?
~Jason: Yes. It was morning, on November 8th.
GetHuman: Did you reach out to Brinkmann Corporation, and if so, how?
GetHuman: And which of these common Brinkmann Corporation customer issues best describes the reason you wanted to talk to them?
(Shows ~Jason a list of common Brinkmann Corporation problems)
~Jason: "Where to buy" was why I was trying to call.
~Jason's review of Brinkmann Corporation customer service
GetHuman: So how would you sum up your experience for GetHuman's Brinkmann Corporation 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.
~Jason: I was expecting a long delay and starting to get angry, then they called me * minutes after I filled out the form! and had excellent customer service! a nice surprise
GetHuman: Let's quantify your experience contacting Brinkmann Corporation. On a scale of 1 to 5, how easy is it go get help on a Brinkmann Corporation problem?
~Jason: I'd give them a one 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?
~Jason: I'd give them a four out of five on communication.
GetHuman: And what about Brinkmann Corporation's ability to quickly and effectively address your problem?
~Jason: For that I would say three out of five.
GetHuman: And finally- any advice for other Brinkmann Corporation customers?
~Jason: Call them early in the day or late. Don't forget any personal or account information you might need for Brinkmann Corporation to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Jason taken from his Brinkmann Corporation customer service problem that occurred on November 8th, 2017.