AERO / LOCKER OPERATIONS

01 / AERO / LOCKER OPERATIONS

Aero.
On the job.

Practical support for Aeropost’s locker teams: answers, approved actions, and a clearer view of the operation—without another round of calls and messages.

More help with the everyday work. More visibility when something goes wrong.

AERO
aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
CONNECTED OPERATIONSHelp with the work.

Workflow illustration · not live data

02 / THE EVERYDAY FRICTION

Less chasing.
More fixing.

A small locker issue can turn into a long conversation. A shorter path to an answer means less time passing the same question around.

Keep the people involved. Cut down the handoffs.

THE OLD PATTERN

Report→Ask→Search→Escalate

A SHORTER PATH

TEAM
Aero
RESULT

Fewer handoffs for supported requests.

Workflow illustration · not live data

03 / WHAT’S DIFFERENT NOW

Ask a question.
Get the next step handled.

Teams can get answers, request approved actions, and check what’s happening across the operation. Aero brings those pieces into the same conversation.

An answer is useful. Getting the next step handled is better.

01

Conversation

Help in the team’s workflow

↗
02

Action

Approved operational tools

✓
03

Visibility

Health, history, and evidence

◎

Workflow illustration · not live data

04 / THE AERO TEAM

Frontline support.
Leadership visibility.

AeroBVI and Aero Locker Ops support frontline conversations. Executive Aero helps leadership investigate issues and guide supported improvements.

Different roles, working from shared operational context.

A

MIKE’S MANAGEMENT PARTNER

Executive Aero

Investigate · Direct · Verify

BVI

AeroBVI

BVI operations
Approved Slack conversations

OPS

Aero Locker Ops

Regional operations
Approved WhatsApp groups

Workflow illustration · not live data

05 / IN THE EVERYDAY CONVERSATIONS

Same conversations.
More getting done.

Aero works in the team’s existing operational conversations. A clear request gets things moving; a missing detail gets a short follow-up question.

No special script. No need to explain the same thing twice when the context is already there.

A
AeroOperational support
This terminal needs a restart.
Earlier context identifies Terminal X.
I’ll use the authorized restart workflow for Terminal X and verify the result.
WHEN A DETAIL IS MISSING
The locker isn’t working.
What specifically isn’t working?

Workflow illustration · not live data

06 / PACKAGE QUESTIONS

The answer shouldn’t
take a message chain.

Give Aero the package and location. It can find the matching record, return the required reference, and help investigate a pickup or drop-off problem.

01Find the right package.
02Get the right reference.
03Look into the problem.

Less time hunting for information. More time using it.

a.
a.
a.

PACKAGE SUPPORT

PackageDEMO-042
LocationExample terminal
Next stepResolve request
Record matched

Start with the right record.

Aero matches the package and location before answering.

a.
a.
a.

PACKAGE SUPPORT

PackageDEMO-042
LocationExample terminal
Next stepReturn courier reference
Reference located

No hunting through messages.

The courier reference stays separate from the customer pickup code.

a.
a.
a.

PACKAGE SUPPORT

PackageDEMO-042
LocationExample terminal
Next stepInvestigate reported issue
Evidence reviewed

Something concrete to work with.

Aero checks pickup or drop-off symptoms against the available evidence.

Workflow illustration · not live data

07 / EVERYDAY REQUESTS

Routine requests.
Without the wait.

For eligible package expirations and driver unblocking, teams can ask Aero directly. The usual checks still apply; routine requests don’t need another leadership handoff.

01Expire an eligible package.
02Unblock an eligible driver.

The checks stay. The extra back-and-forth doesn’t have to.

▣

PACKAGE EXPIRATION

Eligible package→Expired
✓ Exact match✓ Eligibility checked✓ State verified

Already in the requested state? No change needed.

One routine request handled.

Aero matches the package, checks eligibility, and confirms its status.

↗

DRIVER ACCESS

Eligible blocked account→Enabled
✓ Exact match✓ Eligibility checked✓ State verified

Already in the requested state? No change needed.

Help the driver get back to work.

Aero checks the driver’s identity and verifies the account state.

Workflow illustration · not live data

08 / AT THE COMPARTMENT

Check the locker.
Not the group chat.

Aero can provide a fresh compartment reading. When an opening is needed, an authorized request can target that specific door and check the result.

01Ask what the sensor sees.
02Request one authorized opening.
03Check what happened.

Checking what’s inside and asking to open a door are separate requests.

aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
Occupancy detectedExample compartment B3

Is something detected inside?

The sensor reports occupancy—not which parcel it is or how many.

aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
Opening requestedExample compartment B3

That door. That request.

Aero resolves the compartment and sends the approved opening command.

aeropost SMART LOCKER
a.
Ready for
collection.
A1
A2
A3
B1
B2
B3
C1
C2
C3
D1
D2
D3
Door state verifiedExample compartment B3

Don’t stop at “sent.”

A fresh door-state reading and an action record show what was observed.

Workflow illustration · not live data

09 / KEEPING AN EYE ON THE LOCKERS

Spot trouble
sooner.

Connected terminals report application, service, and system health. That creates an early signal to investigate, without first piecing together a chain of messages.

A useful early signal—not a substitute for what someone sees on-site.

CONNECTED TERMINALObserved health
ApplicationResponsiveness
ServicesAvailability
SystemResource signals
ReportingFreshness

A missing report is not proof of a powered-off locker.

