Verizon: I was placed on hold, told that they could not...
A Verizon customer review by GetHuman user ~hexafraction from November 23rd, 2017
Background on ~hexafraction's case
GetHuman: ~hexafraction - can you tell our other Verizon customers when your case took place?
~hexafraction: Yes. It was evening, on November 15th.
GetHuman: Did you reach out to Verizon, and if so, how?
GetHuman: And which of these common Verizon customer issues best describes the reason you wanted to talk to them?
(Shows ~hexafraction a list of common Verizon problems)
~hexafraction: "Setup service" was why I was trying to call.
~hexafraction's review of Verizon customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon 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.
~hexafraction: I was placed on hold, told that they could not replicate obvious symptoms (I'm an IT person and I would know), refused to suport Linux even though the computer was not the root cause. AND transferred me to DELL Customer support, which has no business in this inquiry.
GetHuman: Let's quantify your experience contacting Verizon. On a scale of 1 to 5, how easy is it go get help on a Verizon problem?
~hexafraction: 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?
~hexafraction: I'd give them a three out of five on communication.
GetHuman: And what about Verizon's ability to quickly and effectively address your problem?
~hexafraction: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon customers?
~hexafraction: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~hexafraction taken from his Verizon customer service problem that occurred on November 15th, 2017.