Synchrony Bank: Instructions to contact a live human were excel...
A Synchrony Bank customer review by GetHuman user GetHuman-147555 from November 12th, 2017
Background on GetHuman-147555's case
GetHuman: GetHuman-147555 - can you tell our other Synchrony Bank customers when your case took place?
GetHuman-147555: Yes I can. It was middle of the night, on November 5th.
GetHuman: Did you reach out to Synchrony Bank, and if so, how?
GetHuman: And which of these common Synchrony Bank customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-147555 a list of common Synchrony Bank problems)
GetHuman-147555: "Account Access" was why I was trying to call.
GetHuman-147555's review of Synchrony Bank customer service
GetHuman: So how would you sum up your experience for GetHuman's Synchrony 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-147555: Instructions to contact a live human were excellent and accomplished this goal. Issue with Bank resolved immediately and cordially by rep.
GetHuman: Let's quantify your experience contacting Synchrony Bank. On a scale of 1 to 5, how easy is it go get help on a Synchrony Bank problem?
GetHuman-147555: 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-147555: I'd give them a two out of five on communication.
GetHuman: And what about Synchrony Bank's ability to quickly and effectively address your problem?
GetHuman-147555: For that I would say one out of five.
GetHuman: And finally- any advice for other Synchrony Bank customers?
GetHuman-147555: Call them early in the day or late. Don't forget any personal or account information you might need for Synchrony Bank to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-147555 taken from his Synchrony Bank customer service problem that occurred on November 5th, 2017.