Target: I called to inquire why my shipping and handlin...
Eine Target Kundenbewertung durch GetHuman-Benutzer GetHuman-76231 von November 28., 2017
Background on GetHuman-76231's case
GetHuman: GetHuman-76231 - can you tell our other Target customers when your case took place?
GetHuman-76231: Sure. It was middle of the night, on November 20..
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 GetHuman-76231 a list of common Target problems)
GetHuman-76231: "Store Feedback" was why I was trying to call.
GetHuman-76231'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.
GetHuman-76231: I called to inquire why my shipping and handling was not refunded on my return. Jeff wouldn't give any way to identify himself. Re case number ********. I order often from target but I never will again if my *.** s and h isn't refunded.
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?
GetHuman-76231: I'd give them a four 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?
GetHuman-76231: 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?
GetHuman-76231: For that I would say two out of five.
GetHuman: And finally- any advice for other Target customers?
GetHuman-76231: Rufen Sie sie früh am Tag oder spät an. Vergessen Sie nicht alle persönlichen oder Kontoinformationen, die Sie benötigen, damit Target weiß, wer Sie sind.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-76231 taken from his Target customer service problem that occurred on November 20., 2017.