Facilities AI agent · Mailroom and package logistics
Mailroom & Package Logistics AI Agent
Log each inbound item against the recipient your directory names, keep the handover open until a person accepts it by name, and leave the signature to the hand that gives it.
A parcel arrives, and the manifest line that announced it is bound to the item before it leaves the dock.
02
A handover is made, and the record names who released it, who accepted it and the hour it changed hands.
Reason
03
A recipient cannot be matched, and the item goes into holding rather than onto a plausible desk.
04
A held item ages, and the holding period your estate configured decides what follows, never a guess.
05
A controlled or regulated item is identified, and it takes the handling route you configured for it.
Decide
06
An internal transfer crosses floors, and every leg opens and closes on a line of its own.
07
A collection sits uncollected, and the named recipient is prompted before anything is escalated.
Out
08
A chain shows an open link, and the agent says so rather than closing it on an acceptance nobody gave.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent records each handover and leaves an unnamed link open. A named office manager settles what an unmatched or aged item becomes.
Example workflow
One parcel, dock to desk
AgentHuman
1Inbound item receivedCarrier manifests, dock scans, internal post or courier feeds
2Item context assembledThe item, the site it landed at, the recipient the directory names and the hour it was booked in
3Custody record draftedThe item, its handling route, the legs it has moved through and completeness
4Controls appliedRecipient-match checks, handling-route checks, chain-integrity checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is released at any of them — the agent is recording, and the mailroom lane opens at the completeness gate.
5DecisionSplits at the completeness gate
Chain complete
Goes to the office manager to release.
Anything thin
Adds a mailroom supervisor read first.
Mailroom review
The item is held with its chain, its open links and the site it sits at.
Release · Append evidence · Send to mailroom review
Released — by the office manager▼
6Custody and holding records updatedOnly where write access and records policy allow it
7Outcome evaluatedChain completeness, holding age, supervisor corrections and what the read found
Corrections
Each mailroom correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing for a parcel on behalf of a named recipient.
Deciding that an unmatched item may be given away.
Opening an item that sits on a handling route.
Setting how long a held item may age before disposal.
Automation boundaryAgent acts unaided
✓Bind every inbound item to the manifest line that announced it.
✓Name both hands on every handover, and the hour.
✓Hold an unmatched item in the holding queue and age it against policy.
✓Route a controlled or regulated item down the handling.
Nothing is released or signed for except by a named person, inside the agreed boundaries.
Judging whether a handover actually took place.
Telling a carrier that delivery was completed.
Naming who on a floor a stray parcel belongs to.
Changes to the recipient directory or holding rules.
Example output
One handover, annotated
Our freight track-and-trace agent follows a consignment while a carrier still holds it; this record begins at the dock, where the carrier lets go.
Custody record · single itemIllustrative example
Item
Recorded as
Route
Evidence of record
Confidence
Held for
Internal handover, floor to desk
Accepted by a named recipient
Standard inbound
Dock scan, 3 August 2026
Held unreleased
The office manager, by name
As receivedBuilt from the dock scan and the handover log, and it carries no further than those two sources.
What the record holdsCarrier manifest lineDock scanAcceptance record
Why no release hereWhether custody actually passed is a human account, not a model output.
ActionReleaseAppend evidenceSend to mailroom review
What the score decidesAn item under the configured threshold waits on a mailroom read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every itemFrom the dock that books it in
03Evidence
Where the evidence is used
A custody trail shows where an item travelled and whose hand took it; it is no screening programme, and it claims nothing at all about what the packaging held.
01Approved path
Custody is a chain
A chain is only as good as its weakest handover, so a leg with no named recipient on it stays an open link and is reported as one.
02Human review
What was checked, and not found
No carrier rulebook was treated as binding on your estate, no screening standard was purchased or read, and what a mailroom may hold about a person comes from the recipient directory you maintain rather than from anything inferred off a package.
04Build an evidence trail
The parcel, the hand it passed to and the hour it moved stay on the chain.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Carrier and courier sourcesManifests · dock scans Inbound delivery records
Recipient directoryHR system · directory feed Desk, floor and site records
Handover and custodyHandheld scanners · kiosks Acceptance and release records
Agent
Mailroom and package logistics
Reads the manifests Records the chain Holds for the manager
Holding and case systemsMailroom platform · ticketing Holding and return records
Integration availability depends on the client's existing systems and API access.
Agent controls
Six sentries between the model and the manager
Six sentries along one route, the last the least forgiving. What arrives is named in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to evidence assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and custody rules; a redrawn handling route changes which items may move without a named acceptance.Track
L4TraceabilityRecord each item, the legs behind it, the site it sits at and every read of the chain.Record
L3Manager releaseHold the item for the office manager; that hold governs release, not whether custody genuinely passed.Gate
L2Handling guardrailsTest each item against the routes you configured; a controlled, laboratory or legal-service item is directed and never opened.Restrict
L1Confidence thresholdsRoute a thin chain to a mailroom read before an item moves on an acceptance nobody can name.Require review
Model coreEvidence assembled — the item, the route, the legs and completeness
L1 – L2Test whether a chain may stand
L3Puts the release in a person's hands
L4 – L5Keep the parcel and the hand behind it
L6Holds the handover unlogged when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the custody record that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the chain a recipient reads
Depth of coverage ▼
E1Final-output evaluationDid the chain record what the item actually did?
E2Step-level evaluationDid the agent read the right item, the right route and the live directory?
E3Tool evaluationDid it read and write the correct item record and the correct chain?
E4Confidence calibrationDo low-confidence chains actually attract more mailroom corrections?
E5Slice evaluationHow does performance change across specific recipient groups?
E6Business outcomeHow many items needed a correction before the manager released?
Floor — the chain the estate answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each pinned to the stage where it first shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
KS-03
Stale directory read
The recipient list read is not the one now in force.
Stage gathersThe items, the routes, the hours and the roster
02 · Reasoning2 modes
KS-04
Recipient matched loosely
An item is bound to a near-enough name.
KS-06
Handling route ignored
A routed item is worked as ordinary post.
Stage proposesThe items, their routes and completeness
03 · Tool / write2 modes
KS-02
Thin chain passed forward
An item moves on without the mailroom read.
KS-05
Bound to the wrong site
A parcel is filed against the wrong floor.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
KS-01
Released, custody unrecorded
Release is on the record, the hand that accepted it is not.
Stage returnsThe chain a manager releases and a recipient reads
05 · Change / Version1 mode
KS-07
Silent route regression
A configuration change moves the route, not the item.
Stage tracksModel, prompt, custody rules and chain fields
Sev-1 · a parcel let go to an unnamed handSev-2 · wrong evidence reaches the chainSev-3 · source degrades, item held unreleased
A group-level custody-completeness figure can read clean while shared-desk floors carry most of the rework. Nestack reports the correction rate by recipient group, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Shared-desk floors
7.0%
3.6×
Review
Contractor and site teams
5.0%
2.6×
Review
Field and visiting staff
3.1%
1.6×
Watch
Named desk occupants
1.3%
0.7×
Normal
Bar: correction-rate lift vs. named desk occupant baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a broken chain costs
The loop shuts when the broken custody chain is a regression case. That suite is what the next parcel booked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on shared-desk floors.
02Diagnose
The parcel signed for by a name that matches nobody on the floor is read back until one cause remains.
03Improve
Any change goes out numbered, with the parcels that caused it attached.
04Verify
One parcel case still failing is enough to hold the release back.
05Learn
One case joins the suite, one line joins the custody record.
Learn → DetectThe return edge. The next chain is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, custody recording, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Custody-chain discovery and automation-boundary work.
02Carrier, directory and handover sources.
03Item-to-recipient and handling-route rule mapping.
04Manifest and dock-scan ingestion.
05Item, recipient and route binding.
06Completeness scoring and review routing.
07Manager release workflow.
08Mailroom-platform integration.
09Custody and screening cases.
10Guardrails and handover controls.
11Parcel-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne site, one yearProductionProduction mailroom workflowAdvancedMultiple sites / entities
Introduced at Pilot
Chain recording to your routes✓✓✓
Office manager release✓✓✓
Inbound-volume baseline✓✓✓
Introduced at Production
Reporting by recipient group—✓✓
Release workflow in your systems—✓✓
Approved write-back—✓✓
Carrier-manifest integration—✓✓
Introduced at Advanced
Multi-site directories——✓
Cross-site custody packs——✓
Large inbound loads——✓
Multi-site custody controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, inbound volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your sites and the recipient directory behind each→Site mapping and inbound captureWeek 1
02Representative manifest, scan and handover records→Record binding, route logic and the custody baselineWeek 2
03Your handling routes and holding policy→Route mapping, chain binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Carrier, directory and scanner-source assessment, then integration setupWeek 2
05Handovers you would not want traced→Custody cases and the evaluation runWeek 4
06What no delivery record may settle→Completeness scoring, review routing, guardrails and release controlsWeek 3
07A named office manager who releases→Release workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Width here is time genuinely worked and not drawn space, and so a pair must share the fifth week.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Mailroom workflow discovery, route mapping and the automation boundaryW2Source integration and the custody-chain baselineW3Chain recording, holding logic and release controlsW4Evaluation suite, custody cases and failure-mode testingW5Scanner integration, pilot items and targeted correctionsW6One mail year run under the office manager, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for. The fifth week takes two because the work does.
At the end of W6When the custody record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Facilities AI agent
Build a mailroom agent around the handover nobody can put a name to.
Show us one item and the chain it left behind. Who may accept a parcel on your floor? Whoever your recipient directory names, and never the agent, which records that acceptance and will not make it. An unmatched item is a holding problem, and it ages against your policy.
