WalMart MoneyCard: Card activation couldn't be completed. They had...
A WalMart MoneyCard customer review by GetHuman user ~Reflective Jim from November 13th, 2017
Background on ~Reflective Jim's case
GetHuman: ~Reflective Jim - can you tell our other WalMart MoneyCard customers when your case took place?
~Reflective Jim: Yeah. It was afternoon, on November 10th.
GetHuman: Did you reach out to WalMart MoneyCard, and if so, how?
GetHuman: And which of these common WalMart MoneyCard customer issues best describes the reason you wanted to talk to them?
(Shows ~Reflective Jim a list of common WalMart MoneyCard problems)
~Reflective Jim: "Account Access" was why I was trying to call.
~Reflective Jim's review of WalMart MoneyCard customer service
GetHuman: So how would you sum up your experience for GetHuman's WalMart MoneyCard 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.
~Reflective Jim: Card activation couldn't be completed. They had to email their IT department to get it working. Still waiting...
GetHuman: Let's quantify your experience contacting WalMart MoneyCard. On a scale of 1 to 5, how easy is it go get help on a WalMart MoneyCard problem?
~Reflective Jim: 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?
~Reflective Jim: I'd give them a one out of five on communication.
GetHuman: And what about WalMart MoneyCard's ability to quickly and effectively address your problem?
~Reflective Jim: For that I would say one out of five.
GetHuman: And finally- any advice for other WalMart MoneyCard customers?
~Reflective Jim: Call them early in the day or late. Don't forget any personal or account information you might need for WalMart MoneyCard to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Reflective Jim taken from his WalMart MoneyCard customer service problem that occurred on November 10th, 2017.