WOW!: I was placed on hold to talk to a manager*super...
Una recensione del cliente WOW! da parte dell'utente GetHuman ~COMCAST da novembre 26º, 2017
Background on ~COMCAST's case
GetHuman: ~COMCAST - can you tell our other WOW! customers when your case took place?
~COMCAST: Yup. It was afternoon, on novembre 23º.
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 ~COMCAST a list of common WOW! problems)
~COMCAST: "Setup service" was why I was trying to call.
~COMCAST'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.
~COMCAST: I was placed on hold to talk to a manager*supervisor and then disconnected twice. I was told no managers were available and they would call me back on my cell number. they called back on my land line instead. My bill continues to go up every month. they tell me its because promotions expire. the TV service is horrible. Should have never left Comcast.
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?
~COMCAST: I'd give them a one 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?
~COMCAST: I'd give them a four out of five on communication.
GetHuman: And what about WOW!'s ability to quickly and effectively address your problem?
~COMCAST: For that I would say one out of five.
GetHuman: And finally- any advice for other WOW! customers?
~COMCAST: 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 ~COMCAST taken from his WOW! customer service problem that occurred on novembre 23º, 2017.