Verizon Repair: no or intermittent service for one month...so f...
A Verizon Repair customer review by GetHuman user GetHuman-383532 from November 7th, 2017
Background on GetHuman-383532's case
GetHuman: GetHuman-383532 - can you tell our other Verizon Repair customers when your case took place?
GetHuman-383532: Yeah. It was evening, on November 2nd.
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 GetHuman-383532 a list of common Verizon Repair problems)
GetHuman-383532: "Change plan" was why I was trying to contact.
GetHuman-383532'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.
GetHuman-383532: no or intermittent service for one month...so far. Lack of service help to correct problem reported by technician a month ago. Totally frustrated!
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?
GetHuman-383532: 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?
GetHuman-383532: I'd give them a four out of five on communication.
GetHuman: And what about Verizon Repair's ability to quickly and effectively address your problem?
GetHuman-383532: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Repair customers?
GetHuman-383532: 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 GetHuman-383532 taken from his Verizon Repair customer service problem that occurred on November 2nd, 2017.