Verizon Repair: I waited for over ** minutes then I hung up. I...
A Verizon Repair customer review by GetHuman user ~richard curran from November 16th, 2017
Background on ~richard curran's case
GetHuman: ~richard curran - can you tell our other Verizon Repair customers when your case took place?
~richard curran: Yup. It was afternoon, on November 10th.
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 ~richard curran a list of common Verizon Repair problems)
~richard curran: "Change or cancel services" was why I was trying to contact.
~richard curran'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.
~richard curran: I waited for over ** minutes then I hung up. I need the darn line fixed. tel no **********. you can reach me **********
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?
~richard curran: 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?
~richard curran: I'd give them a three out of five on communication.
GetHuman: And what about Verizon Repair's ability to quickly and effectively address your problem?
~richard curran: For that I would say four out of five.
GetHuman: And finally- any advice for other Verizon Repair customers?
~richard curran: 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 ~richard curran taken from his Verizon Repair customer service problem that occurred on November 10th, 2017.