CampusMind Retention brings the early signals already in your LMS, SIS and CRM together for every student. Agents flag who could use support and draft the outreach. Your advisors decide what goes out.
The first signs show up weeks earlier: a quiet week in the LMS, a missed lab, a financial aid form left open. Each one lands in a different system, in front of a different person.
By the time anyone connects them, there are fewer ways left to help.
Retention agents do the watching and the drafting. Your advisors keep the judgment and the relationship.
Link your LMS, SIS and CRM and choose exactly which data the agents can see. Credentials are encrypted and never shown again after saving.
Detection agents watch for missed work, grade trends, disengagement, holds and registration gaps, then add up a score your team can read.
Action agents draft one consolidated message per student. An advisor edits and approves it before anything is sent.
Signals, emails, replies and meetings sync back to your CRM, so every advisor sees what has already been tried.
Each active signal adds the points your institution configured. The total maps to a response your team defines, so an advisor can always see why a student was flagged.
Example signals and timing. Each is a reason to check in, not a withdrawal prediction.
The score is the sum of every active signal's points.
Configured points, not a probability. Example bands; your institution sets the boundaries.
Detection agents surface who could use support. Action agents handle the follow-through. You choose which ones run.
One work queue, ranked by risk, with the evidence behind every flag. Agents draft the message. Your advisor edits and approves it. Only then does it send.
From his own advisor, at a reasonable hour, with one clear next step.
Signals, emails and meetings sync to your CRM, so the next advisor sees what has already been tried.
You choose what the agents see, when they reach out, and when a person steps in.
Each connection shares only what you switch on.
Every value is an example. Your institution sets its own.
For example, pause outreach during a medical leave.
Flagged in week 4. Supported by week 5. Registered for spring.
Retention fits into the advising workflow you already have. It doesn't ask students or staff to learn a new system.
See where support is needed across the term, with rules and thresholds your team owns.
Start each day with a ranked queue, the evidence behind each flag, and a draft ready to personalize.
Open holds and registration gaps reach an advisor instead of waiting in a separate queue.
Hear from a person they know, at a reasonable hour, with one clear next step.
No. It adds up configured points for observable signals, like a missed assignment or an open hold. It's a reason to check in, not a probability.
Agents draft outreach and queue it for review. An advisor edits and approves each message before it sends, and your team decides what each response band does.
Your LMS, SIS and CRM, such as Canvas, Workday and Slate. You choose which data each connection shares.
Contact limits, quiet hours and a recheck before every contact. If the student already replied or the need has passed, the message doesn't go.
Your institution. Every trigger's scope, condition, weight and response is configurable.
Talk with our team about your advising workflow, your systems and the signals that matter most on your campus.