eTrade: If your cant open a checking account because of...
A eTrade customer review by GetHuman user ~snickles121 from November 15th, 2017
Background on ~snickles121's case
GetHuman: ~snickles121 - can you tell our other eTrade customers when your case took place?
~snickles121: Yes I can. It was morning, on November 9th.
GetHuman: Did you reach out to eTrade, and if so, how?
GetHuman: And which of these common eTrade customer issues best describes the reason you wanted to talk to them?
(Shows ~snickles121 a list of common eTrade problems)
~snickles121: "Get financial advice" was why I was trying to call.
~snickles121's review of eTrade customer service
GetHuman: So how would you sum up your experience for GetHuman's eTrade 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.
~snickles121: If your cant open a checking account because of a bad report on the chexsystems, opening a etrade brokerage account is a great second chance checking account because it comes with checks and a check card along with direct deposit. See www.badcreditmd.com*second-chance-checking-account*etrade*
GetHuman: Let's quantify your experience contacting eTrade. On a scale of 1 to 5, how easy is it go get help on a eTrade problem?
~snickles121: 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?
~snickles121: I'd give them a five out of five on communication.
GetHuman: And what about eTrade's ability to quickly and effectively address your problem?
~snickles121: For that I would say four out of five.
GetHuman: And finally- any advice for other eTrade customers?
~snickles121: Call them early in the day or late. Don't forget any personal or account information you might need for eTrade to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~snickles121 taken from his eTrade customer service problem that occurred on November 9th, 2017.