WalMart: Called this number twice and also the...
A WalMart customer review by GetHuman user GetHuman-261034 from November 27th, 2017
Background on GetHuman-261034's case
GetHuman: GetHuman-261034 - can you tell our other WalMart customers when your case took place?
GetHuman-261034: Yes. It was middle of the night, on November 26th.
GetHuman: Did you reach out to WalMart, and if so, how?
GetHuman: And which of these common WalMart customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-261034 a list of common WalMart problems)
GetHuman-261034: "Problem With an Order" was why I was trying to call.
GetHuman-261034's review of WalMart customer service
GetHuman: So how would you sum up your experience for GetHuman's WalMart 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-261034: Called this number twice and also the *** ***-**** number and each time I received a busy signal when the robot transferred me to an agent. I will never use walmart.com again. Roll over in your grave Sam Walton, your company is going to the dogs.
GetHuman: Let's quantify your experience contacting WalMart. On a scale of 1 to 5, how easy is it go get help on a WalMart problem?
GetHuman-261034: 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-261034: I'd give them a five out of five on communication.
GetHuman: And what about WalMart's ability to quickly and effectively address your problem?
GetHuman-261034: For that I would say four out of five.
GetHuman: And finally- any advice for other WalMart customers?
GetHuman-261034: Call them early in the day or late. Don't forget any personal or account information you might need for WalMart to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-261034 taken from his WalMart customer service problem that occurred on November 26th, 2017.