Verizon: Customer service patched me over to a number th...
Una recensione del cliente Verizon da parte dell'utente GetHuman GetHuman-223163 da novembre 25º, 2017
Background on GetHuman-223163's case
GetHuman: GetHuman-223163 - can you tell our other Verizon customers when your case took place?
GetHuman-223163: Yup. It was afternoon, on novembre 18º.
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-223163 a list of common Verizon problems)
GetHuman-223163: "Lower my bill" was why I was trying to call.
GetHuman-223163'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-223163: Customer service patched me over to a number that was supposed to have tech support after I waited on the line for **Min. Then when auto service said state your problem. I said unlock cell phone the thing ended the CALL.
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-223163: 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?
GetHuman-223163: 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-223163: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon customers?
GetHuman-223163: 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-223163 taken from his Verizon customer service problem that occurred on novembre 18º, 2017.