01
AccessWhich students should join?
Confirm the intended audience and supported institutional email domains.
For university leadership & student-life teams
Define the campus boundary.
Start with one useful use case.
A university partnership defines which students can join with supported institutional emails, which LinkUp use case starts first and who coordinates campus questions during the pilot.
What the university decidesWho can join.
What starts first.
Who supports the pilot.
What starts first.
Who supports the pilot.
The university role
Three decisions before
a campus pilot.
LinkUp operates the product. The university helps define the campus boundary and support model.
02
First use caseWhich student need should start first?
Choose student deals, shared journeys or read-only campus information as the focused starting point.
03
SupportWho owns campus questions?
Name the university and LinkUp contacts who will coordinate the pilot and support students.
A focused partnership
From campus need
to a limited pilot.
Start small, make ownership explicit and review what the first phase teaches both teams.
- 01Campus conversation
Identify the priority and intended student audience.
- 02Written pilot brief
Record supported domains, the first use case and responsibilities.
- 03Limited launch
Start with the agreed audience and support path.
- 04Joint review
Review feedback, support issues and whether a next phase makes sense.
What LinkUp brings
Product, launch support and a clear contact.
The university defines the campus context. LinkUp prepares and supports the agreed product experience.
01Product scope shaped around one student need
02Access setup for agreed supported domains
03Launch guidance for the intended audience
04A joint review conversation after the pilot
University partnership
Tell us the campus need you want to explore.
Share the intended student audience, supported domains, first use case and campus contact.
Useful contextYour campus · the students you want to support · one clear need