WalMart: Millie was not helpful. She only gave an item n...
Una recensione del cliente WalMart da parte dell'utente GetHuman ~Kate da novembre 26º, 2017
Background on ~Kate's case
GetHuman: ~Kate - can you tell our other WalMart customers when your case took place?
~Kate: Sure. It was afternoon, on novembre 25º.
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 ~Kate a list of common WalMart problems)
~Kate: "Overcharge/Strange charge" was why I was trying to call.
~Kate'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.
~Kate: Millie was not helpful. She only gave an item number ********* and told me to keep checking back. Today I received an email that the item was in stock. Your system is extremely poor customer service when an email is sent saying the item is available and when I go to order I am told it is out of stock and keep trying.....April *, ****
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?
~Kate: 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?
~Kate: I'd give them a two out of five on communication.
GetHuman: And what about WalMart's ability to quickly and effectively address your problem?
~Kate: For that I would say five out of five.
GetHuman: And finally- any advice for other WalMart customers?
~Kate: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per WalMart sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~Kate taken from his WalMart customer service problem that occurred on novembre 25º, 2017.