Capital One: Customer Service agent was excellent. Computer...
Una recensione del cliente Capital One da parte dell'utente GetHuman GetHuman-372201 da novembre 22º, 2017
Background on GetHuman-372201's case
GetHuman: GetHuman-372201 - can you tell our other Capital One customers when your case took place?
GetHuman-372201: Sure. It was morning, on novembre 21º.
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 GetHuman-372201 a list of common Capital One problems)
GetHuman-372201: "Payment Inquiry" was why I was trying to call.
GetHuman-372201'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.
GetHuman-372201: Customer Service agent was excellent. Computer was a little slow to pull up information but representative kept me informed and in about one min. computer was fine.
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?
GetHuman-372201: 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?
GetHuman-372201: 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?
GetHuman-372201: For that I would say three out of five.
GetHuman: And finally- any advice for other Capital One customers?
GetHuman-372201: Chiamali presto o tardi. Non dimenticare le informazioni personali o relative all'account di cui potresti aver bisogno per Capital One sapere chi sei.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-372201 taken from his Capital One customer service problem that occurred on novembre 21º, 2017.