WOW!: they didn't tell anyone that the number they ha...
A WOW! customer review by GetHuman user ~firstname.lastname@example.org from November 25th, 2017
Background on ~email@example.com's case
GetHuman: ~firstname.lastname@example.org - can you tell our other WOW! customers when your case took place?
~email@example.com: Yes. It was middle of the night, on November 21st.
GetHuman: Did you reach out to WOW!, and if so, how?
GetHuman: And which of these common WOW! customer issues best describes the reason you wanted to talk to them?
(Shows ~firstname.lastname@example.org a list of common WOW! problems)
~email@example.com: "Setup Service" was why I was trying to call.
~firstname.lastname@example.org's review of WOW! customer service
GetHuman: So how would you sum up your experience for GetHuman's WOW! 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.
~email@example.com: they didn't tell anyone that the number they have on the bill is now for dishnot wow. iam going to cancel today. way to much money they charge for there service.
GetHuman: Let's quantify your experience contacting WOW!. On a scale of 1 to 5, how easy is it go get help on a WOW! problem?
~firstname.lastname@example.org: I'd give them a three 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?
~email@example.com: I'd give them a two out of five on communication.
GetHuman: And what about WOW!'s ability to quickly and effectively address your problem?
~firstname.lastname@example.org: For that I would say five out of five.
GetHuman: And finally- any advice for other WOW! customers?
~email@example.com: Call them early in the day or late. Don't forget any personal or account information you might need for WOW! to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~firstname.lastname@example.org taken from his WOW! customer service problem that occurred on November 21st, 2017.