Finding stuck parcels
Sarah Chen, logistics lead at BigCo, asks which shipments are stuck in exception. Memtro lists the trackings with courier, order and latest checkpoint, so she knows which couriers to chase.
Where is this parcel, and which shipments are stuck?
AfterShip reads your shipment tracking: trackings with courier, order, status, latest checkpoint, expected and actual delivery and destination city and country, and one tracking's checkpoint history. It also lists the couriers enabled on your account. Locations stop at city and country. When asked, and once an administrator has granted the action by name, it starts tracking a shipment, changes a tracking's details, retracks an expired one and marks trackings delivered, lost or returned. It never subscribes a buyer to notifications, though buyers already subscribed may hear of a status change. Deleting a tracking is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right AfterShip tool, reads what it needs, and answers with the source cited.
These tools change something in AfterShip. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once AfterShip is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which AfterShip shipments are stuck in exception?
Where is order 1042?
Which deliveries this week were not on time?
Which couriers do we have enabled?
Start tracking 1Z999AA10123456784 for order 1042.
Sarah Chen, logistics lead at BigCo, asks which shipments are stuck in exception. Memtro lists the trackings with courier, order and latest checkpoint, so she knows which couriers to chase.
Dan Fletcher, support agent at Acme Ltd, finds order 1042 has no tracking in AfterShip. He asks Memtro to add it. Memtro starts tracking the number against the order, AfterShip detects the courier, and the shipment appears in the account's list. No buyer is subscribed.
The teams that lean on AfterShip most, a question each of them asks, and what they connect beside it.
A record in AfterShip is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Sign in at organization.automizely.com and open API keys.
Choose Create an API key and copy it. Memtro creates or changes trackings with it only for actions an administrator grants.
In Memtro, open Connections → AfterShip and paste it into API key.
Ask "Which AfterShip shipments are stuck in exception?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The AfterShip tools are the same everywhere.
Only when you ask, and only what it has been granted: start tracking a shipment by its tracking number; change a tracking's title, note, order id or number, courier or shipping method; retrack an expired tracking (allowed once per shipment); mark a tracking completed as delivered, lost or returned to sender; delete a tracking, permanently. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. Sign in at organization.automizely.com and open API keys.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time