WOW!: Worst customer service ever, service ***** and...
WOW! Ulasan pelanggan oleh pengguna GetHuman GetHuman1143 dari Disember 1, 2017
Background on GetHuman1143's case
GetHuman: GetHuman1143 - can you tell our other WOW! customers when your case took place?
GetHuman1143: Yes. It was morning, on November 25.
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 GetHuman1143 a list of common WOW! problems)
GetHuman1143: "Technical and Service Support" was why I was trying to call.
GetHuman1143'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.
GetHuman1143: Worst customer service ever, service ***** and very expensive with low quality..... *Changing to a different cable company.
GetHuman: Can you tell the rest of us a bit more from what happened on 11/25/17?
GetHuman1143: Customer service representative was very rude, he sounded like he did not care..never again...!
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?
GetHuman1143: I'd give them a two 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?
GetHuman1143: I'd give them a one out of five on communication.
GetHuman: And what about WOW!'s ability to quickly and effectively address your problem?
GetHuman1143: For that I would say one out of five.
GetHuman: And finally- any advice for other WOW! customers?
GetHuman1143: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk WOW! mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman1143 taken from his WOW! customer service problem that occurred on November 25, 2017.