“Where is
my parcel?”
Answered before they ask.
The single most repeated question in New Zealand logistics. Your tracking page today is a gateway — it takes the enquiry and routes it. This is a concept for the ninety seconds before someone gives up on tracking and picks up the phone.
“A tracking number that says “in transit” answers none of the three things the customer actually wants to know.”
What we found reading nzpost.co.nzThe parcel that has not moved since Thursday
Someone refreshes a tracking page for the fourth time. The status has not changed. They do not know whether that is normal, whether it is lost, whether anyone is looking, or whether they should buy another one. So they ring you — and the person who answers has to start from nothing.
We read your own tracking page. It offers a parcel enquiry and a link to FAQs, and it does not state a delivery timeframe, when a parcel is considered lost, how an investigation works, or what compensation applies.
What happens now
A status code, a link to an enquiry form, and a call that begins with “can I take your tracking number”.
What it costs
Every unanswered tracking check becomes a contact. The cheapest contact is the one the tracking page prevented.
What the concept does
Turns the status into an answer, in the wait, and hands the hard ones to a person with the file already open.
Every delivery moment, one pattern.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every waiting moment in a parcel journey
Six real gaps between ordering and holding the box, and what each one could say instead of a status code.
They stop refreshing, because the page finally says what the silence means.
The gap gets a reason, so a quiet week stops looking like a lost parcel.
They get their afternoon back, and the driver gets somewhere to leave it.
A card in the letterbox turns into an address, a time and a plan.
The photo settles it, or the problem starts on the day it happened.
The search stops being invisible, so they stop ringing to check it is happening.
Four steps, every time.
- The signalSomething in your own systems says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get a customer who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected, nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
One tracking number. Four honest answers.
The same “in transit” status means four different things. Choose a situation and see what the customer could be told instead of a status code.
A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.
The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.
What it refuses to say
Most of the harm in delivery communications comes from confident answers. These checks exist to stop them.
Drafts are held against Fair Trading Act 1986, Consumer Guarantees Act 1993, and the Privacy Act 2020.
Press run to see what it catches — and what it refuses to produce at all.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
The parcels that need a person today
Illustrative and fictional. No production access is requested by this concept.
| Situation | Volume | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Running normally | — | Reassurance, no action needed | Nobody — closes itself | Answered |
| No scan for 3+ days | — | Proactive note, site asked to look | Depot response | Looking |
| Delivery attempted, card left | — | Collection point, ID needed, redirect offered | Nobody — closes itself | Answered |
| Arrived damaged | — | File assembled for a claims decision | A person | Held — decision |
| Address looks wrong | — | Draft held | Customer confirmation | Awaiting reply |
| Returned to sender | — | Explanation plus options | Sender contact | Awaiting approval |
Volumes are deliberately blank. This concept has no NZ Post data and does not estimate parcel numbers.
Every draft carries its own working.
Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.
This matters most on the day someone asks why it said what it said.
- Artefact
- Tracking answer — no scan for three days
- Read
- Scan history (placeholder) · network expectations (placeholder) · published delivery information from nzpost.co.nz
- Rules held
- Fair Trading Act 1986 · Consumer Guarantees Act 1993 · Privacy Act 2020
- Refused
- No delivery date, compensation amount, hold period or claim outcome was stated — none of these were published on the pages we read.
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
Why this concept, for NZ Post, now.
Nothing on this page is modelled, projected or borrowed from a slide. These are your own published facts, and the concept above is built on them.
The same evidence, on one page you can print or send: the one-pager →
What this will never do
It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
One parcel situation — the parcel that has stopped moving. Six weeks. Not claims, not the contact centre, not the app.
Access
Your published delivery information and the status codes themselves. No customer records. No addresses. No parcel contents.
Scorecard
Tracking checks that did not become a phone call. Answers a person agreed with. Proactive notes sent before the customer chased. One CX lead’s honest answer to “is this better than the status code?”
Fail any line of the scorecard and we change the design or stop.
What a pilot actually asks of you.
Written out in full, because the honest version of this is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
One parcel situation — the parcel that has stopped moving. Six weeks. Not claims, not the contact centre, not the app.
Read-only access, nothing that writes
Your published delivery information and the status codes themselves. No customer records. No addresses. No parcel contents. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: Tracking checks that did not become a phone call. Answers a person agreed with. Proactive notes sent before the customer chased. One CX lead’s honest answer to “is this better than the status code?” Fail any line of that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how NZ Post actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.