Urgent: Automated Bot repeatedly rejecting genuine Student Application (User: amankumartiwari545)

[amankumartiwari545]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Hi GitHub Education Community Managers,

I am writing to report that the automated AI verification system is repeatedly rejecting my genuine student application without providing any specific reasons (latest rejection on Oct 4).

My school is currently severely affected by floods (Maker, Saran, Bihar, India), making it impossible to visit the campus or get new physical documents. However, I have provided 100% authentic, computer-printed official documents issued by the Bihar School Examination Board (BSEB).

Here are my verified details:

1. Legal Name: Aman Kumar (Matches perfectly with my GitHub Billing Info and Public Profile).
2. Username: amankumartiwari545
3. School Name: SR. SEC. SCHOOL, KAITUKA, LACHHI -MAKER, SARAN (BSEB School Code: 41130).
4. Document Used: Official BSEB Intermediate Registration Form (Session 2026-2028), captured live with clear lighting and zero blur.

Since individual manual support tickets are no longer accepted, the automated bot is stuck in a loop and unfairly denying me access to student benefits. I sincerely request a community moderator or staff member to escalate my case and manually verify my academic affiliation.

Thank you,
Aman Kumar

[prathamgosai]

1. Do Not Re-submit Immediately
   Repeated automatic rejections can trigger further flags. Wait at least 48–72 hours before trying again, as the system may need time to reset or process your previous submission.

2. Ensure Documents Meet Strict Criteria
   The automated system is very sensitive. Double-check that your uploaded BSEB document:

Is clear, unblurred, and fully legible.
Shows your full legal name exactly as it appears on your GitHub profile and billing info.
Is an official, unedited document (no Photoshop, no cropped edges that hide information).
Is in a supported format (usually JPG or PNG, under 10MB).
3. Check Your Profile Consistency
Ensure your GitHub username and legal name on your public profile match the name on your school document exactly.
Ensure your billing address (if you have one) is consistent with your school’s location or legal residence.
4. Try a Different Browser or Device
Sometimes browser extensions or cache issues can cause upload or verification errors. Try using Incognito/Private mode or a different browser (e.g., Firefox or Safari) to submit your application.

5. Reach Out via Official Channels
   Since the community forum may not have active staff monitoring every thread:

Check if your school has a GitHub Education Campus Representative or administrator who can help verify your enrollment.
If you have a .edu email, try using that to re-submit, as it may trigger a different verification path.
6. Wait for Manual Review
If the automated system continues to reject you, you may need to wait for a manual review. This can take several days. Keep checking your email (including spam) for any communication from GitHub Education.

Important Note:
Do not share personal documents in public forums or with anyone online except through GitHub’s official secure upload portal.
Beware of scams: No one should ask for your GitHub password or payment details to help with verification.

[KasraK2K]

Hi @amankumartiwari545, sorry to hear about the flooding affecting your school — that's a genuinely tough situation on top of an already frustrating verification process.

A couple of practical points to add:

1. GitHub Education verification is handled by an automated system plus a dedicated Education team, separate from the general GitHub Support queue. Even though individual "general" support tickets for Student Pack rejections are closed, you can still file a ticket at support.github.com/contact and specifically select the "GitHub Education" / Student Developer Pack category — that routes to Education reviewers rather than the generic queue.
2. 2. Flood/disaster circumstances are worth stating explicitly in that ticket (noting that physical re-documentation isn't currently possible), since the Education team does make manual exceptions for extenuating circumstances — the automated bot alone has no way to know that context.
3. 3. Re-check that your document's dates, name spelling, and school code are 100% consistent across the document and your GitHub profile/billing info — mismatches (even minor ones like initials vs. full name) are the most common cause of auto-rejection.
      One correction to @prathamgosai's otherwise solid checklist above: point 5 ("wait for manual review... individual support tickets are no longer accepted") reads as a bit contradictory — if tickets aren't accepted, there's nothing to passively "wait" on. To be precise: GitHub shut down the old 1:1 general support path for routine Student Pack questions, but a manual review/appeal route still exists via support.github.com/contact under the Education category — so the actionable step is to actively file there, not just keep checking email. Also worth flagging: there's no officially documented "wait 48–72 hours before retrying" rule from GitHub; that's anecdotal advice, not confirmed policy, so I wouldn't treat it as fact.

Also, strongly agree with the earlier warning: never share your documents or personal identifiers with anyone claiming to "manually verify" you outside GitHub's official domains — this thread is public.