GE Money Bank: I saw an increase in the monthly payment. No mi...
A GE Money Bank customer review by GetHuman user ~djstevet from November 2nd, 2017
Background on ~djstevet's case
GetHuman: ~djstevet - can you tell our other GE Money Bank customers when your case took place?
~djstevet: Sure. It was afternoon, on October 27th.
GetHuman: Did you reach out to GE Money Bank, and if so, how?
GetHuman: And which of these common GE Money Bank customer issues best describes the reason you wanted to talk to them?
(Shows ~djstevet a list of common GE Money Bank problems)
~djstevet: "Setup an account" was why I was trying to call.
~djstevet's review of GE Money Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's GE Money Bank 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.
~djstevet: I saw an increase in the monthly payment. No missing or late payments. When I spoke to them they kept saying it was an error and would be corrected. Every month the same story. I am processing a complaint with the NJ Attorney General's office.
GetHuman: Let's quantify your experience contacting GE Money Bank. On a scale of 1 to 5, how easy is it go get help on a GE Money Bank problem?
~djstevet: I'd give them a one 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?
~djstevet: I'd give them a two out of five on communication.
GetHuman: And what about GE Money Bank's ability to quickly and effectively address your problem?
~djstevet: For that I would say three out of five.
GetHuman: And finally- any advice for other GE Money Bank customers?
~djstevet: Call them early in the day or late. Don't forget any personal or account information you might need for GE Money Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~djstevet taken from his GE Money Bank customer service problem that occurred on October 27th, 2017.