WalMart: I listened to their recording saying that if I...
WalMart Ulasan pelanggan oleh pengguna GetHuman ~junkateria dari November 20, 2017
Background on ~junkateria's case
GetHuman: ~junkateria - can you tell our other WalMart customers when your case took place?
~junkateria: Sure. It was morning, on November 10.
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 ~junkateria a list of common WalMart problems)
~junkateria: "Refund a Charge" was why I was trying to call.
~junkateria'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.
~junkateria: I listened to their recording saying that if I was calling about my order on walmart.com, I am in the right place. After looooong hold, the agent told me I am not in the right place and that I had to fill out a form on wm.com. Wrote it all out and the form didn't work. Never using wm again.
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?
~junkateria: I'd give them a five 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?
~junkateria: 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?
~junkateria: For that I would say three out of five.
GetHuman: And finally- any advice for other WalMart customers?
~junkateria: Hubungi mereka pada awal atau lewat. Jangan lupa maklumat peribadi atau akaun yang mungkin anda perlukan untuk WalMart mengetahui siapa anda.
GetHuman: Well there you have it. Some useful feedback and words from ~junkateria taken from his WalMart customer service problem that occurred on November 10, 2017.