01 / OVERVIEW
Aero’s locker
operations capabilities.
Look up packages, carry out permitted actions, monitor terminals, and investigate operational problems.
- Scope
- Approved operational conversations and connected, supported terminals.
- Output
- Package support · compartment actions · monitoring · incident investigation · leadership support.
This guide explains the action, the information needed, and the result to expect.
collection.
Illustrative workflow · not live operational data
02 / WHO TO ASK
Three roles.
Defined responsibilities.
Use the Aero role assigned to the team and location. Access and permitted actions differ by role.
- Scope
- AeroBVI: BVI operations in approved Slack conversations. Aero Locker Ops: approved regional WhatsApp groups.
- Output
- Executive Aero: leadership investigation, supported corrections, and authorized maintenance.
A capability described here does not grant every role the same permissions.
MIKE’S MANAGEMENT PARTNER
Executive Aero
Investigate · Direct · Verify
AeroBVI
BVI operations
Approved Slack conversations
Aero Locker Ops
Regional operations
Approved WhatsApp groups
Illustrative workflow · not live operational data
03 / ON REQUEST
Find a package
and courier reference.
Match a package to its location and retrieve the courier reference needed by the team.
- Provide
- Package barcode or reference, exact location, and purpose of the lookup.
- Receive
- The matched package record and the relevant courier reference.
A courier reference is not the customer’s pickup code.
PACKAGE SUPPORT
Illustrative workflow · not live operational data
04 / ON REQUEST
Investigate a pickup
or drop-off failure.
Compare the reported problem with package status, locker signals, and available records.
- Provide
- Location, package reference, time and time zone, and the exact error or symptom.
- Receive
- Observed findings, gaps in the evidence, and the next recommended action.
Physical faults or unresolved vendor issues may require on-site or specialist support.
PICKUP / DROP-OFF INVESTIGATION
Request
Location + package + error
Compare
Package state + locker signals
Return
Findings + next action
Illustrative workflow · not live operational data
05 / ON REQUEST
Expire an
eligible package.
Check the package’s current status, perform an eligible expiration, and read back the final state.
- Provide
- Exact package barcode or reference and location in an approved operational group.
- Receive
- Verified final status—or the reason no change was made.
Already expired needs no change. Expiration does not open a door or prove physical retrieval.
PACKAGE EXPIRATION
Already in the requested state? No change needed.
Illustrative workflow · not live operational data
06 / ON REQUEST
Unblock an
eligible driver.
Match the driver account, check restrictions, and restore access when the request is permitted.
- Provide
- Exact driver account or identifier and location—not a name alone.
- Receive
- Verified account state, or the restriction preventing an unblock.
Recorded exclusions and do-not-unblock restrictions must be resolved by the appropriate authority.
DRIVER ACCESS
Already in the requested state? No change needed.
Illustrative workflow · not live operational data
07 / ON REQUEST
Check occupancy
and door state.
Read fresh sensor information for the specified supported compartment without opening it.
- Provide
- Exact terminal and compartment, and the reading needed.
- Receive
- Observed occupancy and door state, with reading time or any access limitation.
An occupancy sensor does not identify a parcel or count the packages inside.
collection.
Example B3 · fresh sensor reading · no opening command
Illustrative workflow · not live operational data
08 / ON REQUEST
Open a specific
compartment.
Resolve the requested door, send the authorized opening command, and check the observed result.
- Provide
- Exact terminal and compartment, plus an authorized opening request.
- Receive
- Command result, fresh door-state observation, and an action record.
A sent command is not proof the door opened or a parcel was collected.
collection.
collection.
collection.
Illustrative workflow · not live operational data
09 / AUTOMATIC MONITORING
Monitor connected
terminal health.
Check supported application, service, system, and reporting signals for connected terminals.
- Scope
- Connected terminals with installed monitoring and available reporting.
- Output
- Health observations, reporting timestamps, and signals that need investigation.
A stale report means missing recent evidence—not proof that the locker is powered off.
A missing report is not proof of a powered-off locker.
Illustrative workflow · not live operational data
10 / AUTOMATIC ALERTS
Send issue and
recovery alerts.
Route a detected locker issue to the responsible approved group and report confirmed recovery.
- Scope
- Approved location-to-group routing and supported monitored incidents.
- Output
- An initial issue notification and a recovery update, without repeated reminder traffic.
Checks continue between alerts. Recovery is reported when supported by the evidence.
ONE INCIDENT
Issue detected
Illustrative destinations · actual routes follow the approved location map.
ONE INCIDENT
Recovery confirmed
Illustrative destinations · actual routes follow the approved location map.
Illustrative workflow · not live operational data
11 / HEALTH MONITOR
View status and
incident history.
Use the Health Monitor to review terminal condition, report freshness, and recorded incidents.
- Scope
- Select a terminal or incident period in the dashboard.
- Output
- Last reported health, observation times, and available incident history.
The dashboard shows recorded observations; check their timestamps before treating them as current.
Illustrative workflow · not live operational data
12 / ON REQUEST
Review incident
evidence.
Collect available diagnostic records and use the retained history to explain an incident.
- Provide
- Location, incident time window, and whether a historical review or fresh check is needed.
- Receive
- Timeline, available application and system evidence, findings, and explicit unknowns.
Evidence collection depends on access and reachability. An unconfirmed cause stays unconfirmed.
INCIDENT RECORD · ILLUSTRATION
Collect records
INCIDENT RECORD · ILLUSTRATION
Retain the timeline
INCIDENT RECORD · ILLUSTRATION
Explain the findings
Illustrative workflow · not live operational data
13 / ON REQUEST
Recover supported
terminal software.
Investigate software faults and, with the required authority, restart a supported application or service, or reboot a supported terminal.
- Provide
- Exact location, symptom, operational impact, and approval for the specific interruption.
- Receive
- A bounded recovery action and post-action health observations—or the next required check.
Requires the authorized Aero role and supported target. A restart does not prove a customer transaction succeeded.
Supported software recovery. Physical checks remain a human task.
Supported software recovery. Physical checks remain a human task.
Supported software recovery. Physical checks remain a human task.
Illustrative workflow · not live operational data
14 / ON REQUEST
Assess a proposed
Smartbox deployment.
Executive Aero can assess whether a specific Smartbox change is ready for an authorized deployment.
- Provide
- Exact target, intended version or change, maintenance window, and rollback expectations.
- Receive
- Readiness assessment covering prerequisites, impact, authority, validation, and rollback.
This is deployment planning—not an automatic fleet rollout. Execution requires verified support and explicit scope.
DEPLOYMENT READINESS
Target
Location + intended version
Review
Prerequisites + impact + authority
Plan
Validation + rollback
Illustrative workflow · not live operational data
15 / ON REQUEST
Investigate and correct
Aero’s behavior.
Executive Aero can inspect an incorrect specialist response and apply a supported, authorized instruction or workflow correction.
- Provide
- The affected Aero role, conversation and time, incorrect response, and approved expected behavior.
- Receive
- Cause assessment, a scoped correction where supported, and a verification result.
New integrations or unbuilt capabilities require separate implementation; they are not instruction edits.
THE EXECUTIVE AERO HANDBOOK
Investigate.
Correct.
Verify.
Illustrative workflow · not live operational data
16 / USING AERO
Make a clear request.
Expect a verified result.
Use the existing approved conversation. Identify the target, describe the task, and state the result needed.
- Scope
- Location + package, driver, or compartment ID + action or symptom + relevant time.
- Output
- A verified answer or action result. If blocked, the missing detail, limitation, or next step.
Executive Aero handbook: practical guidance for Mike. Built with Spotlight Revenue.
REQUEST TO RESULT
Identify
Exact target and location
Ask
Specific action or question
Verify
Observed result or next step
Illustrative workflow · not live operational data