Verizon: been on hold **** since before ** a.m. today...
Una recensione del cliente Verizon da parte dell'utente GetHuman GetHuman-19425 da novembre 25º, 2017
Background on GetHuman-19425's case
GetHuman: GetHuman-19425 - can you tell our other Verizon customers when your case took place?
GetHuman-19425: Yes I can. It was late at night, 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 GetHuman-19425 a list of common Verizon problems)
GetHuman-19425: "Transfer Service" was why I was trying to call.
GetHuman-19425'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-19425: been on hold **** since before ** a.m. today ** times call got dropped and im at home using a repeater they sent me...* of those drops happened mid conversation with a cust services assistant who didnt bother calling back
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-19425: 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-19425: 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?
GetHuman-19425: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon customers?
GetHuman-19425: 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-19425 taken from his Verizon customer service problem that occurred on novembre 20º, 2017.