Target: The absolute WORST customer service I've EVER d...
A Target customer review by GetHuman user ~Al from November 19th, 2017
Background on ~Al's case
GetHuman: ~Al - can you tell our other Target customers when your case took place?
~Al: Yes. It was middle of the night, on November 10th.
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 ~Al a list of common Target problems)
~Al: "Make a purchase" was why I was trying to call.
~Al'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.
~Al: The absolute WORST customer service I've EVER dealt with. The representative had NO idea how to help me (in regards to returning a defective item that I purchased * day prior which I HAD the receipt for). I asked her to transfer me to a supervisor (ANY supervisor) and I was put on hold for a FULL hour and then was told to call back tomorrow. ABSOLUTELY HORRIBLE service. I will NEVER shop at a Target again.
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?
~Al: I'd give them a one 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?
~Al: I'd give them a two out of five on communication.
GetHuman: And what about Target's ability to quickly and effectively address your problem?
~Al: For that I would say five out of five.
GetHuman: And finally- any advice for other Target customers?
~Al: 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 ~Al taken from his Target customer service problem that occurred on November 10th, 2017.