Forward bulk
Managers enter recipients; reception loads compartments for delivery.
Building mailroom two-way delivery solution
Dispatch mailroom items to office floors.Book reverse pickups back to reception.
Support bulk reception/mailroom deliveries to company reception desks or workstations and employee-requested pickups back to a fixed mailroom.
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.
Reverse pickup
Employees book, load with a code and send items to the fixed mailroom.
Collection access
Configure suffix, mini-program, badge, password or authorized direct opening.
Temporary forward recipients need not preregister. Staff verify recipient details, packaging and access rules; universal parcel-label recognition is not established.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
2–4-compartment terminal
Separate recipients and validate size/weight.
Platform / IoT
User/manager tools and access integration; choose cloud/local/private and APIs per project.
Suitability
Scenario fit
Support bulk reception/mailroom deliveries to company reception desks or workstations and employee-requested pickups back to a fixed mailroom.
Forward bulk
Managers enter recipients; reception loads compartments for delivery.
Reverse pickup
Employees book, load with a code and send items to the fixed mailroom.
Collection access
Configure suffix, mini-program, badge, password or authorized direct opening.
Where the service helps
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| Forward bulk | Managers enter recipients; reception loads compartments for delivery. |
| Reverse pickup | Employees book, load with a code and send items to the fixed mailroom. |
| Collection access | Configure suffix, mini-program, badge, password or authorized direct opening. |
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.
Mailroom / reception
Check incoming items, enter batches and load.
Company reception / workstation
Arrival alert and verified collection.
Reverse destination
Notify the fixed reception phone and receive under agreed permissions.
Locations
- Mailroom / reception
- Company reception / workstation
- Reverse destination
Validate a complete loop
Mailroom / reception → Company reception / workstation → Reverse 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.
Reception service
Define temporary recipients, fixed-phone alerts, refusal and uncollected returns.
Case context
The Siemens case’s two robots, retail cabinet and two lifts are site-specific, not universal minima.
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 | Mailroom / reception, Company reception / workstation, Reverse 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 | Dispatch and receiving staff, Robot, Management and support | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
Validate both directions from one fixed mailroom to a few floors. The source’s 5–10-minute trips and 2–4 destinations are planning references.
2–4-compartment terminal
Separate recipients and validate size/weight.
Platform / IoT
User/manager tools and access integration; choose cloud/local/private and APIs per project.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Mailroom / reception, Company reception / workstation, Reverse 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
Validate both directions from one fixed mailroom to a few floors. The source’s 5–10-minute trips and 2–4 destinations are planning references.
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
Temporary forward recipients need not preregister. Staff verify recipient details, packaging and access rules; universal parcel-label recognition is 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
- 2–4-compartment terminal
- Separate recipients and validate size/weight.
- Platform / IoT
- User/manager tools and access integration; choose cloud/local/private and APIs per project.
Common questions
Where should the pilot start?
Validate both directions from one fixed mailroom to a few floors. The source’s 5–10-minute trips and 2–4 destinations are planning references.
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?
Temporary forward recipients need not preregister. Staff verify recipient details, packaging and access rules; universal parcel-label recognition is 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
Validate both directions from one fixed mailroom to a few floors. The source’s 5–10-minute trips and 2–4 destinations are planning references.
Scope and points
Mailroom / reception, Company reception / workstation, Reverse 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
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 document delivery solution
Support floor-to-floor documents, reception bulk dispatch, reverse pickups to mailrooms and urgent tasks, with human packaging/recipient/handover checks.
Building takeaway delivery solution
Couriers load meals for autonomous delivery through commissioned doors/lifts.
Building group-meal delivery solution
Coordinate loading, separate compartments and floor delivery around meal peaks using user reservations, courier loading and merchant order tools.