Discover: Didn't work at all the first time I tried it. T...
A Discover customer review by GetHuman user GetHuman-345977 from November 28th, 2017
Background on GetHuman-345977's case
GetHuman: GetHuman-345977 - can you tell our other Discover customers when your case took place?
GetHuman-345977: Yeah. It was afternoon, on November 26th.
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-345977 a list of common Discover problems)
GetHuman-345977: "Lower my interest rate" was why I was trying to call.
GetHuman-345977'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-345977: Didn't work at all the first time I tried it. Tried the second time, adding (*) the country code, and it worked. Must add country code. Actual service was pretty good but unrelated to the usefulness of this number for getting a human
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-345977: 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-345977: I'd give them a three out of five on communication.
GetHuman: And what about Discover's ability to quickly and effectively address your problem?
GetHuman-345977: For that I would say four out of five.
GetHuman: And finally- any advice for other Discover customers?
GetHuman-345977: 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-345977 taken from his Discover customer service problem that occurred on November 26th, 2017.