Columbia House: Person who answered the phone could have been a...
A Columbia House customer review by GetHuman user ~The Doctor from October 30th, 2017
Background on ~The Doctor's case
GetHuman: ~The Doctor - can you tell our other Columbia House customers when your case took place?
~The Doctor: Yes. It was afternoon, on October 25th.
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 ~The Doctor a list of common Columbia House problems)
~The Doctor: "None of those really matches why I wanted to call Columbia House that day." was why I was trying to call.
~The Doctor'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.
~The Doctor: Person who answered the phone could have been a little bit nicer, but all I did was call to have a name removed from the mailing list so I am ok with it.
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?
~The Doctor: I'd give them a two 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?
~The Doctor: I'd give them a one out of five on communication.
GetHuman: And what about Columbia House's ability to quickly and effectively address your problem?
~The Doctor: For that I would say five out of five.
GetHuman: And finally- any advice for other Columbia House customers?
~The Doctor: 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 ~The Doctor taken from his Columbia House customer service problem that occurred on October 25th, 2017.