Verizon FiOS: Thus far, I've spoke to ** persons at Verizon a...
Verizon FiOS отзыв клиента от пользователя GetHuman ~redphoenix из ноябрь 22-го, 2017
Background on ~redphoenix's case
GetHuman: ~redphoenix - can you tell our other Verizon FiOS customers when your case took place?
~redphoenix: Sure. It was afternoon, on ноябрь 16-го.
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 ~redphoenix a list of common Verizon FiOS problems)
~redphoenix: "Update account information" was why I was trying to call.
~redphoenix'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.
~redphoenix: Thus far, I've spoke to ** persons at Verizon and not one of them can fix the mistake they made. * people disconnected unable to properly transfer or use the *'hold' function. incompetence abounding.
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?
~redphoenix: I'd give them a three 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?
~redphoenix: 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?
~redphoenix: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon FiOS customers?
~redphoenix: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Verizon FiOS знал, кто вы.
GetHuman: Well there you have it. Some useful feedback and words from ~redphoenix taken from his Verizon FiOS customer service problem that occurred on ноябрь 16-го, 2017.