WOW!: I spoke with a supervisor that claims charges w...
Una recensione del cliente WOW! da parte dell'utente GetHuman ~Irene da novembre 24º, 2017
Background on ~Irene's case
GetHuman: ~Irene - can you tell our other WOW! customers when your case took place?
~Irene: Yeah. It was afternoon, on novembre 15º.
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 ~Irene a list of common WOW! problems)
~Irene: "Lower my bill" was why I was trying to call.
~Irene'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.
~Irene: I spoke with a supervisor that claims charges were approved by me which is false. My daughter was in the hospital and I have documatation to prove I was there for * days. How ignorant are these people!!!! She told me my charges can't be reversed because someone NOT ME or MY HUSBAND knew the last * digits of my SS*. Still waiting for them to call me back. WATCH YOUR BILLS!!!!
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?
~Irene: 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?
~Irene: I'd give them a five out of five on communication.
GetHuman: And what about WOW!'s ability to quickly and effectively address your problem?
~Irene: For that I would say four out of five.
GetHuman: And finally- any advice for other WOW! customers?
~Irene: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per WOW! sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~Irene taken from his WOW! customer service problem that occurred on novembre 15º, 2017.