WalMart.com: put people who know what they are doing and som...
Una recensione del cliente WalMart.com da parte dell'utente GetHuman ~jimmyjim da novembre 25º, 2017
Background on ~jimmyjim's case
GetHuman: ~jimmyjim - can you tell our other WalMart.com customers when your case took place?
~jimmyjim: Yeah. It was morning, on novembre 16º.
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 ~jimmyjim a list of common WalMart.com problems)
~jimmyjim: "Make a purchase" was why I was trying to call.
~jimmyjim'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.
~jimmyjim: put people who know what they are doing and someone that can do something. Both people I spoke to couldn't help. The *nd one tried but came up with same problem but didn'r know what to do or call. Store said * weeks I been trying for a week.
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?
~jimmyjim: 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?
~jimmyjim: I'd give them a two out of five on communication.
GetHuman: And what about WalMart.com's ability to quickly and effectively address your problem?
~jimmyjim: For that I would say five out of five.
GetHuman: And finally- any advice for other WalMart.com customers?
~jimmyjim: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per WalMart.com sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~jimmyjim taken from his WalMart.com customer service problem that occurred on novembre 16º, 2017.