Capital One: Received message: "We're here, but currently he...
A Capital One customer review by GetHuman user ~bah, humbug from November 22nd, 2017
Background on ~bah, humbug's case
GetHuman: ~bah, humbug - can you tell our other Capital One customers when your case took place?
~bah, humbug: Yes. It was afternoon, on November 17th.
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 ~bah, humbug a list of common Capital One problems)
~bah, humbug: "Payment Inquiry" was why I was trying to call.
~bah, humbug'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.
~bah, humbug: Received message: "We're here, but currently helping other *customers. You're also important so *please check back shortly. If you need *immediate assistance you may call**-***-***-****". Couldn't even wait in queue to chat with anyone.
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?
~bah, humbug: 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?
~bah, humbug: I'd give them a four out of five on communication.
GetHuman: And what about Capital One's ability to quickly and effectively address your problem?
~bah, humbug: For that I would say three out of five.
GetHuman: And finally- any advice for other Capital One customers?
~bah, humbug: 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 ~bah, humbug taken from his Capital One customer service problem that occurred on November 17th, 2017.