Deliveries

Parcels, documents and lunch orders arrive all day. Agoo logs each one with a photo of its label, tells the person or team it's for straight away with a one-time collection code, reminds them until they collect it, and records who took it and how. Nothing sits forgotten at reception, and nobody argues later about whether a parcel arrived.

The deliveries log is included on every plan, Free included. Reading labels with Agoo AI uses AI credits: see Reading parcel labels.

How a parcel movesCopy Anchor Link

Received and Recipient told are both waiting. A parcel can be for:

• a person in your directory;
• a team, such as Finance or Admissions: everyone in it is told, and any of them can collect it;
• the front desk: reception keeps it and nobody is told.

When the courier doesn't know who it's for, or taps I don't know, it goes to your organisation's default recipient: the front desk, unless an Owner or Admin chooses a person or a team instead.

Where parcels are loggedCopy Anchor Link

Everyone is told the same way, whichever way the parcel came in.

Reception logs a parcelCopy Anchor Link

Guards in guard mode log parcels at the gate the same way, from Parcels on the gate device.

A courier logs a parcel at the kioskCopy Anchor Link

Turn on the Delivery button for a kiosk in Console → Devices, and leave Couriers log parcels at the kiosk on in the deliveries settings (it's on unless you turn it off). On the kiosk's welcome screen, the courier taps Delivery, then I'm delivering something:

1. A photo of the label. The camera frames the label. As you choose, the photo is asked for (they can skip it), always asked for, or not asked for. The kiosk reads the label itself and shows We think it's for… with its best matches.
2. Who it's for. They tap a suggestion or search. On a kiosk that visitors use, nobody's name shows until three letters are typed, and then only a first name and an initial ("Kwame M."), as at check-out. Teams that visitors may choose are listed too. I don't know / it's for reception sends it to your default recipient.
3. What it is. Parcel, envelope, food or something else, and how many.
4. Their details. Their name, phone and courier company, if you ask for them: not at all, with a Skip, or always.
5. Done. "Thank you. Reception has been told." or "Kwame M. has been told". The kiosk goes back to the welcome screen.

If couriers don't log parcels at your kiosks, the Delivery button shows a calm page asking them to hand the parcel to reception.

The Agoo Kiosk apps log parcels with no network and send them when the connection is back. A kiosk in a browser has the Delivery button too, but it needs a connection.

The drop-off posterCopy Anchor Link

A drop-off poster lets a courier log a parcel on their own phone where there's no kiosk, for example at a side door or the gate. It's off until an Owner or Admin turns on Couriers log parcels from a drop-off poster in the deliveries settings.

1. Make the poster from the deliveries settings (Make a drop-off poster, one per site), or from QR codes → New QR code → Drop-off poster, choosing the site.
2. Print it and put it where couriers arrive.
3. A courier scans it: a page on your organisation's own Agoo address asks who it's for (three letters first, then first names and initials, from the people listed for visitors and the teams visitors may choose), a photo of the label, what it is and their name, as your settings ask.
4. The courier is told who has been told. Reception sees the parcel arrive in Console → Deliveries.

A drop-off poster is one of your plan's tracked QR codes, on every plan. While the drop-off page is off, the same poster asks couriers to hand the parcel to reception, so you never need to reprint it. Removing the site ends its posters.

What the recipient getsCopy Anchor Link

The person, or every member of the team, is told at once:

• first in Agoo Workspace, by a notification on their phone: "A parcel is waiting for you", with where it's kept and their collection code;
• then by their usual channels if the app doesn't reach them: SMS or email, and WhatsApp if they've chosen it, on paid plans. WhatsApp is never used on the Free plan.

WhatsApp messages say a parcel is waiting but never include the collection code: it comes in the app, by SMS or by email.

The collection code is six digits, made for that parcel only, and only the recipient (or their team) sees it: in the message, and under Your parcels in Agoo Workspace and the Console. Reception never sees it. A new recipient gets a new code.

Reminders follow until the parcel is collected: every 24 hours, at most 3 times, unless you change it. Food is first reminded after 30 minutes. Front-desk parcels have none. Reception can also tap Remind now on a waiting parcel (at most once every ten minutes).

If you ask for it, whoever logged the parcel is told when it's collected (Tell whoever logged it when it's collected), useful when one receptionist takes it in and another hands it over.

Your parcelsCopy Anchor Link

Everyone sees their own parcels, and their teams', in Agoo Workspace (tap Waiting at reception on Home) and in the Console. Each shows what it is, who it's from, where it's kept, when it arrived and the collection code, large, with Show this at reception. A parcel for a team says who it's for ("For Finance").

Hand it overCopy Anchor Link

What collecting takes is your organisation's choice, under Collecting in the deliveries settings:

To hand a parcel over:

1. Find it in Console → Deliveries (or on the Desk in Agoo Workspace, or in Parcels in guard mode), by recipient, courier or date.
2. Select Mark it collected and choose how: Their code, Signature, or Reception hands it over with why ("Lost their phone; I know them").
3. If someone collects for the recipient, record their name.

The record keeps the time, the method, the signature if there is one, who collected it and who handed it over. A kiosk with nobody signed in takes the code only: the recipient taps I'm collecting a parcel, types their code on the keypad, and is shown what's waiting and where to collect it. The Agoo Kiosk apps check the code even with no network.

Correct, send back or refuseCopy Anchor Link

While a parcel waits, open it to:

• Change who it's for: the new recipient is told with a new code, and the old code stops working;
• change where it's kept or what it is;
• Send it back to the sender or the courier, with a reason ("Uncollected after two weeks");
• Record as refused, for a parcel turned away at the door ("Cash on delivery; nobody ordered it").

Sending back and refusing can't be undone. Once a parcel is collected, sent back or refused, it doesn't change.

Console → DeliveriesCopy Anchor Link

Open a parcel to see its photos and its story: who logged it and where, who was told and when, each reminder, any change, and how it ended. Logged offline shows when a device logged it without a connection. Export the list as a CSV file. Home's Parcels waiting card counts what's waiting, and the page updates as parcels arrive and are collected, without a refresh.

SettingsCopy Anchor Link

Owners and Admins change the deliveries settings in Console → Deliveries → Settings. Everyone who sees deliveries can read them.

Each change is recorded in the audit trail.

Who can do whatCopy Anchor Link

Paired kiosks log parcels and hand them over by code. Console → Settings → Roles lists every permission; the new one is Change the deliveries settings.

PrivacyCopy Anchor Link

Label photos, photos of the parcel, what the AI read, riders' phone numbers and signatures are kept for 90 days after the parcel is collected or sent back, unless you choose between 1 day and 2 years under Parcel photos in retention. The parcel's record itself is kept a year after it's collected or sent back unless you choose otherwise, under Deliveries. A parcel still waiting is never deleted. Everything is in your organisation's full export, and every action on a parcel is in the audit trail. Only people who can see a parcel can open its photos.

Gate passes for itemsCopy Anchor Link