Verizon FiOS: We were in Canada when we needed to place call...
Verizon FiOS отзыв клиента от пользователя GetHuman ~Texan in Canada из ноябрь 25-го, 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 ноябрь 23-го.
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: "Service Outage" 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: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Verizon FiOS знал, кто вы.
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 ноябрь 23-го, 2017.