Credit One Bank: Nice trick! tried * different phone numbers, al...
A Credit One Bank customer review by GetHuman user ~fiznerpin from November 27th, 2017
Background on ~fiznerpin's case
GetHuman: ~fiznerpin - can you tell our other Credit One Bank customers when your case took place?
~fiznerpin: Yes I can. It was late at night, on November 23rd.
GetHuman: Did you reach out to Credit One Bank, and if so, how?
GetHuman: And which of these common Credit One Bank customer issues best describes the reason you wanted to talk to them?
(Shows ~fiznerpin a list of common Credit One Bank problems)
~fiznerpin: "Trouble Sending a Payment" was why I was trying to call.
~fiznerpin's review of Credit One Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's Credit One Bank 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.
~fiznerpin: Nice trick! tried * different phone numbers, all go to same recorded Caucasian woman...grrrr card cancelled, supposedly getting confirmation. Busted a nut trying to understand the guy.
GetHuman: Let's quantify your experience contacting Credit One Bank. On a scale of 1 to 5, how easy is it go get help on a Credit One Bank problem?
~fiznerpin: I'd give them a one 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?
~fiznerpin: I'd give them a one out of five on communication.
GetHuman: And what about Credit One Bank's ability to quickly and effectively address your problem?
~fiznerpin: For that I would say one out of five.
GetHuman: And finally- any advice for other Credit One Bank customers?
~fiznerpin: Call them early in the day or late. Don't forget any personal or account information you might need for Credit One Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~fiznerpin taken from his Credit One Bank customer service problem that occurred on November 23rd, 2017.