Verizon Wireless: I was connected right away. The customer servic...
A Verizon Wireless customer review by GetHuman user GetHuman-164851 from November 24th, 2017
Background on GetHuman-164851's case
GetHuman: GetHuman-164851 - can you tell our other Verizon Wireless customers when your case took place?
GetHuman-164851: Sure. It was morning, on November 22nd.
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 GetHuman-164851 a list of common Verizon Wireless problems)
GetHuman-164851: "Account Access" was why I was trying to call.
GetHuman-164851'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.
GetHuman-164851: I was connected right away. The customer service rep. spoke very good English and everything was taken care of very quickly.
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?
GetHuman-164851: 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-164851: I'd give them a three out of five on communication.
GetHuman: And what about Verizon Wireless's ability to quickly and effectively address your problem?
GetHuman-164851: For that I would say two out of five.
GetHuman: And finally- any advice for other Verizon Wireless customers?
GetHuman-164851: 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 GetHuman-164851 taken from his Verizon Wireless customer service problem that occurred on November 22nd, 2017.