UPS: I could hardly hear the person and then they qu...
Una recensione del cliente UPS da parte dell'utente GetHuman ~fuckhead666 da novembre 23º, 2017
Background on ~fuckhead666's case
GetHuman: ~fuckhead666 - can you tell our other UPS customers when your case took place?
~fuckhead666: Yes I can. It was evening, on novembre 17º.
GetHuman: Did you reach out to UPS, and if so, how?
GetHuman: And which of these common UPS customer issues best describes the reason you wanted to talk to them?
(Shows ~fuckhead666 a list of common UPS problems)
~fuckhead666: "Track a Package" was why I was trying to call.
~fuckhead666's review of UPS customer service
GetHuman: So how would you sum up your experience for GetHuman's UPS 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.
~fuckhead666: I could hardly hear the person and then they quoted me $**** to ship a ** pound package. I stayed on hold another ** minutes because I was sent to the wrong department. Come on man! *K to ship ** lbs.???? I think I will stick with USPS.... BTW,,,I am STILL on HOLD. I am finding this more than entertaining
GetHuman: Let's quantify your experience contacting UPS. On a scale of 1 to 5, how easy is it go get help on a UPS problem?
~fuckhead666: 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?
~fuckhead666: I'd give them a four out of five on communication.
GetHuman: And what about UPS's ability to quickly and effectively address your problem?
~fuckhead666: For that I would say three out of five.
GetHuman: And finally- any advice for other UPS customers?
~fuckhead666: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per UPS sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from ~fuckhead666 taken from his UPS customer service problem that occurred on novembre 17º, 2017.