Vonage: First, they don't have chat to help existing cu...
A Vonage customer review by GetHuman user ~Ram Hari Singh from November 22nd, 2017
Background on ~Ram Hari Singh's case
GetHuman: ~Ram Hari Singh - can you tell our other Vonage customers when your case took place?
~Ram Hari Singh: Yeah. It was morning, on November 16th.
GetHuman: Did you reach out to Vonage, and if so, how?
GetHuman: And which of these common Vonage customer issues best describes the reason you wanted to talk to them?
(Shows ~Ram Hari Singh a list of common Vonage problems)
~Ram Hari Singh: "None of those really matches why I wanted to call Vonage that day." was why I was trying to call.
~Ram Hari Singh's review of Vonage customer service
GetHuman: So how would you sum up your experience for GetHuman's Vonage 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.
~Ram Hari Singh: First, they don't have chat to help existing customers!! only to sign on new customers! New customers beware, if this itself is not a warning, I don't know what is! They will sign you on but offer not service, horrible!
GetHuman: Let's quantify your experience contacting Vonage. On a scale of 1 to 5, how easy is it go get help on a Vonage problem?
~Ram Hari Singh: 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?
~Ram Hari Singh: I'd give them a five out of five on communication.
GetHuman: And what about Vonage's ability to quickly and effectively address your problem?
~Ram Hari Singh: For that I would say four out of five.
GetHuman: And finally- any advice for other Vonage customers?
~Ram Hari Singh: Call them early in the day or late. Don't forget any personal or account information you might need for Vonage to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Ram Hari Singh taken from his Vonage customer service problem that occurred on November 16th, 2017.