Verizon Billing: One I was on the account next call I was not...
A Verizon Billing customer review by GetHuman user GetHuman-405494 from November 26th, 2017
Background on GetHuman-405494's case
GetHuman: GetHuman-405494 - can you tell our other Verizon Billing customers when your case took place?
GetHuman-405494: Yes. It was middle of the night, on November 22nd.
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 GetHuman-405494 a list of common Verizon Billing problems)
GetHuman-405494: "Billing question or issues" was why I was trying to call.
GetHuman-405494'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.
GetHuman-405494: One I was on the account next call I was not. Shouldn't they be using computers for my information or writing on rocks?l
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?
GetHuman-405494: 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?
GetHuman-405494: I'd give them a two out of five on communication.
GetHuman: And what about Verizon Billing's ability to quickly and effectively address your problem?
GetHuman-405494: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Billing customers?
GetHuman-405494: 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 GetHuman-405494 taken from his Verizon Billing customer service problem that occurred on November 22nd, 2017.