Verizon FiOS: We were in Canada when we needed to place call...
A Verizon FiOS customer review by GetHuman user ~Texan in Canada from November 25th, 2017
Background on ~Texan in Canada's case
GetHuman: ~Texan in Canada - can you tell our other Verizon FiOS customers when your case took place?
~Texan in Canada: Yes I can. It was afternoon, on November 23rd.
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 ~Texan in Canada a list of common Verizon FiOS problems)
~Texan in Canada: "Change Plan" was why I was trying to call.
~Texan in Canada'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.
~Texan in Canada: We were in Canada when we needed to place call. Verizon *** number wouldn't work, so we tried the call back service. Worked great!
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?
~Texan in Canada: I'd give them a four 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?
~Texan in Canada: 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?
~Texan in Canada: For that I would say two out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
~Texan in Canada: 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 ~Texan in Canada taken from his Verizon FiOS customer service problem that occurred on November 23rd, 2017.