Catch every student before they fall behind.

It runs on top of what you already have. Students get nudges by text, so there is nothing for them to install and no new login. Your staff work inside Microsoft Teams, where Journey posts signals and handoffs to a channel they already use.

Journey reads from the systems you already run, like Banner, Canvas, Workday, Navigate, and Starfish, instead of replacing any of them. No IT project is required to start a pilot.

A 100-student pilot takes about 8 hours of staff time to set up, in total.

Most of that is resource documentation. Journey gathers what your campus already publishes, like links to the gym, counseling, tutoring, and advising. For anything we cannot find publicly, the relevant office sends us the details, and assembling those documents is the bulk of the 8 hours.

The rest is class schedules. Whoever manages scheduling spends about an hour sending us the student schedule list, so Journey can time nudges around real coursework.

After setup the ongoing load is light. Your CARE team reviews a short flagged queue and makes the warm handoffs only a person can make.

A full first-year rollout runs the same way at larger scale. Resource docs are written once and reused across the cohort, so the added effort is mostly broader schedule data and sourcing from more departments. Plan for one admin point of contact, with brief input from the registrar or IT for schedules, your CARE team for resource docs, and counseling for referral steps.

Pulse checks branch by need and route students to the right office, counseling, success coaching, advising, or financial aid, with one-tap scheduling links. A risk signal surfaces to your CARE team in Teams with the context that matters: a health score, the top risk driver, and a recommended next step.

A 48-hour follow-up reaches any student who reported distress. If they could not connect with the resource, they are flagged for direct staff outreach, which closes the loop between digital triage and a human. Journey never replaces a counselor or an advisor. It gets the student to one sooner.

During onboarding, students share their priorities, their preferred voice, their goals, and their pain points. As the relationship develops, Journey records nudge responses, engagement signals, and pulse-check answers.

Staff see signals, not transcripts. They see what a student needs, for example “struggling with chemistry, third week running,” not the underlying message, unless the student asks for the handoff. The full data dictionary, access controls, and retention policy are in Journey’s data documentation.

Journey is FERPA-ready and processes student data only under a written agreement with your institution, for the educational purpose you authorize. Under that agreement, Journey operates as a school official with a legitimate educational interest, the same basis your other vendors use. SOC 2 certification is in progress.

Records are de-identified for research and reporting. We will walk your counsel and IT team through the data-processing agreement, security controls, and retention practices before anything is signed.

In a nine-month pilot at the University of New Haven (N = 100): 74% weekly engagement, a composite holistic health score that rose from 72 to 85 across the year, a high-risk segment that fell from 17 students to 8, and more than 100 completed department connections. In a paired survey of 19 of those students, the share who said the nudges “made it easier to do what I already wanted to do” rose from 14% in the fall to 71% in the spring.

We also publish what we have not yet proven, the small-sample caveats and an honest product-market-fit read, on the research page.