Bradford Exchange: Called twice waited for over * minutes and was...
A Bradford Exchange customer review by GetHuman user ~mark graser from November 18th, 2017
Background on ~mark graser's case
GetHuman: ~mark graser - can you tell our other Bradford Exchange customers when your case took place?
~mark graser: Yes I can. It was morning, on November 9th.
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 ~mark graser a list of common Bradford Exchange problems)
~mark graser: "Update Account Info" was why I was trying to call.
~mark graser'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.
~mark graser: Called twice waited for over * minutes and was disconnected.Called back a second time and waited again for several minutes with no help
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?
~mark graser: 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?
~mark graser: 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?
~mark graser: For that I would say four out of five.
GetHuman: And finally- any advice for other Bradford Exchange customers?
~mark graser: 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 ~mark graser taken from his Bradford Exchange customer service problem that occurred on November 9th, 2017.