Remote family
visits.
Create a more dignified shared visit when travel or health constraints keep families apart.
The opportunity
Design for the moment that matters.
What breaks today
Phone and tablet calls require someone to hold a device and can make a vulnerable person feel like a task on a screen. Families struggle to share a stable, natural conversation.
The presence pattern
A prepared Space places the remote family at a comfortable scale and eye line, with simple controls and staff support for consent, scheduling and privacy.
Design requirements
Make it useful before making it magical.
- 01
State the boundary
Disclose whether the presence is educational, administrative, human-led or AI-assisted and what it cannot do.
- 02
Protect privacy
Minimize collected information, obtain appropriate consent and design the room for confidential conversation.
- 03
Escalate safely
Make qualified human help, emergency guidance and session termination easy to reach.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Hospitals and care communities should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for visit completion.
- 02
Invite with clarity
Before the remote family visits 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 prepared Space places the remote family at a comfortable scale and eye line, with simple controls and staff support for consent, scheduling and privacy. 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 visit completion, setup time, family satisfaction. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Visit completion
Define the starting event, completion event and current-workflow baseline for visit completion. Count only observable outcomes.
Setup time
Review setup time by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Family satisfaction
Set a minimum threshold for family satisfaction 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 remote family visits 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 remote family visits until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Hospitals and care communities 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 Remote family visits, 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
- Hospitals and care communities
- Experience family
- Health & wellness
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow