Verizon Wireless Prepaid: Never got to a human being. Automated system k...
A Verizon Wireless Prepaid customer review by GetHuman user ~fed up from November 26th, 2017
Background on ~fed up's case
GetHuman: ~fed up - can you tell our other Verizon Wireless Prepaid customers when your case took place?
~fed up: Yes. It was evening, on November 19th.
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 ~fed up a list of common Verizon Wireless Prepaid problems)
~fed up: "Activate Account" was why I was trying to call.
~fed up'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.
~fed up: Never got to a human being. Automated system kept saying, "sorry you are having trouble. Good bye." Then it hung up.
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?
~fed up: I'd give them a three 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?
~fed up: I'd give them a five out of five on communication.
GetHuman: And what about Verizon Wireless Prepaid's ability to quickly and effectively address your problem?
~fed up: For that I would say five out of five.
GetHuman: And finally- any advice for other Verizon Wireless Prepaid customers?
~fed up: 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 ~fed up taken from his Verizon Wireless Prepaid customer service problem that occurred on November 19th, 2017.