Capital One Auto Finance: Although it is Sunday*site says call...
A Capital One Auto Finance customer review by GetHuman user ~rtorrez from November 23rd, 2017
Background on ~rtorrez's case
GetHuman: ~rtorrez - can you tell our other Capital One Auto Finance customers when your case took place?
~rtorrez: Yes I can. It was afternoon, on November 18th.
GetHuman: Did you reach out to Capital One Auto Finance, and if so, how?
GetHuman: And which of these common Capital One Auto Finance customer issues best describes the reason you wanted to talk to them?
(Shows ~rtorrez a list of common Capital One Auto Finance problems)
~rtorrez: "Update Account Info" was why I was trying to call.
~rtorrez's review of Capital One Auto Finance customer service
GetHuman: So how would you sum up your experience for GetHuman's Capital One Auto Finance 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.
~rtorrez: Although it is Sunday*site says call ***-***-**** for service ****. Called twice and now one picked-up.
GetHuman: Let's quantify your experience contacting Capital One Auto Finance. On a scale of 1 to 5, how easy is it go get help on a Capital One Auto Finance problem?
~rtorrez: 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?
~rtorrez: I'd give them a one out of five on communication.
GetHuman: And what about Capital One Auto Finance's ability to quickly and effectively address your problem?
~rtorrez: For that I would say five out of five.
GetHuman: And finally- any advice for other Capital One Auto Finance customers?
~rtorrez: Call them early in the day or late. Don't forget any personal or account information you might need for Capital One Auto Finance to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~rtorrez taken from his Capital One Auto Finance customer service problem that occurred on November 18th, 2017.