Employee request
Provide recipient and destination in the app/mini-program.
Headquarters comprehensive item delivery
Move office items through defined tasks.Connect reservations, loading and collection.
Connect headquarters reception, employees and floor service points through reservations, loading, arrival notifications, authorized collection and redelivery.
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.
Reception dispatch
Reception verifies items, recipients and loading tasks.
Ad hoc dispatch
Couriers follow authorized procedures; direct compartment access is not automatic.
Confirm compartments, collection methods, systems and access integration for the project. Assigned staff classify, load and handle exceptions.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
Compartment delivery
Source reference: 2–4 compartments, 5 kg small/10 kg large; confirm the supplied model.
Management
Tasks, devices, routes, records and permissions; optional APIs.
Suitability
Scenario fit
Connect headquarters reception, employees and floor service points through reservations, loading, arrival notifications, authorized collection and redelivery.
Employee request
Provide recipient and destination in the app/mini-program.
Reception dispatch
Reception verifies items, recipients and loading tasks.
Ad hoc dispatch
Couriers follow authorized procedures; direct compartment access is not automatic.
Where the service helps
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| Employee request | Provide recipient and destination in the app/mini-program. |
| Reception dispatch | Reception verifies items, recipients and loading tasks. |
| Ad hoc dispatch | Couriers follow authorized procedures; direct compartment access is not automatic. |
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.
Reception / loading
Verify recipients, classify and load.
Floor destination
Call/SMS notification and configured collection checks.
Support
Confirm charging, dispatch and lift/door access.
Locations
- Reception / loading
- Floor destination
- Support
Validate a complete loop
Reception / loading → Floor destination → 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.
Collection
Choose QR, phone verification or badge according to the document and configuration; staff verify recipient details.
Exceptions
Manage fallback SMS, uncollected reminders/redelivery, lift waiting and door faults.
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 | Reception / loading, Floor destination, 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
Source reference: one or two robots, one management platform, with cross-floor IoT and APIs assessed as needed.
Compartment delivery
Source reference: 2–4 compartments, 5 kg small/10 kg large; confirm the supplied model.
Management
Tasks, devices, routes, records and permissions; optional APIs.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Reception / loading, Floor destination, 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
Source reference: one or two robots, one management platform, with cross-floor IoT and APIs assessed as needed.
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
Confirm compartments, collection methods, systems and access integration for the project. Assigned staff classify, load and handle exceptions.
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
- Compartment delivery
- Source reference: 2–4 compartments, 5 kg small/10 kg large; confirm the supplied model.
- Management
- Tasks, devices, routes, records and permissions; optional APIs.
Common questions
Where should the pilot start?
Source reference: one or two robots, one management platform, with cross-floor IoT and APIs assessed as needed.
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?
Confirm compartments, collection methods, systems and access integration for the project. Assigned staff classify, load and handle exceptions.
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
Source reference: one or two robots, one management platform, with cross-floor IoT and APIs assessed as needed.
Scope and points
Reception / loading, Floor destination, 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.
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 visitor guidance solution
The robot waits at a fixed welcome point.
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.