Verizon Wireless Prepaid: I have a notation on my account for a prepaid e...
Background on GetHuman-tyheywar's case
GetHuman: GetHuman-tyheywar - can you tell our other Verizon Wireless Prepaid customers when your case took place?
GetHuman-tyheywar: Yeah. It was late at night, on December 6th.
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 GetHuman-tyheywar a list of common Verizon Wireless Prepaid problems)
GetHuman-tyheywar: "Activate Account" was why I was trying to call.
GetHuman-tyheywar'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.
GetHuman-tyheywar: I have a notation on my account for a prepaid extension but the phone has already went off
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?
GetHuman-tyheywar: 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-tyheywar: 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?
GetHuman-tyheywar: For that I would say two out of five.
GetHuman: And finally- any advice for other Verizon Wireless Prepaid customers?
GetHuman-tyheywar: 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 GetHuman-tyheywar taken from his Verizon Wireless Prepaid customer service problem that occurred on December 6th, 2017.