BB&T Bank: Can't believe they will not let you speak to so...
A BB&T Bank customer review by GetHuman user GetHuman-182261 from November 18th, 2017
Background on GetHuman-182261's case
GetHuman: GetHuman-182261 - can you tell our other BB&T Bank customers when your case took place?
GetHuman-182261: Sure. It was afternoon, on November 9th.
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-182261 a list of common BB&T Bank problems)
GetHuman-182261: "Question" was why I was trying to call.
GetHuman-182261'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-182261: Can't believe they will not let you speak to someone unless you enter your pin correctly. I don't know what pin they are referring to but my debit card pin isn't working. Ridiculous! How can they not connect you to someone?!?!
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-182261: 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?
GetHuman-182261: I'd give them a five out of five on communication.
GetHuman: And what about BB&T Bank's ability to quickly and effectively address your problem?
GetHuman-182261: For that I would say five out of five.
GetHuman: And finally- any advice for other BB&T Bank customers?
GetHuman-182261: 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-182261 taken from his BB&T Bank customer service problem that occurred on November 9th, 2017.