The Weather Channel: Constantly busy. I wanted to suggest that they...
A The Weather Channel customer review by GetHuman user ~LMorrison from November 27th, 2017
Background on ~LMorrison's case
GetHuman: ~LMorrison - can you tell our other The Weather Channel customers when your case took place?
~LMorrison: Yes. It was morning, on November 23rd.
GetHuman: Did you reach out to The Weather Channel, and if so, how?
GetHuman: And which of these common The Weather Channel customer issues best describes the reason you wanted to talk to them?
(Shows ~LMorrison a list of common The Weather Channel problems)
~LMorrison: "Service problem" was why I was trying to contact.
~LMorrison's review of The Weather Channel customer service
GetHuman: So how would you sum up your experience for GetHuman's The Weather Channel 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.
~LMorrison: Constantly busy. I wanted to suggest that they place the date of the broadcast on the video. It's hard to know if the threat is current or old news.
GetHuman: Let's quantify your experience contacting The Weather Channel. On a scale of 1 to 5, how easy is it go get help on a The Weather Channel problem?
~LMorrison: 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?
~LMorrison: I'd give them a one out of five on communication.
GetHuman: And what about The Weather Channel's ability to quickly and effectively address your problem?
~LMorrison: For that I would say two out of five.
GetHuman: And finally- any advice for other The Weather Channel customers?
~LMorrison: Call them early in the day or late. Don't forget any personal or account information you might need for The Weather Channel to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~LMorrison taken from his The Weather Channel customer service problem that occurred on November 23rd, 2017.