Classmates.com: This program is not user friendly and if you do...
A Classmates.com customer review by GetHuman user GetHuman-165346 from November 25th, 2017
Background on GetHuman-165346's case
GetHuman: GetHuman-165346 - can you tell our other Classmates.com customers when your case took place?
GetHuman-165346: Sure. It was morning, on November 19th.
GetHuman: Did you reach out to Classmates.com, and if so, how?
GetHuman: And which of these common Classmates.com customer issues best describes the reason you wanted to talk to them?
(Shows GetHuman-165346 a list of common Classmates.com problems)
GetHuman-165346: "Lower my bill" was why I was trying to call.
GetHuman-165346's review of Classmates.com customer service
GetHuman: So how would you sum up your experience for GetHuman's Classmates.com 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-165346: This program is not user friendly and if you don't use it daily it certainly isn't worth the money. I cancelled my credit card also so you cannot charge me again!
GetHuman: Let's quantify your experience contacting Classmates.com. On a scale of 1 to 5, how easy is it go get help on a Classmates.com problem?
GetHuman-165346: 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-165346: I'd give them a one out of five on communication.
GetHuman: And what about Classmates.com's ability to quickly and effectively address your problem?
GetHuman-165346: For that I would say five out of five.
GetHuman: And finally- any advice for other Classmates.com customers?
GetHuman-165346: Call them early in the day or late. Don't forget any personal or account information you might need for Classmates.com to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from GetHuman-165346 taken from his Classmates.com customer service problem that occurred on November 19th, 2017.