Hear what students need before the flag shows up.
Journey gives every student one text thread that actually helps. It remembers what they are working toward, nudges a useful next step when their calendar opens, answers questions on the spot, and brings in Wayne support when a person is the better answer.
Illustrative Wayne State readout. A pilot should answer a simple question: are students getting unstuck sooner?
Trusted by universities
What the student actually gets
Not another list of links. Help in the moment.
Sometimes help is a Wayne resource. Sometimes it is a 25-minute focus block. Sometimes it is “you’re free at 4:10 and this starts at 4:30.” Sometimes the student just asks. Journey handles all four in the same thread.
Illustrative demo. Wayne controls the approved information, resources, people, and schedule context Journey can use.
What would make this semester a win?
Start with their answer, not ours.
Where could you use a hand right now?
One answer helps Journey pick the kind of help that fits.
What should Journey know about your day?
Good timing beats more messaging.
Start with what this student wants.
A goal, one current friction point, and a little schedule context is enough to start. Journey learns the rest by listening.
Help them get unstuck.
If a student says “I can’t focus,” the first answer does not need to be a link. It can be one small behavior they can do now.
Catch the student when they can act.
The same nudge hits differently at 4:00 after class than at 1:15 in the middle of it. Journey uses the calendar as part of the help.
Let the student ask.
Students do not need to wait for the next campaign. They can text the question the second it shows up.
Ask what changed.
People change. Goals do too. One short check-in keeps the next nudge useful and gives staff a fresher signal than last month’s profile.
Turn context into the next rep.
Journey knows focus has been rough. It knows the student has an hour. So the nudge can be specific enough to act on.
Do not reset to zero next term.
Journey remembers the student’s goals, questions, what worked, and when a human helped. The next semester starts with context.
What Journey did, in plain English.
It listened. Helped with a behavior. Answered a question. Used the calendar. Connected Wayne support. Learned what changed.
Before the retention number moves
Students usually tell you before they leave.
The problem is not that Wayne lacks data. The earliest signals are often human: “I’m lost.” “I don’t know anyone.” “I’m behind.” “I can’t afford this.” Journey gives those signals somewhere to land while there is still time to help.
Registered does not mean settled.
A student can still be enrolled and already wondering if this is working. Journey gives that uncertainty somewhere to show up before it becomes an absence, a withdrawal, or a flag.
Sometimes the next step is a behavior.
“I can’t focus” may need 25 clean minutes. “I feel alone” may need one text to another human. Journey helps with the thing before defaulting to a portal.
When Wayne is the answer, make Wayne easy.
Tutoring. Warrior One-Stop. A coach. A Peer Success Partner. A campus event. If Wayne has the right help, Journey puts it one move away.
How Journey decides what to do
Listen first. Then help with the smallest useful thing.
Journey does not need another blast campaign. It listens for the need, checks the context, and picks the lightest intervention that can actually help.
Hear it in their words
Students tell Journey what they want, what is hard, or just ask the question. No new portal. No waiting for the next survey.
Know enough to be useful
Goals, recent replies, preferences, and approved schedule context help Journey choose what fits this student right now.
Do the next useful thing
Coach a behavior. Answer the question. Surface a Wayne resource. Bring in a person. Stop when the job is done.
One thread. Four jobs.
Four ways the same thread helps.
Tap through it. The point is not texting. The point is what the student can do next.
What sits underneath retention
Retention is downstream. These are the things you can improve now.
Journey will not claim one text kept a student enrolled. It will show you the smaller things it can influence: students speaking up, taking action, getting answers, reaching people, and building enough momentum to keep going.
Student voice
The student says what is hard while it is still small enough to help.
Small action
Journey turns the need into one thing the student can actually do next.
Answer or connection
The answer arrives in-thread, or the student reaches the right Wayne person or resource.
Belonging & momentum
Small wins build confidence: I can ask. I can act. I can find my way around.
Persistence
Wayne watches what happens downstream without pretending one touchpoint did all the work.
What Wayne can measure
Measure the stuff Journey can actually move.
Replies. Next steps. Questions answered. Wayne connections. Human handoffs. Then look at persistence downstream without pretending a single nudge did all the work.
Voice
Students tell you
Who answers, what they need, what they ask, and what changes over time.
Behavior
Students do something
Focus blocks, study starts, social moves, goal reps, and the small actions that build momentum.
People
Students get human touch
Questions resolved, Wayne resources reached, and handoffs that land with the right person.
Persist
Students keep moving
Compare persistence by cohort while keeping the causal claim honest: retention has many inputs.
Students answered. Then they acted.
At New Haven, 74% of students engaged with Journey in a typical week and 100+ campus resource connections were confirmed across one cohort. Retention also rose sharply in the high-risk group. We show all three because the first two are what Journey directly touches; the last is the outcome everyone cares about.
Same engine. First-year student success.
“Universities are clumsy with how they communicate. Journey is the first thing I’ve seen that students actually answer.”
Jens Frederiksen · President · University of New Haven
What Wayne is going to ask
Six questions worth asking.
Isn’t this just another texting tool? +
No. Text is the interface, not the product. The product is the context behind the thread: what this student wants, what changed, what they ask, what helps, and when they can act.
That context lets Journey coach a behavior, answer a question, surface a Wayne opportunity in a real free window, or bring in a person. The clean first test is alongside the tools Wayne already uses, with one cohort such as Warrior 360.
What does my team actually see? +
The human signals that usually arrive late: what students are trying to do, where confidence is slipping, what questions keep coming up, which nudges help, where belonging is changing, which Wayne resources get used, and who is asking for a person.
Staff can move from the cohort pattern into the individual context needed for a follow-up, so the conversation starts closer to the truth.
Does this replace our coaches or Peer Success Partners? +
No. It gives them better context. Warrior 360 already provides the human structure. Journey listens between those touchpoints, helps with the small stuff, and surfaces the moments where a person matters more.
The win is simple: the right student reaches the right Wayne person sooner, and that person knows more when the conversation starts.
How much work is this to stand up? +
Keep the pilot narrow: one cohort, a roster, the schedule context Wayne is comfortable providing, and a map of the approved information, resources, and people Journey can use. That is enough to test the behavior, timing, Q&A, and handoff model before a heavy integration.
Ongoing, your team works a short signal queue and the human follow-ups you already want to make.
What about FERPA and security? +
Journey is FERPA-ready and processes student data only under a written agreement with Wayne State for the educational purpose Wayne authorizes. SOC 2 certification is in progress.
Staff see the context needed to help, not unnecessary private-message exposure. We walk IT, counsel, and Student Success through the data flow and controls before launch.
How will we know if it works? +
Agree on the score before the pilot starts: student response, goals captured, next-step actions, questions answered, Wayne connections, belonging and engagement signals, successful human handoffs, and whether staff found the signals useful.
Then look at persistence downstream. Journey does not need credit for every outcome to prove Wayne heard students earlier and helped them act sooner.
Start with one cohort. Prove the next step gets better.
Give Journey one Wayne State cohort. Let it listen, coach, answer, time the nudge, and bring in Wayne support. Then look at what students did, what your team learned earlier, and whether the cohort kept moving.