WalMart.com: I called to tried to get information about my o...
A WalMart.com customer review by GetHuman user GetHuman-132546 from November 25th, 2017
Background on GetHuman-132546's case
GetHuman: GetHuman-132546 - can you tell our other WalMart.com customers when your case took place?
GetHuman-132546: Sure. It was middle of the night, on November 17th.
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 GetHuman-132546 a list of common WalMart.com problems)
GetHuman-132546: "Cancel order" was why I was trying to call.
GetHuman-132546'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.
GetHuman-132546: I called to tried to get information about my online order because it was suppose to arrive at are local walmart dec * and know one knows where my order is !!!!!!!!!!!!!!!!!
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?
GetHuman-132546: 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?
GetHuman-132546: 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?
GetHuman-132546: For that I would say four out of five.
GetHuman: And finally- any advice for other WalMart.com customers?
GetHuman-132546: Try to deal with them early in the day or later. 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 GetHuman-132546 taken from his WalMart.com customer service problem that occurred on November 17th, 2017.