Faculty Education Benefits application denied twice with no specific reason - requesting guidance

[JeremyC-27]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

I'm a faculty member at a US public university, teaching for 13 years, applying for GitHub Education faculty benefits. My application has been denied twice on the same day with no specific reason given in the second denial - just a generic FAQ link.

For the first application I submitted my faculty ID photo (clearly showing my name, "Staff/Faculty" designation, and the university branding). The denial email cited three account issues: missing profile name, missing billing name, and 2FA not enabled.

I corrected all three:

• Public profile name set to my full legal name
• Billing information completed with matching full name
• Two-factor authentication enabled with an authenticator app

For the second application I submitted a screenshot of my public faculty directory page on the university's official .edu domain. The screenshot includes the URL bar, my full name, "FACULTY" label, my title, my department, my institutional .edu email address, and the university's branding. This is independently verifiable - any reviewer can visit the URL directly.

The second denial gave no specific reason and pointed to a generic "common verification problems" FAQ that doesn't describe my situation.

GitHub Support's contact form for Education applications now states that individual manual reviews are no longer provided, and directs faculty here.

My questions:

1. What additional evidence would the automated verification system accept beyond a public faculty directory page on the university's .edu domain?
2. Is there a known issue with the automated verifier rejecting valid faculty applications?
3. Is there any path to escalate a denied application other than reapplying through the same automated system that already denied me twice?

I'm happy to provide my username and supporting URLs privately to any GitHub staff member who can help.

Thanks for any guidance.

[samarjeets10]

It sounds like you’ve done everything right on the profile side, but the automated system is likely failing on the physicality and metadata of the evidence provided. Since manual reviews are being phased out, you have to "game" the AI verifier by making the evidence undeniable.

Here are a few things that often trip up the system, even for valid faculty:

• The "Live Photo" Requirement: GitHub's system strongly prefers a "live" photo taken through the webcam rather than a pre-captured screenshot or an uploaded file. If you are uploading a screenshot of your faculty directory, the AI often flags it as "low signal." Try taking a photo of your physical Faculty ID card using the camera interface during the application process.

• Location Discrepancy: Ensure you are physically on campus or not using a VPN when you apply. The system checks if your IP address matches the geographical location of the university listed on your profile.

• Dated Documents: The system looks for "Current." If your ID card doesn't have a specific "2024-2025" or "Valid Thru" date, it might get rejected. The best document is usually a formal Employment Verification Letter or a Contract/Salary Letter from the current semester, printed, and then photographed.

• The "Generic" Reject: Usually, a second instant denial means your account is "cooled down." Wait 48–72 hours before trying again to ensure the system doesn't auto-flag you as spam for multiple attempts in one day.

My advice for the next attempt: Instead of the directory screenshot, try a high-resolution photo of a dated document (like a pay stub with sensitive info redacted, or a letter on university letterhead). Make sure the lighting is bright and the text is extremely clear.

Good luck—the automated system is definitely more of a "hoop" to jump through than a logical reviewer!