As usual my experience with Discover representa...
Discover отзыв клиента от пользователя GetHuman GetHuman-37847 из ноябрь 21-го, 2017
Background on GetHuman-37847's case
GetHuman: GetHuman-37847 - can you tell our other Discover customers when your case took place?
GetHuman-37847: Yeah. It was morning, on ноябрь 15-го.
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-37847 a list of common Discover problems)
GetHuman-37847: "Lower my interest rate" was why I was trying to call.
GetHuman-37847'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-37847: As usual my experience with Discover representatives was professional, friendly, very knowledgeable of her position, and satisfied my questions completely. I spoke with someone from the Salt Lake City office, named Arrisol.
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-37847: 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-37847: I'd give them a five out of five on communication.
GetHuman: And what about Discover's ability to quickly and effectively address your problem?
GetHuman-37847: For that I would say four out of five.
GetHuman: And finally- any advice for other Discover customers?
GetHuman-37847: Позвоните им рано днем или поздно. Не забывайте личную информацию или информацию об учетной записи, которая может вам понадобиться, чтобы Discover знал, кто вы.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-37847 taken from his Discover customer service problem that occurred on ноябрь 15-го, 2017.