WalMart Credit Card: Communications effective. Problem solution unab...
A WalMart Credit Card customer review by GetHuman user ~time wasted from November 22nd, 2017
Background on ~time wasted's case
GetHuman: ~time wasted - can you tell our other WalMart Credit Card customers when your case took place?
~time wasted: Yeah. It was afternoon, on November 20th.
GetHuman: Did you reach out to WalMart Credit Card, and if so, how?
GetHuman: And which of these common WalMart Credit Card customer issues best describes the reason you wanted to talk to them?
(Shows ~time wasted a list of common WalMart Credit Card problems)
~time wasted: "Overcharge/Strange charge" was why I was trying to call.
~time wasted's review of WalMart Credit Card customer service
GetHuman: So how would you sum up your experience for GetHuman's WalMart Credit 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.
~time wasted: Communications effective. Problem solution unabtained. For a positive memorable expirence, resolution needed.
GetHuman: Let's quantify your experience contacting WalMart Credit Card. On a scale of 1 to 5, how easy is it go get help on a WalMart Credit Card problem?
~time wasted: 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?
~time wasted: I'd give them a five out of five on communication.
GetHuman: And what about WalMart Credit Card's ability to quickly and effectively address your problem?
~time wasted: For that I would say five out of five.
GetHuman: And finally- any advice for other WalMart Credit Card customers?
~time wasted: Call them early in the day or late. Don't forget any personal or account information you might need for WalMart Credit Card to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~time wasted taken from his WalMart Credit Card customer service problem that occurred on November 20th, 2017.