Verizon Wireless Financial: After explaining my personal situation, they we...
A Verizon Wireless Financial customer review by GetHuman user ~B from November 13th, 2017
Background on ~B's case
GetHuman: ~B - can you tell our other Verizon Wireless Financial customers when your case took place?
~B: Yes I can. It was evening, on November 8th.
GetHuman: Did you reach out to Verizon Wireless Financial, and if so, how?
GetHuman: And which of these common Verizon Wireless Financial customer issues best describes the reason you wanted to talk to them?
(Shows ~B a list of common Verizon Wireless Financial problems)
~B: "Overcharge on Account" was why I was trying to call.
~B's review of Verizon Wireless Financial customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Wireless Financial 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.
~B: After explaining my personal situation, they were very helpful and VERY kind. Thanks, Verizon, for your understanding and your help!
GetHuman: Let's quantify your experience contacting Verizon Wireless Financial. On a scale of 1 to 5, how easy is it go get help on a Verizon Wireless Financial problem?
~B: 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?
~B: I'd give them a two out of five on communication.
GetHuman: And what about Verizon Wireless Financial's ability to quickly and effectively address your problem?
~B: For that I would say one out of five.
GetHuman: And finally- any advice for other Verizon Wireless Financial customers?
~B: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon Wireless Financial to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~B taken from his Verizon Wireless Financial customer service problem that occurred on November 8th, 2017.