I have contacted Samsung * times now regarding...
A Samsung customer review by GetHuman user GetHuman-321513 from November 27th, 2017
Background on GetHuman-321513's case
GetHuman: GetHuman-321513 - can you tell our other Samsung customers when your case took place?
GetHuman-321513: Yup. It was evening, on November 24th.
GetHuman: Did you reach out to Samsung, and if so, how?
GetHuman: And which of these common Samsung customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-321513 a list of common Samsung problems)
GetHuman-321513: "Track an Order" was why I was trying to call.
GetHuman-321513's review of Samsung customer service
GetHuman: So how would you sum up your experience for GetHuman's Samsung 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-321513: I have contacted Samsung * times now regarding dishwasher delay timer not working. Each rep asks me to perform the same tests, none of which solve the problem, and each one says they will get back to me later, which never happens. Soon the thing will be out of warranty!
GetHuman: Let's quantify your experience contacting Samsung. On a scale of 1 to 5, how easy is it go get help on a Samsung problem?
GetHuman-321513: 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?
GetHuman-321513: I'd give them a three out of five on communication.
GetHuman: And what about Samsung's ability to quickly and effectively address your problem?
GetHuman-321513: For that I would say two out of five.
GetHuman: And finally- any advice for other Samsung customers?
GetHuman-321513: Call them early in the day or late. Don't forget any personal or account information you might need for Samsung to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-321513 taken from his Samsung customer service problem that occurred on November 24th, 2017.