User reservation
Register an address and book ahead to manage peak demand.
Building autonomous delivery solution
Eight modes connect building deliveries.From reservations to reverse pickups.
Connect takeaway, parcels, documents, retail and internal supplies through robot transport with booking/loading flows for users, couriers, merchants and reception.
Request
Users
Select items, destination and required time.
Deliver
Robot
Follow configured routes and access rules.
Handover
Recipients
Receive the arrival alert, use configured access and verify receipt.
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.
Users
Request
Select items, destination and required time.
Dispatch staff
Prepare and load
Check items, packaging and compartments; load manually and confirm.
Robot
Deliver
Follow configured routes and access rules.
Recipients
Handover
Receive the arrival alert, use configured access and verify receipt.
Managers
Retain records
Review completion, exceptions and handover records.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Roles
Dispatch and receiving staff
Request, prepare, load, verify and acknowledge receipt.
Robot
Transport, notify and return status within the configured scope.
Management and support
Maintain points, schedules, equipment, exception handling and records.
Service modes
Select modes for the workflow; agree extensions separately.
Courier reservation
Couriers scan, enter and load while retaining courier identity.
Screen ordering
Enter a phone suffix directly without courier phone interaction.
Point-to-point delivery
Move documents and small items between reachable A/B points.
Merchant shopping
Users purchase, merchants prepare and robots deliver indoors.
Parcel dispatch
Reception enters batches for floors; temporary recipients need not preregister.
Parcel pickup
Employees book and load with a code for return to a fixed post/mail desk.
Call-to-deliver
Summon from the app for ad hoc needs such as missing meeting items.
A comprehensive solution does not make every workflow/interface standard. Select scope for the site, goods and roles; universal concurrency/latency guarantees are not established.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
KAGO5 reference
Source 20 kg total, 2–4 compartments and eight-hour static/no-load runtime refer to the documented model; verify supplied specifications.
Platform
Choose cloud, local/private, standard APIs and mini-program links within scope.
Suitability
Scenario fit
Connect takeaway, parcels, documents, retail and internal supplies through robot transport with booking/loading flows for users, couriers, merchants and reception.
User reservation
Register an address and book ahead to manage peak demand.
Courier reservation
Couriers scan, enter and load while retaining courier identity.
Screen ordering
Enter a phone suffix directly without courier phone interaction.
Point-to-point delivery
Move documents and small items between reachable A/B points.
Merchant shopping
Users purchase, merchants prepare and robots deliver indoors.
Parcel dispatch
Reception enters batches for floors; temporary recipients need not preregister.
Parcel pickup
Employees book and load with a code for return to a fixed post/mail desk.
Call-to-deliver
Summon from the app for ad hoc needs such as missing meeting items.
Where the service helps
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| User reservation | Register an address and book ahead to manage peak demand. |
| Courier reservation | Couriers scan, enter and load while retaining courier identity. |
| Screen ordering | Enter a phone suffix directly without courier phone interaction. |
| Point-to-point delivery | Move documents and small items between reachable A/B points. |
| Merchant shopping | Users purchase, merchants prepare and robots deliver indoors. |
| Parcel dispatch | Reception enters batches for floors; temporary recipients need not preregister. |
| Parcel pickup | Employees book and load with a code for return to a fixed post/mail desk. |
| Call-to-deliver | Summon from the app for ad hoc needs such as missing meeting items. |
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.
Entrance / merchants
Check orders, goods, recipients and compartments.
Floor destinations
Notify, authorize collection and redeliver.
Reception / support
Receive reverse deliveries, charge, dispatch and handle exceptions.
Locations
- Entrance / merchants
- Floor destinations
- Reception / support
Validate a complete loop
Entrance / merchants → Floor destinations → Reception / support
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Site readiness and operations
Confirm site, equipment and staffing; verify interfaces per project.
Door / lift access
The source’s 4G/2.4G module approach preserves the original lift system; assess vendor APIs/cost when unsuitable.
Notification extensions
Confirm doorbell, speaker and telephone compatibility by brand/interface.
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 | Entrance / merchants, Floor destinations, Reception / support | 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 | Dispatch and receiving staff, Robot, Management and support | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
Start with one frequent workflow and complete route; validate roles, loading, notification, collection and exceptions before adding services.
KAGO5 reference
Source 20 kg total, 2–4 compartments and eight-hour static/no-load runtime refer to the documented model; verify supplied specifications.
Platform
Choose cloud, local/private, standard APIs and mini-program links within scope.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Entrance / merchants, Floor destinations, Reception / support |
| 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
Start with one frequent workflow and complete route; validate roles, loading, notification, collection and exceptions before adding services.
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
A comprehensive solution does not make every workflow/interface standard. Select scope for the site, goods and roles; universal concurrency/latency guarantees are not established.
Responsibilities
Dispatch and receiving staff, Robot, Management and support
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
- KAGO5 reference
- Source 20 kg total, 2–4 compartments and eight-hour static/no-load runtime refer to the documented model; verify supplied specifications.
- Platform
- Choose cloud, local/private, standard APIs and mini-program links within scope.
Common questions
Where should the pilot start?
Start with one frequent workflow and complete route; validate roles, loading, notification, collection and exceptions before adding services.
How do robots and staff share work?
Dispatch and receiving staff：Request, prepare, load, verify and acknowledge receipt. Robot：Transport, notify and return status within the configured scope. Management and support：Maintain points, schedules, equipment, exception handling and records.
What needs separate confirmation?
A comprehensive solution does not make every workflow/interface standard. Select scope for the site, goods and roles; universal concurrency/latency guarantees are not established.
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
Start with one frequent workflow and complete route; validate roles, loading, notification, collection and exceptions before adding services.
Scope and points
Entrance / merchants, Floor destinations, Reception / support 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
Dispatch and receiving staff, Robot, Management and support Agree notifications, staff takeover, records and review rules.
Related solutions
Choose a dedicated solution for each workflow.
Building takeaway delivery solution
Couriers load meals for autonomous delivery through commissioned doors/lifts.
Building mailroom two-way delivery solution
Support bulk reception/mailroom deliveries to company reception desks or workstations and employee-requested pickups back to a fixed mailroom.
Building document delivery solution
Support floor-to-floor documents, reception bulk dispatch, reverse pickups to mailrooms and urgent tasks, with human packaging/recipient/handover checks.