Verizon Land Line: Hit * ** times and was transferred to an agent...
A Verizon Land Line customer review by GetHuman user ~Helen from November 22nd, 2017
Background on ~Helen's case
GetHuman: ~Helen - can you tell our other Verizon Land Line customers when your case took place?
~Helen: Yup. It was middle of the night, on November 15th.
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 ~Helen a list of common Verizon Land Line problems)
~Helen: "None of those really matches why I wanted to call Verizon Land Line that day." was why I was trying to call.
~Helen'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.
~Helen: Hit * ** times and was transferred to an agent. Issues with residential landline phones not working - will send someone out within ** hours
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?
~Helen: 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?
~Helen: I'd give them a four out of five on communication.
GetHuman: And what about Verizon Land Line's ability to quickly and effectively address your problem?
~Helen: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon Land Line customers?
~Helen: 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 ~Helen taken from his Verizon Land Line customer service problem that occurred on November 15th, 2017.