Vanilla Visa Card: I attempted to report a Vanilla gift card found...
A Vanilla Visa Card customer review by GetHuman user GetHuman-428933 from November 20th, 2017
Background on GetHuman-428933's case
GetHuman: GetHuman-428933 - can you tell our other Vanilla Visa Card customers when your case took place?
GetHuman-428933: Yup. It was morning, on November 14th.
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 GetHuman-428933 a list of common Vanilla Visa Card problems)
GetHuman-428933: "Account Setup" was why I was trying to call.
GetHuman-428933'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.
GetHuman-428933: I attempted to report a Vanilla gift card found on my driveway - what to do with it? Finally just cut it in half.
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?
GetHuman-428933: 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?
GetHuman-428933: I'd give them a three out of five on communication.
GetHuman: And what about Vanilla Visa Card's ability to quickly and effectively address your problem?
GetHuman-428933: For that I would say one out of five.
GetHuman: And finally- any advice for other Vanilla Visa Card customers?
GetHuman-428933: 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 GetHuman-428933 taken from his Vanilla Visa Card customer service problem that occurred on November 14th, 2017.