Capital One: What's in your wallet. Too bad you can't talk to C...
A Capital One customer review by GetHuman user GetHuman20663 from December 4th, 2017
Background on GetHuman20663's case
GetHuman: GetHuman20663 - can you tell our other Capital One customers when your case took place?
GetHuman20663: Yes I can. It was afternoon, on November 29th.
GetHuman: Did you reach out to Capital One, and if so, how?
GetHuman: And which of these common Capital One customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman20663 a list of common Capital One problems)
GetHuman20663: "Lost or Stolen Card" was why I was trying to call.
GetHuman20663's review of Capital One customer service
GetHuman: So how would you sum up your experience for GetHuman's Capital One 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.
GetHuman20663: What's in your wallet. Too bad you can't talk to C...
GetHuman: Can you tell the rest of us a bit more from what happened on 11/29/17?
GetHuman20663: What's in your wallet. Too bad you can't talk to Capitol One Bank.
GetHuman: Let's quantify your experience contacting Capital One. On a scale of 1 to 5, how easy is it go get help on a Capital One problem?
GetHuman20663: I'd give them a five 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?
GetHuman20663: I'd give them a two out of five on communication.
GetHuman: And what about Capital One's ability to quickly and effectively address your problem?
GetHuman20663: For that I would say five out of five.
GetHuman: And finally- any advice for other Capital One customers?
GetHuman20663: Call them early in the day or late. Don't forget any personal or account information you might need for Capital One to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman20663 taken from his Capital One customer service problem that occurred on November 29th, 2017.