Target: They shipped the wrong item. Now I have spent o...
A Target customer review by GetHuman user ~Irate Customer from November 25th, 2017
Background on ~Irate Customer's case
GetHuman: ~Irate Customer - can you tell our other Target customers when your case took place?
~Irate Customer: Yup. It was middle of the night, on November 19th.
GetHuman: Did you reach out to Target, and if so, how?
GetHuman: And which of these common Target customer issues best describes the reason you wanted to talk to them?
(Shows ~Irate Customer a list of common Target problems)
~Irate Customer: "Warranty claim" was why I was trying to call.
~Irate Customer's review of Target customer service
GetHuman: So how would you sum up your experience for GetHuman's Target 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.
~Irate Customer: They shipped the wrong item. Now I have spent over * hours with chat and customer service. At least chat was understandable unlike the customer service people who, if they do understand English, choose to be misunderstand and I was disconnected * times.
GetHuman: Let's quantify your experience contacting Target. On a scale of 1 to 5, how easy is it go get help on a Target problem?
~Irate Customer: 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?
~Irate Customer: I'd give them a three out of five on communication.
GetHuman: And what about Target's ability to quickly and effectively address your problem?
~Irate Customer: For that I would say two out of five.
GetHuman: And finally- any advice for other Target customers?
~Irate Customer: Call them early in the day or late. Don't forget any personal or account information you might need for Target to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Irate Customer taken from his Target customer service problem that occurred on November 19th, 2017.