Discover: Very helpful. I called to ask them to stop send...
A Discover customer review by GetHuman user GetHuman-249748 from November 19th, 2017
Background on GetHuman-249748's case
GetHuman: GetHuman-249748 - can you tell our other Discover customers when your case took place?
GetHuman-249748: Yup. It was afternoon, on November 16th.
GetHuman: Did you reach out to Discover, and if so, how?
GetHuman: And which of these common Discover customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-249748 a list of common Discover problems)
GetHuman-249748: "Question" was why I was trying to call.
GetHuman-249748's review of Discover customer service
GetHuman: So how would you sum up your experience for GetHuman's Discover 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-249748: Very helpful. I called to ask them to stop sending me solicitations in the mail and the customer rep was extremely cooperative and helpful. This actually changed my mind about them since I've had such a hard time with my own bank's customer service.
GetHuman: Let's quantify your experience contacting Discover. On a scale of 1 to 5, how easy is it go get help on a Discover problem?
GetHuman-249748: I'd give them a three 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-249748: I'd give them a two out of five on communication.
GetHuman: And what about Discover's ability to quickly and effectively address your problem?
GetHuman-249748: For that I would say three out of five.
GetHuman: And finally- any advice for other Discover customers?
GetHuman-249748: Call them early in the day or late. Don't forget any personal or account information you might need for Discover to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-249748 taken from his Discover customer service problem that occurred on November 16th, 2017.