Verizon FiOS: Called at *:** am eastern and I was on hold...
Verizon FiOS отзыв клиента от пользователя GetHuman GetHuman-43766 из ноябрь 22-го, 2017
Background on GetHuman-43766's case
GetHuman: GetHuman-43766 - can you tell our other Verizon FiOS customers when your case took place?
GetHuman-43766: Sure. It was afternoon, on ноябрь 14-го.
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-43766 a list of common Verizon FiOS problems)
GetHuman-43766: "Cancel Service" was why I was trying to call.
GetHuman-43766'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-43766: Called at *:** am eastern and I was on hold *** seconds after inputting the *,**,*,*,*. It then went to a recording waiting for a rep and my call was quickly answered.
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-43766: 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?
GetHuman-43766: 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?
GetHuman-43766: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
GetHuman-43766: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Verizon FiOS знал, кто вы.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-43766 taken from his Verizon FiOS customer service problem that occurred on ноябрь 14-го, 2017.