Vanilla Visa Card: this was a huge mistake that i wont be making a...
A Vanilla Visa Card customer review by GetHuman user ~fuck nilla from November 24th, 2017
Background on ~fuck nilla 's case
GetHuman: ~fuck nilla - can you tell our other Vanilla Visa Card customers when your case took place?
~fuck nilla : Yup. It was middle of the night, on November 22nd.
GetHuman: Did you reach out to Vanilla Visa Card, and if so, how?
GetHuman: And which of these common Vanilla Visa Card customer issues best describes the reason you wanted to talk to them?
(Shows ~fuck nilla a list of common Vanilla Visa Card problems)
~fuck nilla : "Account Setup" was why I was trying to call.
~fuck nilla 's review of Vanilla Visa Card customer service
GetHuman: So how would you sum up your experience for GetHuman's Vanilla Visa Card 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.
~fuck nilla : this was a huge mistake that i wont be making again the level of retardation these people have knows no bounds even the call me back is terrible
GetHuman: Let's quantify your experience contacting Vanilla Visa Card. On a scale of 1 to 5, how easy is it go get help on a Vanilla Visa Card problem?
~fuck nilla : I'd give them a four 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?
~fuck nilla : I'd give them a five out of five on communication.
GetHuman: And what about Vanilla Visa Card's ability to quickly and effectively address your problem?
~fuck nilla : For that I would say four out of five.
GetHuman: And finally- any advice for other Vanilla Visa Card customers?
~fuck nilla : Call them early in the day or late. Don't forget any personal or account information you might need for Vanilla Visa Card to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~fuck nilla taken from his Vanilla Visa Card customer service problem that occurred on November 22nd, 2017.