FedEx: I got a call center in Central America with a c...
Una FedEx reseña del cliente por el usuario de GetHuman GetHuman-383388 de noviembre 28º, 2017
Background on GetHuman-383388's case
GetHuman: GetHuman-383388 - can you tell our other FedEx customers when your case took place?
GetHuman-383388: Yup. It was middle of the night, on noviembre 19º.
GetHuman: Did you reach out to FedEx, and if so, how?
GetHuman: And which of these common FedEx customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-383388 a list of common FedEx problems)
GetHuman-383388: "Overcharge/Strange charge" was why I was trying to call.
GetHuman-383388's review of FedEx customer service
GetHuman: So how would you sum up your experience for GetHuman's FedEx 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-383388: I got a call center in Central America with a customer service rep that hardly spoke English. FedEx lost my package (did not deliver it) of medication for two months that cost me $***. they are not following up on where my package went.
GetHuman: Let's quantify your experience contacting FedEx. On a scale of 1 to 5, how easy is it go get help on a FedEx problem?
GetHuman-383388: 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?
GetHuman-383388: I'd give them a five out of five on communication.
GetHuman: And what about FedEx's ability to quickly and effectively address your problem?
GetHuman-383388: For that I would say five out of five.
GetHuman: And finally- any advice for other FedEx customers?
GetHuman-383388: Llámalos temprano en el día o tarde. No olvide ninguna información personal o de cuenta que pueda necesitar para FedEx para saber quién es usted.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-383388 taken from his FedEx customer service problem that occurred on noviembre 19º, 2017.