Education 5 min read

Start of term: when a campus front desk meets 2,000 students

Enrolment week compresses a term of admin into five days. The queue is not the problem — the fact that four departments each run their own is.

Customer flow · Education
PEAKTerm beginsEnrolment, fees, IT, visas at once
TOKENPick a categoryCurrent or prospective student
CSPick a serviceStudent services, finance, IT, advising
SMSWait anywhereLibrary, cafeteria, next lecture
FSCounterRouted to the right department
NPSRate itBy department, not by campus

A university front desk has a demand curve unlike any other service operation: for roughly five days a year, it does about a third of its annual volume. The rest of the year it is quiet enough that the enrolment-week experience is what students remember.

Four departments, four queues, one corridor

Student services, finance, IT and academic advising are usually separate teams with separate systems, often in the same corridor. A new student needs three of them and does not know it. So they queue for the first, are told to see finance, queue again, and are told they need an IT account first.

The sequencing problem is the same one public service halls have — and so is the fix. One token, several desks, and a board that tells the student where to go next rather than making them find out by queueing.

Two questions, not a form

The intake that works at scale is short. Are you a current or a prospective student? What do you need? That is enough to route accurately, and it is short enough that a queue of two hundred people does not stall at the kiosk.

Everything else — student number, programme, document upload — can be collected while they wait, on their own phone, rather than at the front of a line.

Prospective students are a different service

An enquiring applicant and an enrolled student have different needs, different staff and different urgency. Separating them at the first question stops admissions conversations from queueing behind a fee payment — and stops a prospective student’s first experience of your campus being a forty-minute wait.

Give the wait somewhere to go

A campus has something most service environments do not: places students actually want to be. A token on the phone means a student can wait in the library, the cafeteria or a lecture, and walk over when they are called.

The corridor empties, which matters more than it sounds — a visible queue of two hundred people is its own deterrent, and some of the students who walk away are the ones who needed help most.

Plan next year with this year’s data

Enrolment week is the most predictable crisis in the academic calendar, and the least well-instrumented. One term of token data gives you the shape of it: which day peaks, which service runs longest, how many students needed more than one desk, and where the abandonment happened.

That converts next year’s staffing from an argument into an arithmetic problem.

What to measure

  • Peak by day and hour across enrolment week, not averaged across the term.
  • Multi-department journeys. How many students needed two or more desks.
  • Abandonment, especially among prospective students.
  • Score by department, so a struggling team gets support rather than a campus-wide average.

Want this flow for your building?

A 30-minute walkthrough using your services and counters.

Book a demo