Workflow illustration · not live data

10 / ALERTS WITHOUT THE NOISE

A heads-up.
Not a message storm.

An issue goes to the team responsible for that locker. Aero keeps checking quietly and sends a recovery update when the evidence supports it.

01Let the responsible team know.
02Follow up when it recovers.

Useful updates, without filling every group with reminders.

A

ONE INCIDENT

Issue detected

Region AResponsible groupRegion C
“An issue at your location needs attention.”

Illustrative destinations · actual routes follow the approved location map.

The right team gets the heads-up.

The locker’s location determines which approved group receives the alert.

A

ONE INCIDENT

Recovery confirmed

Region AResponsible groupRegion C
“Fresh checks confirm the reported issue has recovered.”

Illustrative destinations · actual routes follow the approved location map.

An update when it’s back.

Checks continue quietly; recovery is reported when confirmed.

Workflow illustration · not live data

11 / THE HEALTH MONITOR

One place to see
what needs attention.

The Health Monitor brings status, report times, and incident history into one place. Teams can see what needs attention without assembling the story from separate chats.

Check the status—and how recently it was reported.

aero / Health MonitorILLUSTRATION
STATUSAt a glance.
HISTORYIn context.
TERMINALOBSERVATIONSTATUS
Example ARecent reportHealthy
Example BFault observedReview
Example COlder reportStale
INCIDENT HISTORY
Open Health Monitor ↗

Workflow illustration · not live data

12 / LOOKING BACK AT AN INCIDENT

“It went down.”
There’s more to the story.

Available diagnostic records stay with the incident. Aero and the dashboard can look back at the same history instead of starting the investigation again.

01Keep the available records.
02Keep the history together.
03Ask Aero about it later.

Known facts, with the gaps clearly marked.

CaptureRetainExplain

INCIDENT RECORD · ILLUSTRATION

Evidence arrives.

Observed eventApplication unresponsive
Available evidenceApplication + system records
CauseUnconfirmed
Dashboard↔Aero

Start with what happened.

Relevant application and system records are gathered when the terminal is reachable.

CaptureRetainExplain

INCIDENT RECORD · ILLUSTRATION

Context stays.

Observed eventApplication unresponsive
Available evidenceApplication + system records
CauseUnconfirmed
Dashboard↔Aero

A record worth keeping.

The timeline, findings, and any missing evidence stay with the incident.

CaptureRetainExplain

INCIDENT RECORD · ILLUSTRATION

Answers improve.

Observed eventApplication unresponsive
Available evidenceApplication + system records
CauseUnconfirmed
Dashboard↔Aero

No need to start from scratch.

Aero can explain the record and identify when the cause is still unconfirmed.

Workflow illustration · not live data

13 / GETTING THINGS RUNNING AGAIN

More fixes.
Less running around.

For supported software issues, Aero can investigate, carry out an authorized recovery, and check the result. Physical faults still need hands on-site.

01Look at the current condition.
02Carry out the approved fix.
03Check it again.

“Command sent” isn’t the finish line. Check what actually changed.

STEP 01Diagnose
EvidenceActionOutcome

Supported software recovery. Physical checks remain a human task.

Check before changing anything.

Aero identifies the terminal and looks at the available evidence.

STEP 02Recover
EvidenceActionOutcome

Supported software recovery. Physical checks remain a human task.

Do what’s needed.

The recovery stays within the supported action and approved scope.

STEP 03Verify
EvidenceActionOutcome

Supported software recovery. Physical checks remain a human task.

Confirm what actually changed.

Aero confirms observed recovery or explains the next required check.

Workflow illustration · not live data

14 / STAYING IN CONTROL

Faster doesn’t mean
anything goes.

Aero still needs to know who is asking, which location or package they mean, and whether the action is allowed. The action record keeps track of what happened.

The right request, the right scope, and a result that can be explained.

✓Control stays
in place.
01IdentityWho is asking?
02ScopeWhere does it apply?
03EvidenceWhat can be verified?
04RecordWhat actually happened?

Workflow illustration · not live data

15 / KEEPING AERO USEFUL

Not quite right?
There’s a way to fix it.

Executive Aero gives leadership a way to investigate an incorrect response, direct a supported correction, and check whether it helped.

The Executive Aero handbook provides a practical guide to the process.

aeropost

THE EXECUTIVE AERO HANDBOOK

Your Aero,
working
with you.

MIKE’S PRACTICAL OPERATING GUIDE
01 / Describe02 / Investigate03 / Direct04 / Verify

Workflow illustration · not live data

16 / WHAT TO MEASURE

Less on the plate.
More getting done.

The next step is to measure the difference in the work: time to useful help, routine requests handled, and problems that keep coming back.

The measure is a better working day—not more AI messages.

WHAT TO KEEP TRACK OF

01

Response & resolution

How quickly does the team get useful help?

↗
02

Requests handled

How much routine work does Aero support?

↗
03

Repeat incidents

Where does the same friction keep returning?

↗

Measurement priorities—not claims of measured savings.

Workflow illustration · not live data

17 / FROM HERE

Put it to work.
Keep making it better.

Use Aero for supported requests. Flag the gaps. Keep improving the support around how Aeropost’s teams actually work.

Built with Spotlight Revenue. Shaped around Aeropost’s working day.

AERO
The teams.The operation.The next chapter.

Put it to work.
Keep improving the everyday.

Workflow illustration · not live data

Use the corner arrows to explore