Chase UCard: COULD NOT GET NOT ONE REAL PERSON TO TALK TO ME...
A Chase UCard customer review by GetHuman user ~HUERTALIZETH from November 22nd, 2017
Background on ~HUERTALIZETH's case
GetHuman: ~HUERTALIZETH - can you tell our other Chase UCard customers when your case took place?
~HUERTALIZETH: Sure. It was afternoon, on November 21st.
GetHuman: Did you reach out to Chase UCard, and if so, how?
GetHuman: And which of these common Chase UCard customer issues best describes the reason you wanted to talk to them?
(Shows ~HUERTALIZETH a list of common Chase UCard problems)
~HUERTALIZETH: "Setup an account" was why I was trying to call.
~HUERTALIZETH's review of Chase UCard customer service
GetHuman: So how would you sum up your experience for GetHuman's Chase UCard 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.
~HUERTALIZETH: COULD NOT GET NOT ONE REAL PERSON TO TALK TO ME. I JUST HAD ONE QUESTION AND I COULD NOT GET A LIVE PERSON TO HELP. THERE SHOULD BE AN OPTION SAYING "IF YOU HAVE A QUESTION ABOUT YOUR ACCOUNT PRESS ..."
GetHuman: Let's quantify your experience contacting Chase UCard. On a scale of 1 to 5, how easy is it go get help on a Chase UCard problem?
~HUERTALIZETH: 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?
~HUERTALIZETH: I'd give them a two out of five on communication.
GetHuman: And what about Chase UCard's ability to quickly and effectively address your problem?
~HUERTALIZETH: For that I would say three out of five.
GetHuman: And finally- any advice for other Chase UCard customers?
~HUERTALIZETH: Try to deal with them early in the day or later. Don't forget any personal or account information you might need for Chase UCard to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~HUERTALIZETH taken from his Chase UCard customer service problem that occurred on November 21st, 2017.