NCAA Eligibility Center: I miraculously got through to someone and they...
A NCAA Eligibility Center customer review by GetHuman user ~jim from November 27th, 2017
Background on ~jim's case
GetHuman: ~jim - can you tell our other NCAA Eligibility Center customers when your case took place?
~jim: Yes I can. It was morning, on November 23rd.
GetHuman: Did you reach out to NCAA Eligibility Center, and if so, how?
GetHuman: And which of these common NCAA Eligibility Center customer issues best describes the reason you wanted to talk to them?
(Shows ~jim a list of common NCAA Eligibility Center problems)
~jim: "None of those really matches why I wanted to call NCAA Eligibility Center that day." was why I was trying to call.
~jim's review of NCAA Eligibility Center customer service
GetHuman: So how would you sum up your experience for GetHuman's NCAA Eligibility Center 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.
~jim: I miraculously got through to someone and they were very helpful. They need more cust service reps.
GetHuman: Let's quantify your experience contacting NCAA Eligibility Center. On a scale of 1 to 5, how easy is it go get help on a NCAA Eligibility Center problem?
~jim: 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?
~jim: I'd give them a two out of five on communication.
GetHuman: And what about NCAA Eligibility Center's ability to quickly and effectively address your problem?
~jim: For that I would say five out of five.
GetHuman: And finally- any advice for other NCAA Eligibility Center customers?
~jim: Call them early in the day or late. Don't forget any personal or account information you might need for NCAA Eligibility Center to know who you are.
GetHuman: Well there you have it. Some useful feedback and words from ~jim taken from his NCAA Eligibility Center customer service problem that occurred on November 23rd, 2017.