Synchrony Bank: I was actually surprised to have good service...
A Synchrony Bank customer review by GetHuman user GetHuman-403794 from November 27th, 2017
Background on GetHuman-403794's case
GetHuman: GetHuman-403794 - can you tell our other Synchrony Bank customers when your case took place?
GetHuman-403794: Yes. It was middle of the night, on November 19th.
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-403794 a list of common Synchrony Bank problems)
GetHuman-403794: "Complaint" was why I was trying to call.
GetHuman-403794'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-403794: I was actually surprised to have good service. Usually, it's a foreign country and the language is hard to understand. Thanks for the recommendation.
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-403794: I'd give them a four 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-403794: I'd give them a five out of five on communication.
GetHuman: And what about Synchrony Bank's ability to quickly and effectively address your problem?
GetHuman-403794: For that I would say four out of five.
GetHuman: And finally- any advice for other Synchrony Bank customers?
GetHuman-403794: 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-403794 taken from his Synchrony Bank customer service problem that occurred on November 19th, 2017.