Bradford Exchange: The CSR told me my package had already been ****...
A Bradford Exchange customer review by GetHuman user ~Anonymous from November 25th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Bradford Exchange customers when your case took place?
~Anonymous: Yes I can. It was late at night, on November 16th.
GetHuman: Did you reach out to Bradford Exchange, and if so, how?
GetHuman: And which of these common Bradford Exchange customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Bradford Exchange problems)
~Anonymous: "Cancel Order" was why I was trying to call.
~Anonymous's review of Bradford Exchange customer service
GetHuman: So how would you sum up your experience for GetHuman's Bradford Exchange 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.
~Anonymous: The CSR told me my package had already been shipped but FedEx had no record of my package. I don't like being lied to. (The line also went very staticky for a portion of the call.)
GetHuman: Let's quantify your experience contacting Bradford Exchange. On a scale of 1 to 5, how easy is it go get help on a Bradford Exchange problem?
~Anonymous: 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?
~Anonymous: I'd give them a three out of five on communication.
GetHuman: And what about Bradford Exchange's ability to quickly and effectively address your problem?
~Anonymous: For that I would say two out of five.
GetHuman: And finally- any advice for other Bradford Exchange customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Bradford Exchange to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Bradford Exchange customer service problem that occurred on November 16th, 2017.