Have called Columbia House about a billing prob...
A Columbia House customer review by GetHuman user ~bluehorse from November 20th, 2017
Background on ~bluehorse's case
GetHuman: ~bluehorse - can you tell our other Columbia House customers when your case took place?
~bluehorse: Yes I can. It was morning, on November 16th.
GetHuman: Did you reach out to Columbia House, and if so, how?
GetHuman: And which of these common Columbia House customer issues best describes the reason you wanted to talk to them?
(Shows ~bluehorse a list of common Columbia House problems)
~bluehorse: "None of those really matches why I wanted to call Columbia House that day." was why I was trying to call.
~bluehorse's review of Columbia House customer service
GetHuman: So how would you sum up your experience for GetHuman's Columbia House 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.
~bluehorse: Have called Columbia House about a billing problem three times and this last time is the only one that seems hopeful. I am now waiting for a supervisor to call me back.
GetHuman: Let's quantify your experience contacting Columbia House. On a scale of 1 to 5, how easy is it go get help on a Columbia House problem?
~bluehorse: 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?
~bluehorse: I'd give them a five out of five on communication.
GetHuman: And what about Columbia House's ability to quickly and effectively address your problem?
~bluehorse: For that I would say five out of five.
GetHuman: And finally- any advice for other Columbia House customers?
~bluehorse: Call them early in the day or late. Don't forget any personal or account information you might need for Columbia House to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~bluehorse taken from his Columbia House customer service problem that occurred on November 16th, 2017.