Verizon Billing: yesterday, i made a trio to the local verizon s...
A Verizon Billing customer review by GetHuman user ~howard from November 22nd, 2017
Background on ~howard's case
GetHuman: ~howard - can you tell our other Verizon Billing customers when your case took place?
~howard: Yup. It was morning, on November 15th.
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 ~howard a list of common Verizon Billing problems)
~howard: "Setup Service" was why I was trying to call.
~howard'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.
~howard: yesterday, i made a trio to the local verizon store because my bill was due. i askd for an extension until the **th and was told i would get it. today is the **th and i am being asked to make a payment in order to make a call. what was yesterday about
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?
~howard: 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?
~howard: I'd give them a three out of five on communication.
GetHuman: And what about Verizon Billing's ability to quickly and effectively address your problem?
~howard: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Billing customers?
~howard: 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 ~howard taken from his Verizon Billing customer service problem that occurred on November 15th, 2017.