Verizon FiOS: I took the steps outlined on your site, and rat...
A Verizon FiOS customer review by GetHuman user GetHuman-14749 from November 25th, 2017
Background on GetHuman-14749's case
GetHuman: GetHuman-14749 - can you tell our other Verizon FiOS customers when your case took place?
GetHuman-14749: Yes. It was middle of the night, on November 24th.
GetHuman: Did you reach out to Verizon FiOS, and if so, how?
GetHuman: And which of these common Verizon FiOS customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-14749 a list of common Verizon FiOS problems)
GetHuman-14749: "Dispute a Charge" was why I was trying to call.
GetHuman-14749's review of Verizon FiOS customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon FiOS 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-14749: I took the steps outlined on your site, and rather than get a customer representative to speak with in ** minutes, I was told it would be an hour wait. Then I was disconnected. Miserable service.
GetHuman: Let's quantify your experience contacting Verizon FiOS. On a scale of 1 to 5, how easy is it go get help on a Verizon FiOS problem?
GetHuman-14749: I'd give them a two 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-14749: I'd give them a five out of five on communication.
GetHuman: And what about Verizon FiOS's ability to quickly and effectively address your problem?
GetHuman-14749: For that I would say four out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
GetHuman-14749: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon FiOS to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-14749 taken from his Verizon FiOS customer service problem that occurred on November 24th, 2017.