Synchrony Bank: After finally getting through to a person I cou...
A Synchrony Bank customer review by GetHuman user GetHuman-402116 from November 22nd, 2017
Background on GetHuman-402116's case
GetHuman: GetHuman-402116 - can you tell our other Synchrony Bank customers when your case took place?
GetHuman-402116: Sure. It was middle of the night, on November 16th.
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-402116 a list of common Synchrony Bank problems)
GetHuman-402116: "Overcharge on Account" was why I was trying to call.
GetHuman-402116'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-402116: After finally getting through to a person I could talk with (about * min.) it took about * *** minutes to get my question answered.
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-402116: 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-402116: I'd give them a three out of five on communication.
GetHuman: And what about Synchrony Bank's ability to quickly and effectively address your problem?
GetHuman-402116: For that I would say two out of five.
GetHuman: And finally- any advice for other Synchrony Bank customers?
GetHuman-402116: 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-402116 taken from his Synchrony Bank customer service problem that occurred on November 16th, 2017.