Welcome to Agentic Case Management thatopens one case when three offices flag the same student.
A warning lands, and Risely's agents open the case, route each step to the office that owns it, and revive any step that goes quiet. Every message to a student waits for a person to approve it.
Case file · one student
38 open cases · all owned
Opened on a mid-term warning from her instructor. Four steps, four offices, one record everybody reads.
read the case ledger · no tutoring session logged since Tuesday
checked the Learning Center calendar · an open slot on Thursday
drafted the follow-up · the slot is held, not booked
"Tuesday's session slipped. I held a new spot for Thursday, and I would like to help you keep it."
held for advisor approval
When the case closes, the instructor who raised the warning learns what happened, once, on the same record.
Three flags in one week open one case.
Her instructor files a mid-term warning, the risk model crosses her line, and she emails the front desk, all in the same week. Risely's agents merge every one of them onto the case that is already running, so three offices never work the same student three times.
This week's flags
same student
One case, already open
All three land on the record that is already running. Nobody works this student three times.
A step with nobody's name on it is the step that stalls.
The aid consult belongs to an officer, the schedule change to her advisor, the tutoring slot to the Learning Center. Risely's agents put a role and a clock on each one, and the step that goes quiet shows itself.
Who owns what
one open case
A step with nobody's name on it is the step that stalls. Every step here carries a role and a clock, and the quiet one shows itself.
The session that never happened gets caught the same week.
Nobody reports a no-show. Risely's agents read the case ledger, find the gap on Wednesday, hold an open slot on Thursday, and draft the message that asks her to keep it.
One step, one week
tutoring
Nobody reported the no-show. Risely's agents read the case ledger, found the gap, and held a new slot before the week ended.
The loop closes to whoever raised the flag.
The instructor who filed the warning hears how it ended. So does the Learning Center, and so does her advisor. People keep reporting what they notice when they can see that the last report worked.
Each of them hears how it ended
case closed
People raise flags again when they hear how the last one ended. The closing note is what keeps the campus reporting.
One thing moves. The case re-plans.
A missed session, a cleared hold, a grade that finally posts. Any of them changes what the case still owes the student, and every one runs the same way.
A tutoring session slips
Tuesday's booking never happened
The case notices by Wednesday
no session logged on the record
A new slot gets held
a Thursday slot from the Learning Center calendar
The follow-up waits for a person
an advisor reads it and sends it
The loop closes to the instructor
the flag they raised got answered
What changes, and how it runs.
Every case gets followed through
Each step carries an owner, and a stalled one comes back the same week.
Offices stop guessing who called
Everyone who holds a step in the case reads the same record.
Help lands while the term can still be saved
The fix arrives while it is still small enough to work.
The technical read
Connects read-only to your SIS, LMS, and bursar ledger to start
A person approves every send
Every action lands on an append-only log
Runs alongside what you have. Nothing rips out.