Armed Forces Bank: Money was put in my account from someone else a...
A Armed Forces Bank customer review by GetHuman user ~Anonymous from November 16th, 2017
Background on ~Anonymous's case
GetHuman: ~Anonymous - can you tell our other Armed Forces Bank customers when your case took place?
~Anonymous: Yes. It was afternoon, on November 8th.
GetHuman: Did you reach out to Armed Forces Bank, and if so, how?
GetHuman: And which of these common Armed Forces Bank customer issues best describes the reason you wanted to talk to them?
(Shows ~Anonymous a list of common Armed Forces Bank problems)
~Anonymous: "Setup an account" was why I was trying to call.
~Anonymous's review of Armed Forces Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's Armed Forces 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.
~Anonymous: Money was put in my account from someone else account - almost *,***.**. Customer service is requesting a passcode from me before they will talk to me and I don't have.
GetHuman: Let's quantify your experience contacting Armed Forces Bank. On a scale of 1 to 5, how easy is it go get help on a Armed Forces Bank problem?
~Anonymous: 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?
~Anonymous: I'd give them a two out of five on communication.
GetHuman: And what about Armed Forces Bank's ability to quickly and effectively address your problem?
~Anonymous: For that I would say one out of five.
GetHuman: And finally- any advice for other Armed Forces Bank customers?
~Anonymous: Call them early in the day or late. Don't forget any personal or account information you might need for Armed Forces Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~Anonymous taken from his Armed Forces Bank customer service problem that occurred on November 8th, 2017.