Verizon FiOS: Three calls to Verizon...first one, they hung u...
A Verizon FiOS customer review by GetHuman user ~HughJohnson from November 25th, 2017
Background on ~HughJohnson's case
GetHuman: ~HughJohnson - can you tell our other Verizon FiOS customers when your case took place?
~HughJohnson: Yes. It was afternoon, on November 16th.
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 ~HughJohnson a list of common Verizon FiOS problems)
~HughJohnson: "Service Outage" was why I was trying to call.
~HughJohnson'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.
~HughJohnson: Three calls to Verizon...first one, they hung up on me before anything could be done, second one transferred me to a non-working number, third one transferred mee to "repair". Verizon does greatat hiring stupid people.
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?
~HughJohnson: 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?
~HughJohnson: 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?
~HughJohnson: For that I would say four out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
~HughJohnson: 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 ~HughJohnson taken from his Verizon FiOS customer service problem that occurred on November 16th, 2017.