SunTrust Bank: Press * like * times then wait a few seconds. W...
A SunTrust Bank customer review by GetHuman user GetHuman-296887 from November 9th, 2017
Background on GetHuman-296887's case
GetHuman: GetHuman-296887 - can you tell our other SunTrust Bank customers when your case took place?
GetHuman-296887: Yeah. It was middle of the night, on November 1st.
GetHuman: Did you reach out to SunTrust Bank, and if so, how?
GetHuman: And which of these common SunTrust Bank customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-296887 a list of common SunTrust Bank problems)
GetHuman-296887: "Fraudulent Charge" was why I was trying to call.
GetHuman-296887's review of SunTrust Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's SunTrust 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-296887: Press * like * times then wait a few seconds. When it says it is transferring you just wait. If it asks for more info press * a few more times and wait.
GetHuman: Let's quantify your experience contacting SunTrust Bank. On a scale of 1 to 5, how easy is it go get help on a SunTrust Bank problem?
GetHuman-296887: 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-296887: I'd give them a five out of five on communication.
GetHuman: And what about SunTrust Bank's ability to quickly and effectively address your problem?
GetHuman-296887: For that I would say three out of five.
GetHuman: And finally- any advice for other SunTrust Bank customers?
GetHuman-296887: Call them early in the day or late. Don't forget any personal or account information you might need for SunTrust Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-296887 taken from his SunTrust Bank customer service problem that occurred on November 1st, 2017.