Welcome to Agentic At-Risk Flagging thatturns one typed sentence into a routed advising case.
A professor is the institution's earliest signal and its worst-connected one. Risely's agents attach the evidence, route the flag to the advisor who already holds the student, and report back what happened. Nothing waits in a forwarded email.
Early alert · one flag
listening
the professor:
step 1
drafted
step 2
professor approves
step 3
advising queue
step 4
meeting booked
step 5
professor told
The flag reaches the advisor who already holds the student.
A shared alerts inbox is where a concern goes to age. Risely's agents read the caseload, find the person who owns this student, and put the flag in front of them with a name attached to the assignment.
Where the flag lands
routing
A queue nobody owns is where a concern goes to age. Risely's agents send the flag to the person whose caseload already carries this student.
One flag is read beside everything else the record holds.
On its own it is one professor's worry. Beside an attendance dip in another course and a balance that opened last week, it reads as a student sliding across the whole term, and the advisor acts on the first signal rather than the third.
One record, three offices
Read together, these are one student sliding across the whole term rather than three unrelated bad weeks.
No single office sees enough to act. The advisor who sees all three acts on the first one.
The professor hears what happened.
A flag that disappears is a flag nobody sends twice. When the meeting books, Risely's agents send the professor a short note saying so, which is why the campus keeps its earliest signal switched on.
One flag, start to finish
back to the professor
Your flag reached her advisor on Tuesday and they met Thursday. Thank you for sending it.
A professor who never hears what happened stops sending flags, and the campus loses its earliest signal. Closing the loop is what keeps the sensor switched on.
The outreach names the actual week.
A student who is under water reads a general check-in as small talk. The drafted message names the assignments, the course, and the balance that all slipped together, and an advisor approves it before it sends.
What the advisor sends
the generic version
"Hi! Just checking in. How are classes going this semester?"
drafted from the record
"The BIO-210 assignments and the HIST-201 attendance both slipped the same week your balance opened. Can we take fifteen minutes Thursday and sort them one at a time?"
A student who is drowning reads a general check-in as small talk. Naming the actual week is what gets an answer.
One thing moves. The case redraws.
A second professor speaks up, a grade posts, an appointment gets missed. Any of them changes what the student needs, and every one runs the same way.
A second professor raises the same student
different course, same week
The concern joins the open case
no second queue and no second advisor
The picture changes shape
one rough course becomes a term-wide slide
The advisor moves the meeting up
and the outreach names the real problem
Both professors get the same note
the loop closes where it started
What changes, and how it runs.
A concern becomes a case the same day
The evidence attaches before anyone asks for it.
The right advisor gets it first
Risely's agents route to the caseload that holds the student.
Professors keep flagging
The loop closes back to the person who raised it.
The technical read
Connects read-only to your LMS, SIS, and advising caseloads to start
A professor approves every flag before it sends
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.