Bradford Exchange: Your agent was very kind and helpful. The wai...
A Bradford Exchange customer review by GetHuman user GetHuman-275883 from November 19th, 2017
Background on GetHuman-275883's case
GetHuman: GetHuman-275883 - can you tell our other Bradford Exchange customers when your case took place?
GetHuman-275883: Yup. It was afternoon, on November 13th.
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 GetHuman-275883 a list of common Bradford Exchange problems)
GetHuman-275883: "Track a Package" was why I was trying to call.
GetHuman-275883'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.
GetHuman-275883: Your agent was very kind and helpful. The wait was better than some and worse than others, but not bad at all.
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?
GetHuman-275883: 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?
GetHuman-275883: 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?
GetHuman-275883: For that I would say five out of five.
GetHuman: And finally- any advice for other Bradford Exchange customers?
GetHuman-275883: 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 GetHuman-275883 taken from his Bradford Exchange customer service problem that occurred on November 13th, 2017.