Fixed welcome
Wait at a visible reception point.
Headquarters visitor guidance solution
Choose a destination at the welcome point.Follow the robot along an authorized route.
The robot waits at a fixed welcome point. Visitors or staff select a destination on screen to start route guidance and arrival messages.
Start
Visitor / staff
Select a destination or tour at the service point.
Guide
Robot
Lead along the route and play checkpoint content.
Arrive
Reception staff
Confirm arrival and continue the human service.
Pilot the documented workflow with responsible staff verifying key handovers.
The service
Service flow and ownership
Robots execute configured tasks; responsible staff retain verification and on-site response.
Visitor / staff
Start
Select a destination or tour at the service point.
Platform
Dispatch
Create a task from configured destinations and routes.
Robot
Guide
Lead along the route and play checkpoint content.
Reception staff
Arrive
Confirm arrival and continue the human service.
Managers
Review
Review tasks and maintain routes and content.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Roles
Reception staff
Start service, check destinations and continue reception.
Robot
Guide and announce along configured routes; report task status.
Managers
Maintain locations, routes, scripts, accounts and exception procedures.
Service modes
Select modes for the workflow; agree extensions separately.
Screen-started guidance
Visitors or staff choose a destination.
Content configuration
Configure welcome scripts, branding and route announcements.
The robot does not approach visitors proactively. Facial identity verification, ID scanning, badge issuance and security clearance are not default functions.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
Guidance terminal / web
Manage locations, routes, tasks, devices and records.
Optional interfaces
Assess visitor systems, doors and lifts against actual fields and scope.
Suitability
Scenario fit
The robot waits at a fixed welcome point. Visitors or staff select a destination on screen to start route guidance and arrival messages.
Fixed welcome
Wait at a visible reception point.
Screen-started guidance
Visitors or staff choose a destination.
Content configuration
Configure welcome scripts, branding and route announcements.
Where the service helps
Coordinate routes, content and staff around these tasks.
| Service area | Service scope |
|---|---|
| Fixed welcome | Wait at a visible reception point. |
| Screen-started guidance | Visitors or staff choose a destination. |
| Content configuration | Configure welcome scripts, branding and route announcements. |
Coordination priorities
Reduce repeated trips
Assign suitable repeated routes to robots and compare results in the pilot.
Clear handovers
Verify outcomes against task, destination and responsible role.
Operational review
Use task states and exception records to adjust routes, schedules and configuration.
Building route
Routes and service points
Configure routes for the actual site; diagrams explain the workflow.
Welcome point
Wait without pursuing or approaching people.
Authorized route
Configure around floors, doors and lifts.
Destination
Announce arrival and hand over to reception staff.
Locations
- Welcome point
- Authorized route
- Destination
Validate a complete loop
Welcome point → Authorized route → Destination
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Site readiness and operations
Confirm site, equipment and staffing; verify interfaces per project.
Human handover
Staff verify visitors, permissions and reception after arrival.
Later reuse
Validate any off-peak patrol, environment or display role separately.
Commission configured interfaces, notifications and access; assign site contacts and staff fallback.
Suggested readiness checks
Swipe horizontally to see all columns.
| Item | Scope | Confirmation |
|---|---|---|
| Scope and points | Welcome point, Authorized route, Destination | Confirm accessible scope and responsible staff on site. |
| Routes and access | Maps, passages, doors/lifts, network and charging. | Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests. |
| Handover and exceptions | Reception staff, Robot, Managers | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
The source recommends one or two robots and a web management platform; start with welcome-to-frequent-destination routes.
Guidance terminal / web
Manage locations, routes, tasks, devices and records.
Optional interfaces
Assess visitor systems, doors and lifts against actual fields and scope.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Welcome point, Authorized route, Destination |
| Staff coordination | Allow for available receiving, reviewing and exception-response staff. |
Source configurations/data refer to their stated scenario; confirm final sizing through site validation.
Pilot & operation
Suggested implementation
The following are project assessment and acceptance suggestions, subject to site confirmation.
Confirm scope
Site preparation
The source recommends one or two robots and a web management platform; start with welcome-to-frequent-destination routes.
Configure and commission
When ready
Check devices, routes, points, accounts and necessary access/system interfaces.
Trial and acceptance
By project agreement
Validate real tasks, staff coordination, exceptions and records before expansion.
Suggested exception handling
The following are project assessment and acceptance suggestions, subject to site confirmation.
View the exception checklist
Swipe horizontally to see all columns.
| Condition | Action | Ownership and records |
|---|---|---|
| Task cannot continue | Pause, wait or hand over to staff under site rules. | Managers record cause, owner and recovery conditions. |
| Handover/review incomplete | Contact the assigned staff; automatic task closure does not replace their confirmation. | Record the reason and follow-up. |
| Device/access exception | Follow support procedures and use staff service if required. | Support and site staff coordinate and validate recovery. |
Suggested acceptance
The following are project assessment and acceptance suggestions, subject to site confirmation.
View acceptance measures and responsibilities
Swipe horizontally to see all columns.
| Check | Status | Verification |
|---|---|---|
| Task execution | Suggested acceptance item | Complete tasks within agreed routes/scope and record success, failure and reasons. |
| Staff coordination | Suggested acceptance item | Verify notification, permissions, human review/handover and exception takeover. |
| Operational records | Suggested acceptance item | Sample tasks, times, points and outcomes; agree metrics and targets with the project team. |
Agree before delivery
Service scope
The robot does not approach visitors proactively. Facial identity verification, ID scanning, badge issuance and security clearance are not default functions.
Responsibilities
Reception staff, Robot, Managers
Configuration and metrics
Agree device models, options, interfaces, timing and targets in project documents.
Questions
Related equipment
Review product information and reconcile the document version with the supplied model/configuration.
View productDocument configuration and device checks
- Guidance terminal / web
- Manage locations, routes, tasks, devices and records.
- Optional interfaces
- Assess visitor systems, doors and lifts against actual fields and scope.
Common questions
Where should the pilot start?
The source recommends one or two robots and a web management platform; start with welcome-to-frequent-destination routes.
How do robots and staff share work?
Reception staff：Start service, check destinations and continue reception. Robot：Guide and announce along configured routes; report task status. Managers：Maintain locations, routes, scripts, accounts and exception procedures.
What needs separate confirmation?
The robot does not approach visitors proactively. Facial identity verification, ID scanning, badge issuance and security clearance are not default functions.
How are configuration and acceptance set?
Use source recommendations as a starting point, then confirm against site routes, supplied equipment and trial data. Suggested checks do not establish fixed performance or service guarantees.
Pilot preparation
The source recommends one or two robots and a web management platform; start with welcome-to-frequent-destination routes.
Scope and points
Welcome point, Authorized route, Destination Confirm accessible scope and responsible staff on site.
Routes and access
Maps, passages, doors/lifts, network and charging. Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptions
Reception staff, Robot, Managers Agree notifications, staff takeover, records and review rules.
Related solutions
Choose a dedicated solution for each workflow.
Headquarters meeting supplies delivery
Deliver documents and refreshments before meetings, ad hoc supplies during sessions and permitted returns afterwards, with staff handover outside meeting rooms.
Headquarters comprehensive item delivery
Connect headquarters reception, employees and floor service points through reservations, loading, arrival notifications, authorized collection and redelivery.
Building welcome and guidance solution
Visitors select destinations on screen at reception; robots guide along configured routes with voice, screen and brand content.