Verizon: it's a dam shame when I had my phone number for...
A Verizon customer review by GetHuman user GetHuman-281952 from November 22nd, 2017
Background on GetHuman-281952's case
GetHuman: GetHuman-281952 - can you tell our other Verizon customers when your case took place?
GetHuman-281952: Yeah. It was late at night, on November 12th.
GetHuman: Did you reach out to Verizon, and if so, how?
GetHuman: And which of these common Verizon customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-281952 a list of common Verizon problems)
GetHuman-281952: "Device Support" was why I was trying to call.
GetHuman-281952's review of Verizon customer service
GetHuman: So how would you sum up your experience for GetHuman's Verizon 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-281952: it's a dam shame when I had my phone number for about a year when Verizon took it and I can't talk to my doctor when it didn't belong to Verizon in the first place. It's a obama phone any way this is the first time in my life I have every had this happen.
GetHuman: Let's quantify your experience contacting Verizon. On a scale of 1 to 5, how easy is it go get help on a Verizon problem?
GetHuman-281952: I'd give them a two 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-281952: I'd give them a three out of five on communication.
GetHuman: And what about Verizon's ability to quickly and effectively address your problem?
GetHuman-281952: For that I would say four out of five.
GetHuman: And finally- any advice for other Verizon customers?
GetHuman-281952: Call them early in the day or late. Don't forget any personal or account information you might need for Verizon to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-281952 taken from his Verizon customer service problem that occurred on November 12th, 2017.