Campus
welcome.
Give new students a friendly, consistent arrival point across large or distributed campuses.
The opportunity
Design for the moment that matters.
What breaks today
Orientation information is abundant but fragmented. New students often need reassurance and a simple next step more than another map or portal.
The presence pattern
A student ambassador or digital host welcomes the newcomer, answers approved questions, shows relevant routes and connects a live campus resource when needed.
Design requirements
Make it useful before making it magical.
- 01
Teach one objective
Anchor each experience to a specific skill, concept or decision rather than broad entertainment.
- 02
Keep learners active
Alternate explanation with observation, discussion, practice and visible feedback.
- 03
Support the instructor
Give the local educator control over pacing, context, access and recovery.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Student affairs and campus operations should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for questions resolved.
- 02
Invite with clarity
Before the campus welcome experience begins, explain why the presence is there, whether it is live, recorded or AI-assisted, what it can do and how a participant can leave or reach a person.
- 03
Operate the moment
A student ambassador or digital host welcomes the newcomer, answers approved questions, shows relevant routes and connects a live campus resource when needed. The operator should be able to observe state, recover the session and protect the physical activity already happening in the room.
- 04
Close the loop
End with a visible next step, capture only consented information and record questions resolved, correct destinations, new-student confidence. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Questions resolved
Define the starting event, completion event and current-workflow baseline for questions resolved. Count only observable outcomes.
Correct destinations
Review correct destinations by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
New-student confidence
Set a minimum threshold for new-student confidence before launch. Name the owner and recovery action when a session misses it.
Decision gates
Know when presence is—and is not—the answer.
Presence must earn the room
If the same campus welcome outcome can be achieved by a well-designed phone, kiosk or conventional video call with equal trust and clarity, use the simpler tool.
The boundary must stay visible
Do not launch campus welcome until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Student affairs and campus operations should be able to run, pause, recover and measure the experience repeatedly. Do not scale while success depends on a founder or engineer standing beside it.
Evidence status. This page is a product-design field brief, not a claim that Reality Relay has already produced the stated customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.
Build the first pilot
Start narrow enough to learn.
For Campus welcome, begin with one real environment, one defined audience and one repeatable interaction. Establish who operates the experience, what information or tools it can access and exactly when a person must take control.
Reality Relay Platform coordinates content, session state, approved intelligence and operations. Reality Relay Spaces give the experience a calibrated physical endpoint with intentional scale, eye line, sound and grounding. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Student affairs and campus operations
- Experience family
- Education & training
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow