LG Electronics: very satisfied--I wish all customer service was...
A LG Electronics customer review by GetHuman user GetHuman-210415 from October 31st, 2017
Background on GetHuman-210415's case
GetHuman: GetHuman-210415 - can you tell our other LG Electronics customers when your case took place?
GetHuman-210415: Yes I can. It was evening, on October 22nd.
GetHuman: Did you reach out to LG Electronics, and if so, how?
GetHuman: And which of these common LG Electronics customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-210415 a list of common LG Electronics problems)
GetHuman-210415: "Technical support" was why I was trying to call.
GetHuman-210415's review of LG Electronics customer service
GetHuman: So how would you sum up your experience for GetHuman's LG Electronics 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-210415: very satisfied--I wish all customer service was this good. There was a wait time of several minutes while person gathered info, but very reasonable
GetHuman: Let's quantify your experience contacting LG Electronics. On a scale of 1 to 5, how easy is it go get help on a LG Electronics problem?
GetHuman-210415: 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-210415: I'd give them a three out of five on communication.
GetHuman: And what about LG Electronics's ability to quickly and effectively address your problem?
GetHuman-210415: For that I would say one out of five.
GetHuman: And finally- any advice for other LG Electronics customers?
GetHuman-210415: Call them early in the day or late. Don't forget any personal or account information you might need for LG Electronics to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-210415 taken from his LG Electronics customer service problem that occurred on October 22nd, 2017.