Credit One Bank: wrote address on bill to cancel card still bein...
A Credit One Bank customer review by GetHuman user GetHuman-78077 from November 25th, 2017
Background on GetHuman-78077's case
GetHuman: GetHuman-78077 - can you tell our other Credit One Bank customers when your case took place?
GetHuman-78077: Yeah. It was evening, on November 22nd.
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 GetHuman-78077 a list of common Credit One Bank problems)
GetHuman-78077: "Account Access" was why I was trying to call.
GetHuman-78077'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.
GetHuman-78077: wrote address on bill to cancel card still being billed. called service number was put on hold and hung up on. no reputable bank does this to customers.
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?
GetHuman-78077: 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?
GetHuman-78077: I'd give them a five out of five on communication.
GetHuman: And what about Credit One Bank's ability to quickly and effectively address your problem?
GetHuman-78077: For that I would say two out of five.
GetHuman: And finally- any advice for other Credit One Bank customers?
GetHuman-78077: 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 GetHuman-78077 taken from his Credit One Bank customer service problem that occurred on November 22nd, 2017.