Skip to content

Organize reception and exhibit tours.Connect explanations with expert handover.

Connect welcome, route selection, exhibit explanations, multi-stop tours and expert handover using approved screen, voice and multimedia content.

Illustrative robot service scene
  1. Start

    Visitor / staff

    Select a destination or tour at the service point.

  2. Guide

    Robot

    Lead along the route and play checkpoint content.

  3. Arrive

    Reception staff

    Confirm arrival and continue the human service.

Pilot the documented workflow with responsible staff verifying key handovers.

Service flow and ownership

Robots execute configured tasks; responsible staff retain verification and on-site response.

  1. Visitor / staff

    Start

    Select a destination or tour at the service point.

  2. Platform

    Dispatch

    Create a task from configured destinations and routes.

  3. Robot

    Guide

    Lead along the route and play checkpoint content.

  4. Reception staff

    Arrive

    Confirm arrival and continue the human service.

  5. 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.

Single exhibit

Click/voice triggers configured content.

Multi-stop tours

Configure standard, quick or VIP routes for visitors.

Human collaboration

Robots explain recurring content; staff handle expert questions and deeper discussions.

Illustrations and sample dashboards do not establish conversion or satisfaction results. Assess CRM, reservations, displays and access interfaces per project.

Terminals and configuration

Document-based scope; confirm supplied model, options and site fit.

  • One or two terminals / platform

    Source recommendation, adjusted to routes and visitor flow.

  • Content management

    Welcome scripts, exhibit text, question prompts, uploads, routes and records.

Scenario fit

Connect welcome, route selection, exhibit explanations, multi-stop tours and expert handover using approved screen, voice and multimedia content.

  • Single exhibit

    Click/voice triggers configured content.

  • Multi-stop tours

    Configure standard, quick or VIP routes for visitors.

  • Human collaboration

    Robots explain recurring content; staff handle expert questions and deeper discussions.

Where the service helps

Coordinate routes, content and staff around these tasks.

Service areaService scope
Single exhibitClick/voice triggers configured content.
Multi-stop toursConfigure standard, quick or VIP routes for visitors.
Human collaborationRobots explain recurring content; staff handle expert questions and deeper discussions.
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.

Routes and service points

Configure routes for the actual site; diagrams explain the workflow.

  1. Welcome

    Greet, establish needs and select a route.

  2. Exhibits / stops

    Configure sequence, dwell time, media and multilingual scripts.

  3. Handover / feedback

    Human reception, feedback and content review.

Locations

  • Welcome
  • Exhibits / stops
  • Handover / feedback

Validate a complete loop

Welcome → Exhibits / stops → Handover / feedback

Diagrams explain the flow; survey actual passages, thresholds, access and stops.

Site readiness and operations

Confirm site, equipment and staffing; verify interfaces per project.

  • Content ownership

    Venue staff approve and maintain materials, multilingual scripts and responses.

  • Operational review

    Use tasks, feedback and popular exhibits to improve content/routes; refer special needs and out-of-scope questions to staff.

Commission configured interfaces, notifications and access; assign site contacts and staff fallback.

Suggested readiness checks

Swipe horizontally to see all columns.

ItemScopeConfirmation
Scope and pointsWelcome, Exhibits / stops, Handover / feedbackConfirm accessible scope and responsible staff on site.
Routes and accessMaps, passages, doors/lifts, network and charging.Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptionsReception staff, Robot, ManagersAgree notifications, staff takeover, records and review rules.

Pilot and expansion

Prepare content/site and validate welcome-to-human-handover routes. The source’s two-to-four-week period is conditional, not fixed.

One or two terminals / platform

Source recommendation, adjusted to routes and visitor flow.

Content management

Welcome scripts, exhibit text, question prompts, uploads, routes and records.

Sizing considerations
Sizing variableEffect on capacity
Task cycleMeasure request, execution, handover, return and charging time.
Site scopeWelcome, Exhibits / stops, Handover / feedback
Staff coordinationAllow for available receiving, reviewing and exception-response staff.

Source configurations/data refer to their stated scenario; confirm final sizing through site validation.

Suggested implementation

The following are project assessment and acceptance suggestions, subject to site confirmation.

  1. Confirm scope

    Site preparation

    Prepare content/site and validate welcome-to-human-handover routes. The source’s two-to-four-week period is conditional, not fixed.

  2. Configure and commission

    When ready

    Check devices, routes, points, accounts and necessary access/system interfaces.

  3. 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.

ConditionActionOwnership and records
Task cannot continuePause, wait or hand over to staff under site rules.Managers record cause, owner and recovery conditions.
Handover/review incompleteContact the assigned staff; automatic task closure does not replace their confirmation.Record the reason and follow-up.
Device/access exceptionFollow 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.

CheckStatusVerification
Task executionSuggested acceptance itemComplete tasks within agreed routes/scope and record success, failure and reasons.
Staff coordinationSuggested acceptance itemVerify notification, permissions, human review/handover and exception takeover.
Operational recordsSuggested acceptance itemSample tasks, times, points and outcomes; agree metrics and targets with the project team.

Agree before delivery

  • Service scope

    Illustrations and sample dashboards do not establish conversion or satisfaction results. Assess CRM, reservations, displays and access interfaces per project.

  • Responsibilities

    Reception staff, Robot, Managers

  • Configuration and metrics

    Agree device models, options, interfaces, timing and targets in project documents.

KAGO Robot

Related equipment

Review product information and reconcile the document version with the supplied model/configuration.

View product

Document configuration and device checks

One or two terminals / platform
Source recommendation, adjusted to routes and visitor flow.
Content management
Welcome scripts, exhibit text, question prompts, uploads, routes and records.

Common questions

Where should the pilot start?

Prepare content/site and validate welcome-to-human-handover routes. The source’s two-to-four-week period is conditional, not fixed.

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?

Illustrations and sample dashboards do not establish conversion or satisfaction results. Assess CRM, reservations, displays and access interfaces per project.

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

Prepare content/site and validate welcome-to-human-handover routes. The source’s two-to-four-week period is conditional, not fixed.

Scope and points

Welcome, Exhibits / stops, Handover / feedback 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.

Discuss the solution

Choose a dedicated solution for each workflow.