Verizon: I needed a copy of my final bill but was unable...
Una recensione del cliente Verizon da parte dell'utente GetHuman GetHuman-433735 da novembre 22º, 2017
Background on GetHuman-433735's case
GetHuman: GetHuman-433735 - can you tell our other Verizon customers when your case took place?
GetHuman-433735: Yes I can. It was afternoon, on novembre 12º.
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 GetHuman-433735 a list of common Verizon problems)
GetHuman-433735: "Find supplier" was why I was trying to call.
GetHuman-433735'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.
GetHuman-433735: I needed a copy of my final bill but was unable to log-in online since I am no longer a customer. I google searched for a VW customer service number and found this page. I am pleased with the results, thank you.
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?
GetHuman-433735: 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?
GetHuman-433735: I'd give them a five out of five on communication.
GetHuman: And what about Verizon's ability to quickly and effectively address your problem?
GetHuman-433735: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon customers?
GetHuman-433735: 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 GetHuman-433735 taken from his Verizon customer service problem that occurred on novembre 12º, 2017.