Verizon FiOS: Called to cancel service prior to installation...
A Verizon FiOS customer review by GetHuman user ~Mac Nanimous from November 25th, 2017
Background on ~Mac Nanimous's case
GetHuman: ~Mac Nanimous - can you tell our other Verizon FiOS customers when your case took place?
~Mac Nanimous: Yup. It was morning, on November 20th.
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 ~Mac Nanimous a list of common Verizon FiOS problems)
~Mac Nanimous: "Cancel service" was why I was trying to call.
~Mac Nanimous'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.
~Mac Nanimous: Called to cancel service prior to installation, waited ** minutes and hung up. Called again ** minutes later was able to cancel. Their service supported my decision not to go with Verizon, price is not everything
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?
~Mac Nanimous: I'd give them a one 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?
~Mac Nanimous: I'd give them a one out of five on communication.
GetHuman: And what about Verizon FiOS's ability to quickly and effectively address your problem?
~Mac Nanimous: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
~Mac Nanimous: 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 ~Mac Nanimous taken from his Verizon FiOS customer service problem that occurred on November 20th, 2017.