Verizon Wireless: I HAVE BEEN TRYING EVERYTHING EVEN LIVE CHAT AN...
A Verizon Wireless customer review by GetHuman user ~a thorny rose from November 25th, 2017
Background on ~a thorny rose's case
GetHuman: ~a thorny rose - can you tell our other Verizon Wireless customers when your case took place?
~a thorny rose: Sure. It was middle of the night, on November 17th.
GetHuman: Did you reach out to Verizon Wireless, and if so, how?
GetHuman: And which of these common Verizon Wireless customer issues best describes the reason you wanted to talk to them?
(Shows ~a thorny rose a list of common Verizon Wireless problems)
~a thorny rose: "Overcharge/Strange charge" was why I was trying to call.
~a thorny rose's review of Verizon Wireless customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Wireless 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.
~a thorny rose: I HAVE BEEN TRYING EVERYTHING EVEN LIVE CHAT AND CALL BACK AFTER NUMEROUS FAILED ATTEMTS WITH THE BEST VERIZON CALL NUM
GetHuman: Let's quantify your experience contacting Verizon Wireless. On a scale of 1 to 5, how easy is it go get help on a Verizon Wireless problem?
~a thorny rose: 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?
~a thorny rose: I'd give them a four out of five on communication.
GetHuman: And what about Verizon Wireless's ability to quickly and effectively address your problem?
~a thorny rose: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Wireless customers?
~a thorny rose: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon Wireless to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~a thorny rose taken from his Verizon Wireless customer service problem that occurred on November 17th, 2017.