BB&T Bank: Thank God for this page. My problem didn't fall...
A BB&T Bank customer review by GetHuman user GetHuman-225107 from November 26th, 2017
Background on GetHuman-225107's case
GetHuman: GetHuman-225107 - can you tell our other BB&T Bank customers when your case took place?
GetHuman-225107: Yeah. It was middle of the night, on November 18th.
GetHuman: Did you reach out to BB&T Bank, and if so, how?
GetHuman: And which of these common BB&T Bank customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-225107 a list of common BB&T Bank problems)
GetHuman-225107: "Update Account Info" was why I was trying to call.
GetHuman-225107's review of BB&T Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's BB&T 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.
GetHuman-225107: Thank God for this page. My problem didn't fall into the, "Press * for ..." answer tree. I had spent ** minutes trying to get an actual person with no luck. With this, I had to wait, but at least I got a person.
GetHuman: Let's quantify your experience contacting BB&T Bank. On a scale of 1 to 5, how easy is it go get help on a BB&T Bank problem?
GetHuman-225107: 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?
GetHuman-225107: I'd give them a two out of five on communication.
GetHuman: And what about BB&T Bank's ability to quickly and effectively address your problem?
GetHuman-225107: For that I would say three out of five.
GetHuman: And finally- any advice for other BB&T Bank customers?
GetHuman-225107: Call them early in the day or late. Don't forget any personal or account information you might need for BB&T Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-225107 taken from his BB&T Bank customer service problem that occurred on November 18th, 2017.