WalMart.com: Couldn't get a human. Pressing *, then * did no...
A WalMart.com customer review by GetHuman user ~Miz Pat from November 24th, 2017
Background on ~Miz Pat's case
GetHuman: ~Miz Pat - can you tell our other WalMart.com customers when your case took place?
~Miz Pat: Yup. It was evening, on November 20th.
GetHuman: Did you reach out to WalMart.com, and if so, how?
GetHuman: And which of these common WalMart.com customer issues best describes the reason you wanted to talk to them?
(Shows ~Miz Pat a list of common WalMart.com problems)
~Miz Pat: "Account Access" was why I was trying to call.
~Miz Pat's review of WalMart.com customer service
GetHuman: So how would you sum up your experience for GetHuman's WalMart.com 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.
~Miz Pat: Couldn't get a human. Pressing *, then * did not solve the problem. Machine could not solve my problem.
GetHuman: Let's quantify your experience contacting WalMart.com. On a scale of 1 to 5, how easy is it go get help on a WalMart.com problem?
~Miz Pat: 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?
~Miz Pat: I'd give them a one out of five on communication.
GetHuman: And what about WalMart.com's ability to quickly and effectively address your problem?
~Miz Pat: For that I would say five out of five.
GetHuman: And finally- any advice for other WalMart.com customers?
~Miz Pat: Call them early in the day or late. Don't forget any personal or account information you might need for WalMart.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Miz Pat taken from his WalMart.com customer service problem that occurred on November 20th, 2017.