Verizon Wireless Prepaid: I can't believe I got through so fast. The guy...
A Verizon Wireless Prepaid customer review by GetHuman user ~KenB from November 16th, 2017
Background on ~KenB's case
GetHuman: ~KenB - can you tell our other Verizon Wireless Prepaid customers when your case took place?
~KenB: Yes. It was evening, on November 8th.
GetHuman: Did you reach out to Verizon Wireless Prepaid, and if so, how?
GetHuman: And which of these common Verizon Wireless Prepaid customer issues best describes the reason you wanted to talk to them?
(Shows ~KenB a list of common Verizon Wireless Prepaid problems)
~KenB: "Change Plan" was why I was trying to call.
~KenB's review of Verizon Wireless Prepaid customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon Wireless Prepaid 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.
~KenB: I can't believe I got through so fast. The guy that helped me knew what he was doing. I activated my phone on a new * and paid my bill in less than * minutes.
GetHuman: Let's quantify your experience contacting Verizon Wireless Prepaid. On a scale of 1 to 5, how easy is it go get help on a Verizon Wireless Prepaid problem?
~KenB: 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?
~KenB: I'd give them a two out of five on communication.
GetHuman: And what about Verizon Wireless Prepaid's ability to quickly and effectively address your problem?
~KenB: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Wireless Prepaid customers?
~KenB: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon Wireless Prepaid to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~KenB taken from his Verizon Wireless Prepaid customer service problem that occurred on November 8th, 2017.