Verizon Repair: verizon doesn't care to repair their old freque...
A Verizon Repair customer review by GetHuman user ~fred zadick from November 15th, 2017
Background on ~fred zadick's case
GetHuman: ~fred zadick - can you tell our other Verizon Repair customers when your case took place?
~fred zadick: Sure. It was morning, on November 11th.
GetHuman: Did you reach out to Verizon Repair, and if so, how?
GetHuman: And which of these common Verizon Repair customer issues best describes the reason you wanted to talk to them?
(Shows ~fred zadick a list of common Verizon Repair problems)
~fred zadick: "Technical support" was why I was trying to contact.
~fred zadick's review of Verizon Repair customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Repair 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.
~fred zadick: verizon doesn't care to repair their old frequently troubled lines, even for a critical medical emergency number. They said they'd sent a man out in * DAYS!!!!
GetHuman: Let's quantify your experience contacting Verizon Repair. On a scale of 1 to 5, how easy is it go get help on a Verizon Repair problem?
~fred zadick: 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?
~fred zadick: I'd give them a two out of five on communication.
GetHuman: And what about Verizon Repair's ability to quickly and effectively address your problem?
~fred zadick: For that I would say three out of five.
GetHuman: And finally- any advice for other Verizon Repair customers?
~fred zadick: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Verizon Repair to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~fred zadick taken from his Verizon Repair customer service problem that occurred on November 11th, 2017.