Verizon Repair: Never got through waited on hold ** minutes and...
A Verizon Repair customer review by GetHuman user ~caller repair from November 20th, 2017
Background on ~caller repair's case
GetHuman: ~caller repair - can you tell our other Verizon Repair customers when your case took place?
~caller repair: Yes I can. It was middle of the night, on November 18th.
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 ~caller repair a list of common Verizon Repair problems)
~caller repair: "Overcharge/Strange charge" was why I was trying to contact.
~caller repair'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.
~caller repair: Never got through waited on hold ** minutes and no one ever picked up. I was trying to report service outage for my customer business repair
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?
~caller repair: I'd give them a two 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?
~caller repair: I'd give them a five out of five on communication.
GetHuman: And what about Verizon Repair's ability to quickly and effectively address your problem?
~caller repair: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon Repair customers?
~caller repair: 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 ~caller repair taken from his Verizon Repair customer service problem that occurred on November 18th, 2017.