Verizon: Represenative was rude, and cranky about the bi...
Una recensione del cliente Verizon da parte dell'utente GetHuman ~rivmic29 da novembre 27º, 2017
Background on ~rivmic29's case
GetHuman: ~rivmic29 - can you tell our other Verizon customers when your case took place?
~rivmic29: Yes. It was afternoon, on novembre 20º.
GetHuman: Did you reach out to Verizon, and if so, how?
GetHuman: And which of these common Verizon customer issues best describes the reason you wanted to talk to them?
(Shows ~rivmic29 a list of common Verizon problems)
~rivmic29: "Overcharge/Strange charge" was why I was trying to call.
~rivmic29's review of Verizon customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon 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.
~rivmic29: Represenative was rude, and cranky about the bill matrix fee of $*.** instead that money being applied to the bill,I just looked at this post it was very faster to get through. Thanks so much maybe next time I will have a better person with a better attitude he was a total blow head.
GetHuman: Let's quantify your experience contacting Verizon. On a scale of 1 to 5, how easy is it go get help on a Verizon problem?
~rivmic29: I'd give them a five 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?
~rivmic29: I'd give them a two out of five on communication.
GetHuman: And what about Verizon's ability to quickly and effectively address your problem?
~rivmic29: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon customers?
~rivmic29: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Verizon sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~rivmic29 taken from his Verizon customer service problem that occurred on novembre 20º, 2017.