Faculty verification repeatedly auto-rejected despite exact matching employment certificate

[thasanin]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Re-verification/Repeat Application

Hi everyone,

Hello GitHub Education Team,
I am experiencing repeated, immediate rejection of my GitHub Education faculty verification application.
I have already addressed every issue listed in the rejection notices.
My institutional email is verified, and GitHub correctly recognizes and associates my academic institution with that email domain.
The photo has very low resolution, and I think your automated system can't verify the document I'm uploading
I have carefully checked all of these items, and they do match.
I also followed the instructions to update my profile, log out and log back in, and submit a newly issued official employment certificate.
When I try to contact GitHub Education Support using “Application not approved (faculty)”, the support form states that individual manual reviews and status updates are no longer provided, so I am unable to submit the issue through that route.
Because the rejection occurs almost immediately and reports missing information even though it is visibly present in the document, this appears to be an automated document-recognition or verification issue.
Could GitHub staff please advise whether there is a supported way to escalate or investigate an apparent technical failure of the faculty verification process?
I can provide the original official employment certificate privately to GitHub staff if necessary.
Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