Why education inboxes are different
Coursework, cohort announcements and admin mail all compete for attention. Here is how we structure the inbox around them.
The three streams of campus mail
Every student inbox carries three very different kinds of message, and treating them identically is the fastest way to lose an assignment deadline.
- Coursework — submission receipts, feedback, grade notifications
- Cohort announcements — timetable changes, room moves, cancellations
- Administration — enrolment, fees, library and IT notices
Why generic clients struggle
Consumer mail clients optimise for one person with one identity. A student has a personal identity, a course identity, and often a department identity, all landing in the same place.
Sorting by sender is not enough. Sorting by intent is what actually reduces missed deadlines.
How we model it
We attach a lightweight classification to every inbound message at ingest time:
type MailIntent = "coursework" | "announcement" | "admin" | "other";
function classify(headers: Headers): MailIntent {
if (headers.get("x-course-id")) return "coursework";
if (headers.get("list-id")) return "announcement";
return "admin";
}Classification happens before the message is written, so the inbox never has to re-scan history.
Reading time matters
Students triage on a phone between lectures. Every view in InstantEduMail is designed so the first screen answers is this urgent? without a tap.
What comes next
We are working on per-course folders that materialise automatically from the classification above. Subscribe below if you want the release note.
About the author
Maya Oduya
Head of Deliverability
Maya spent eight years running mail infrastructure for university systems before joining InstantEduMail. She writes about SPF, DKIM and the unglamorous work of landing in the inbox.
All posts by Maya OduyaComments are coming soon
We're wiring up a moderated discussion thread for each post. Until then, reply by email and we'll add good questions to the article.
Send us a note