Synchrony Bank: I tried to talk to a human being dozens and doz...
A Synchrony Bank customer review by GetHuman user GetHuman-401494 from November 23rd, 2017
Background on GetHuman-401494's case
GetHuman: GetHuman-401494 - can you tell our other Synchrony Bank customers when your case took place?
GetHuman-401494: Yes. It was middle of the night, on November 22nd.
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-401494 a list of common Synchrony Bank problems)
GetHuman-401494: "Overcharge on Account" was why I was trying to call.
GetHuman-401494'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-401494: I tried to talk to a human being dozens and dozens of times. It was very frustrating not to able to talk to anyone. Very poor customer service.
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-401494: I'd give them a two 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-401494: I'd give them a one out of five on communication.
GetHuman: And what about Synchrony Bank's ability to quickly and effectively address your problem?
GetHuman-401494: For that I would say two out of five.
GetHuman: And finally- any advice for other Synchrony Bank customers?
GetHuman-401494: 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-401494 taken from his Synchrony Bank customer service problem that occurred on November 22nd, 2017.