Verizon Billing: * minute hold instead of usual hour for frequen...
A Verizon Billing customer review by GetHuman user ~NSQ from November 14th, 2017
Background on ~NSQ's case
GetHuman: ~NSQ - can you tell our other Verizon Billing customers when your case took place?
~NSQ: Yes I can. It was middle of the night, on November 6th.
GetHuman: Did you reach out to Verizon Billing, and if so, how?
GetHuman: And which of these common Verizon Billing customer issues best describes the reason you wanted to talk to them?
(Shows ~NSQ a list of common Verizon Billing problems)
~NSQ: "Setup service" was why I was trying to call.
~NSQ's review of Verizon Billing customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Billing 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.
~NSQ: * minute hold instead of usual hour for frequent lost service to land line and internet. Told I could save $ from basic $***month by changing to Fios for $***month. Rarely use service so not sure how that saves me $. Wish they had a sliding rate for minimal usage.
GetHuman: Let's quantify your experience contacting Verizon Billing. On a scale of 1 to 5, how easy is it go get help on a Verizon Billing problem?
~NSQ: 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?
~NSQ: I'd give them a four out of five on communication.
GetHuman: And what about Verizon Billing's ability to quickly and effectively address your problem?
~NSQ: For that I would say three out of five.
GetHuman: And finally- any advice for other Verizon Billing customers?
~NSQ: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon Billing to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~NSQ taken from his Verizon Billing customer service problem that occurred on November 6th, 2017.