The Experience Suite
Student Loop · Keep students in the loop

The question they were too unsure to ask.

Every student has one. Where do I park. Am I allowed to bring my mum. Have I actually enrolled. Who do I tell that I am struggling. They will not ring a switchboard to find out, and most of them will not email either. Student Loop answers in seconds, in your voice, at two in the morning, and quietly tells your team what it learned.

  • 📅 Open Day
  • 🎓 O-Week
  • ✨ All year
  • 🔄 Writes back to your CRM
  • 🤝 Hands over to a human
SL

Student Loop

Answering as your university · demo content

One concierge, three moments

the same student, eighteen months apart
📅

Open Day

Before they come, it plans the day around what they actually want to study. On the day, it is the volunteer who never gets tired, never has a queue and knows where the toilets are.

🎓

Orientation

The fortnight where confusion turns into attrition. It walks them through enrolment, timetables and census date, and notices the ones who go quiet.

✨

All year

Extensions, placements, fee trouble, exam timetables, and the harder conversations. It knows what it is not qualified to answer, and hands those to a person fast.

2amPeak question time
<4sMedian answer
1Voice, every channel
0Questions left on read

Figures above are illustrative placeholders for the demo, not measured results. Replace with your own once a pilot has run.

What it feels like, and what it gives you

the student’s side, and your team’s
👩‍🎓 For students

Someone who is always up

  • No wrong question. It is built for the ones people are embarrassed to ask out loud, which is most of the important ones.
  • It does the thing, not just the answer. Sessions go into a plan, the plan goes into their calendar, the reminder arrives the night before.
  • It sounds like the university. Your tone, your names for things, your campuses. Not a bot bolted onto the corner of a page.
  • It knows when to stop. Money trouble, safety, mental health: it stops answering and connects them to a person, with the context already written up.
  • Wherever they already are. Web, SMS, WhatsApp, the app, a QR code on a lanyard. Same concierge, same memory.
🏛️ For your team

The switchboard that reports back

  • Volume off the front desk. The repetitive eighty percent is handled, so your people spend their day on the twenty that needs a human.
  • Zero party signal. What they asked is the intent data: study area, campus, start year, worry, blocker. Volunteered, not inferred.
  • It writes back. Every exchange updates the contact record and can trigger the next comm, so nothing dies in a chat log.
  • You see the gaps. The unanswered questions are a live list of what your website does not say clearly enough.
  • Governed, not improvised. Answers come from sources your team owns and approves. Out of scope goes to a human by design.
For your team: it is one control centre, not another inbox.

One conversation for students. One control centre for you.

how it runs
Answers

Grounded in your content

It reads what you already publish: course pages, the Open Day programme, the O-Week schedule, policy, FAQs. If a source is not approved, it is not an answer.

For your team: update the page, the concierge updates.
Handover

To a human, with context

Escalation carries the transcript, the detected need and the urgency, so the student never repeats themselves and your staff member starts three steps in.

For your team: fewer cold starts, shorter calls.
Systems

Reads and writes

Reads the timetable, the programme and the student record where you allow it. Writes interest, consent and outcome back to the CRM and marketing automation.

For your team: the conversation becomes a record.
Channels

Everywhere they already are

Embedded in your site, on a campaign landing page, behind a QR code on campus, or over SMS and WhatsApp during the event itself.

For your team: one build, every surface.
Guardrails

Knows its limits

Wellbeing, disclosure, complaints, anything legal or financial: routed, not answered. Wording for those pathways is written with your student support team.

For your team: risk handled deliberately.
Reporting

Reports as it goes

Themes, volumes, sentiment, drop off, unanswered questions and handover reasons, by cohort and by moment.

For your team: next year’s comms plan writes itself.

The three moments, joined up

The suite already covers the two dates a university budgets for and the aspiration that runs underneath them. Student Loop is the thread between them: the same assistant that helped them plan Open Day is the one that walks them through enrolment, and it remembers.

Open Day ExperienceThey build the day
UniLoop ImagineThey picture the life
Orientation ExperienceThey arrive knowing what happens
Student LoopThey can ask anything, at any point
UniLoop Control CentreYour team runs all of it
Your systemsCRM, CMS, timetable, student record

What this page is. The concierge above is a working demonstration running entirely in your browser. Its answers are scripted against a fixed demo knowledge base with a demo campus, demo sessions and demo dates, so it can be sent as a link and opened anywhere with nothing to install. A live deployment is the connected build: your content as the source, your systems read and written, your staff on the other end of a handover.

See it answering your questions, not ours

Send us the twenty questions your front desk is sickest of, and we will come back with this same concierge answering them in your voice.

uniloop.com.au ↗
⟳ UniLoop Interactive