Verizon Land Line: After spending ** minutes on the phone and bein...
A Verizon Land Line customer review by GetHuman user ~anon from November 11th, 2017
Background on ~anon's case
GetHuman: ~anon - can you tell our other Verizon Land Line customers when your case took place?
~anon: Yeah. It was morning, on November 3rd.
GetHuman: Did you reach out to Verizon Land Line, and if so, how?
GetHuman: And which of these common Verizon Land Line customer issues best describes the reason you wanted to talk to them?
(Shows ~anon a list of common Verizon Land Line problems)
~anon: "None of those really matches why I wanted to call Verizon Land Line that day." was why I was trying to call.
~anon's review of Verizon Land Line customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Land Line 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.
~anon: After spending ** minutes on the phone and being transferred from department to department I got disconnected from the automated system as a slap in the face.
GetHuman: Let's quantify your experience contacting Verizon Land Line. On a scale of 1 to 5, how easy is it go get help on a Verizon Land Line problem?
~anon: I'd give them a five 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?
~anon: I'd give them a two out of five on communication.
GetHuman: And what about Verizon Land Line's ability to quickly and effectively address your problem?
~anon: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Land Line customers?
~anon: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Verizon Land Line to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~anon taken from his Verizon Land Line customer service problem that occurred on November 3rd, 2017.