Bradford Exchange: Never answered phone after a ** min. wait I gav...
A Bradford Exchange customer review by GetHuman user ~Delores Agee from November 24th, 2017
Background on ~Delores Agee's case
GetHuman: ~Delores Agee - can you tell our other Bradford Exchange customers when your case took place?
~Delores Agee: Yes I can. It was afternoon, on November 14th.
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 ~Delores Agee a list of common Bradford Exchange problems)
~Delores Agee: "Missing Order" was why I was trying to call.
~Delores Agee'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.
~Delores Agee: Never answered phone after a ** min. wait I gave up and hung up. That is more then enough time to be put on hold very frustating!!!
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?
~Delores Agee: 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?
~Delores Agee: I'd give them a five out of five on communication.
GetHuman: And what about Bradford Exchange's ability to quickly and effectively address your problem?
~Delores Agee: For that I would say five out of five.
GetHuman: And finally- any advice for other Bradford Exchange customers?
~Delores Agee: 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 ~Delores Agee taken from his Bradford Exchange customer service problem that occurred on November 14th, 2017.