Welcome to Agentic Faculty Assistant thatanswers a professor's question out of the institution's record.
Faculty live in the LMS, and the institution lives everywhere else. Risely's agents answer a professor's question from the record itself, cite what they read, and draft the next step. The professor approves before anything sends.
Faculty assistant · BIO-210
listening
the professor:
Every answer names the record it came from.
Risely's agents read the roster, the gradebook, and the advising caseloads, then show which line of the answer came from which system. A confident sentence with nothing behind it is worth nothing to a professor.
What the answer was read from
0/3
Section roster
who is enrolled, and who stopped submitting
Gradebook
the fall from 81 to 58 on the midterm
Advising caseloads
no case open on either student
A confident sentence with no source behind it is worth nothing to a professor. Every line of the answer points at the system it was read from.
The first check is whether somebody already acted.
Before anything drafts, Risely's agents look for an open case, an earlier flag, and a colleague who raised the same student last week. A second case is how a student ends up with two advisors and no plan.
Checked before anything drafts
A colleague raised the same student last week, so this concern joins that case rather than opening a second one.
Duplicate cases are how a student ends up with two advisors and no plan. The first question Risely's agents ask is whether anybody is already on it.
The assistant reaches the professor's own sections and nothing else.
Risely's agents run inside the permissions that professor already holds. Colleagues' sections, personnel files, and evaluation records all sit outside that reach, and no question about a colleague's teaching is one they can answer.
What it reaches
In reach
- · the sections this professor teaches
- · the students on those rosters
- · forms and deadlines the office publishes
Out of reach
- · another professor's sections
- · personnel and evaluation records
- · anything the professor could not already open
The assistant works inside the permissions the professor already has. It reads the record faster than a person can, and it reaches nothing a person in that role could not open today.
One question replaces the hunt for the right form.
Half the administrative load on faculty is working out which office owns a thing. Risely's agents return the form, the deadline, and the owner together, with this section's details already filled in.
"How do I give a student an incomplete?"
Half the administrative load on faculty is finding out which office owns a thing. One question returns the form, the date, and the owner together.
One thing moves. The record answers.
A grade posts, a submission stops, a colleague raises the same name. Any of them changes what a professor should know, and every one runs the same way.
A professor asks one question
typed between two classes
The record answers
roster, gradebook, and caseloads, read at once
Two flags draft themselves
the evidence attached to each
The professor approves the send
one tap and nothing automatic
Advising sees both the same hour
and the professor gets told what happened
What changes, and how it runs.
A professor's question gets a real answer
Read out of the record, with the sources named.
What one professor noticed reaches the offices that act
The flag lands with its evidence the same hour.
Nothing sends without the professor
Every drafted step waits for an approval.
The technical read
Connects read-only to your LMS, SIS, and advising caseloads to start
Scoped to the permissions the professor already holds
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.