Apartment takeaway delivery solution
Couriers load meals at a handover point. Robots travel through authorized doors and lifts to the apartment door and call residents to collect. Registered residents and temporary occupants use different address matching flows.
Register
Provide address details for the selected resident flow.
Deliver
Use project-integrated doors and lifts to reach the apartment door.
Collect
Receive the call and verify collection using the configured method.
Pilot the documented workflow with responsible staff verifying key handovers.
The service
Robots execute configured tasks; responsible staff retain verification and on-site response.
Resident
Provide address details for the selected resident flow.
Courier
Check the apartment or phone suffix and load the assigned compartment.
Robot
Use project-integrated doors and lifts to reach the apartment door.
Resident
Receive the call and verify collection using the configured method.
Management
Apply the retained-order policy and return to a pickup or charging point.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Check recipient details, load and confirm.
Register delivery details and collect after notification.
Manage orders, devices, reports and exceptions; provide charging power.
Select modes for the workflow; agree extensions separately.
Registered residents
Bind a phone number to the apartment; the courier enters the apartment number to load.
Configure and validate against site conditions.
Temporary residents / guests
Load using the phone suffix; the robot calls on arrival at the apartment door.
Configure and validate against site conditions.
Video doorbell and Bluetooth speaker notifications require brand-specific feasibility and cost assessment.
Document-based scope; confirm supplied model, options and site fit.
2–4 independent compartments for multiple orders; match packaging to the selected layout.
Resident, courier and property tools cover reservations, tracking, redelivery and device management.
Suitability
Couriers load meals at a handover point. Robots travel through authorized doors and lifts to the apartment door and call residents to collect. Registered residents and temporary occupants use different address matching flows.
Bind a phone number to the apartment; the courier enters the apartment number to load.
Load using the phone suffix; the robot calls on arrival at the apartment door.
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| Registered residents | Bind a phone number to the apartment; the courier enters the apartment number to load. |
| Temporary residents / guests | Load using the phone suffix; the robot calls on arrival at the apartment door. |
Assign suitable repeated routes to robots and compare results in the pilot.
Verify outcomes against task, destination and responsible role.
Use task states and exception records to adjust routes, schedules and configuration.
Building route
Configure routes for the actual site; diagrams explain the workflow.
The courier loads meals.
Configure high/low-rise lifts and lobby doors.
Arrival call and verified collection.
Entrance handover → Doors and lifts → Apartment door
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Confirm site, equipment and staffing; verify interfaces per project.
Immediate departures off-peak and consolidated departures when busy; configure roles, pickup and charging points by time.
The document mentions Xiaodu speaker integration; assess other speaker and doorbell brands individually.
Commission configured interfaces, notifications and access; assign site contacts and staff fallback.
Swipe horizontally to see all columns.
| Item | Scope | Confirmation |
|---|---|---|
| Scope and points | Entrance handover, Doors and lifts, Apartment door | 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 | Courier, Resident, Property team | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Size the fleet from demand, with the management app and required lift/door integrations. The document gives no universal robot count.
2–4 independent compartments for multiple orders; match packaging to the selected layout.
Resident, courier and property tools cover reservations, tracking, redelivery and device management.
| Sizing input | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Entrance handover, Doors and lifts, Apartment door |
| 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.
Schedule around demand and site routines, allowing for cleaning, charging and exceptions.
Dispatch schedule
Immediate departures off-peak and consolidated departures when busy; configure roles, pickup and charging points by time.
Notification extensions
The document mentions Xiaodu speaker integration; assess other speaker and doorbell brands individually.
Size the fleet from demand, with the management app and required lift/door integrations. The document gives no universal robot count.Video doorbell and Bluetooth speaker notifications require brand-specific feasibility and cost assessment.
Start with the documented workflow and verify optional interfaces separately.
| System layer | Responsibilities |
|---|---|
| KAGO5 | 2–4 independent compartments for multiple orders; match packaging to the selected layout. |
| Applications | Resident, courier and property tools cover reservations, tracking, redelivery and device management. |
Pilot & operation
The following are project assessment and acceptance suggestions, subject to site confirmation.
Site preparation
Size the fleet from demand, with the management app and required lift/door integrations. The document gives no universal robot count.
When ready
Check devices, routes, points, accounts and necessary access/system interfaces.
By project agreement
Validate real tasks, staff coordination, exceptions and records before expansion.
The following are project assessment and acceptance suggestions, subject to site confirmation.
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. |
The following are project assessment and acceptance suggestions, subject to site confirmation.
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. |
Video doorbell and Bluetooth speaker notifications require brand-specific feasibility and cost assessment.
Courier, Resident, Property team
Agree device models, options, interfaces, timing and targets in project documents.
Questions
Review product information and reconcile the document version with the supplied model/configuration.
View productDocument and current product versions may differ; confirm supplied specifications and project configuration.
Size the fleet from demand, with the management app and required lift/door integrations. The document gives no universal robot count.
Courier：Check recipient details, load and confirm. Resident：Register delivery details and collect after notification. Property team：Manage orders, devices, reports and exceptions; provide charging power.
Video doorbell and Bluetooth speaker notifications require brand-specific feasibility and cost assessment.
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.
Plan a project
Size the fleet from demand, with the management app and required lift/door integrations. The document gives no universal robot count.
Discuss the solutionChoose a dedicated solution for each workflow.
Concierge staff receive, check and sort parcels.
Robots patrol configured communal routes, capture checkpoint images and return live views.
Connect courier loading, indoor transport and collection.