FedEx (Canada): Terrible experience with FedEx. Should be re-na...
A FedEx (Canada) customer review by GetHuman user ~libin from November 25th, 2017
Background on ~libin's case
GetHuman: ~libin - can you tell our other FedEx (Canada) customers when your case took place?
~libin: Yup. It was middle of the night, on November 24th.
GetHuman: Did you reach out to FedEx (Canada), and if so, how?
GetHuman: And which of these common FedEx (Canada) customer issues best describes the reason you wanted to talk to them?
(Shows ~libin a list of common FedEx (Canada) problems)
~libin: "Overcharge/Strange charge" was why I was trying to call.
~libin's review of FedEx (Canada) customer service
GetHuman: So how would you sum up your experience for GetHuman's FedEx (Canada) 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.
~libin: Terrible experience with FedEx. Should be re-named to Fed-Up Ex-customers. Non user friendly online shipment service, irrate and cluless customer reps, horrible pick-up and delivery service adds to the many issues with them. Never again will trust FedEx.
GetHuman: Let's quantify your experience contacting FedEx (Canada). On a scale of 1 to 5, how easy is it go get help on a FedEx (Canada) problem?
~libin: 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?
~libin: I'd give them a three out of five on communication.
GetHuman: And what about FedEx (Canada)'s ability to quickly and effectively address your problem?
~libin: For that I would say two out of five.
GetHuman: And finally- any advice for other FedEx (Canada) customers?
~libin: Call them early in the day or late. Don't forget any personal or account information you might need for FedEx (Canada) to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~libin taken from his FedEx (Canada) customer service problem that occurred on November 24th, 2017.