Bradford Exchange: pretty quick automated computer voice response...
A Bradford Exchange customer review by GetHuman user ~hugh hollowell from November 24th, 2017
Background on ~hugh hollowell's case
GetHuman: ~hugh hollowell - can you tell our other Bradford Exchange customers when your case took place?
~hugh hollowell: Yup. It was morning, on November 18th.
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 ~hugh hollowell a list of common Bradford Exchange problems)
~hugh hollowell: "Change order" was why I was trying to call.
~hugh hollowell'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.
~hugh hollowell: pretty quick automated computer voice response and fairly intelligible---- now I know when my order is supposed to ship
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?
~hugh hollowell: I'd give them a three 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?
~hugh hollowell: I'd give them a four out of five on communication.
GetHuman: And what about Bradford Exchange's ability to quickly and effectively address your problem?
~hugh hollowell: For that I would say five out of five.
GetHuman: And finally- any advice for other Bradford Exchange customers?
~hugh hollowell: 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 ~hugh hollowell taken from his Bradford Exchange customer service problem that occurred on November 18th, 2017.