Virtual
receptionist.
Extend a warm, consistent front desk across locations without turning the entrance into a call center.
At a glance
Three decisions that shape the use case.
- 01
The receptionist’s real job is to establish trust, confirm intent and route correctly before an unattended entrance becomes a security or service problem.
- 02
Use a physical presence only when shared gaze, gesture, turn-taking or a visible role in the room improves the task. If voice, text or a conventional kiosk works equally well, keep the simpler interface.
- 03
The pilot should define a baseline and measure visitor wait time, correct routing and arrival satisfaction before anyone treats the concept as proven.
The opportunity
Design for the moment that matters.
What breaks today
Smaller sites may not justify a full-time reception team, yet an unattended entrance feels confusing and insecure. Conventional video calls make the remote host feel incidental.
The presence pattern
A remote or AI-assisted receptionist appears at an intentional eye line, welcomes the visitor, confirms the purpose of the visit and connects the right local contact.
Design requirements
Make it useful before making it magical.
- 01
Bound the role
Make the system’s job, knowledge, tools and limits clear before the interaction begins.
- 02
Show state
Listening, thinking, speaking, waiting and escalation should be visible and understandable.
- 03
Preserve control
Give operators a reliable way to observe, pause, recover and hand the moment to a person.
Operator runbook
Design the complete service—not only the scene.
- 01
Set the baseline
Before launch, define the audience, room, and baseline event this presence changes. Name the owner of each session state and the handoff path.
- 02
Invite with clarity
For the first pilot, make the purpose explicit: why this presence is there, what it can do, whether it is live or AI-assisted, and how a participant exits safely.
- 03
Close the loop
A remote or AI-assisted receptionist appears at an intentional eye line, welcomes the visitor, confirms the purpose of the visit and connects the right local contact. End every session with a visible next action, capture only consented outcomes, and run one short review before expanding to a second site.
Pilot scorecard
Prove a real outcome in the room.
Visitor wait time
Define the starting event, completion event and current-workflow baseline for visitor wait time. Count only observable outcomes.
Correct routing
Review correct routing by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Arrival satisfaction
Set a minimum threshold for arrival 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 virtual receptionist 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 virtual receptionist until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Multi-site operations teams 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 Virtual receptionist, 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. Relay Space, Relay Frame and Relay Box give each experience a calibrated physical endpoint at the right scale. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Multi-site operations teams
- Experience family
- AI & digital humans
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow