A Yipii tracking link stops working at an expiry you set when you create it. Before that point you can see how many times it has been opened, and you can switch it off early. The person receiving it needs no login and no app.
The expiry is set before you send
So the decision that matters happens in the dialog, before anything goes out. You choose how long the link stays valid, and that setting travels with it. If the job is a delivery this afternoon, the link does not outlive the afternoon. Nobody has to remember to close it.
That matters because a link sent by WhatsApp does not stay where you put it. It gets forwarded to whoever asked next. With an expiry attached, forwarding stops being something you have to police, because the link closes itself on the schedule you picked.
Every active link on one screen
Because every link carries its own lifespan, the sharing screen reads as a list you can act on rather than a set of links you have lost track of. Each active link is a row: how many times it has been opened, and when it runs out. That is the screen operators actually live on once sharing gets used more than once a week.
The view count tells you plain things. A link you sent to one client, opened far more times than that client could account for, has been passed around. A link with no views at all means the message never landed, which is worth knowing before the phone rings asking where the van is.
Switching a link off early
Jobs change. Work gets reassigned to another vehicle, a client relationship ends, a link reaches someone you did not intend. You can switch that link off before its expiry, and the live view goes with it.
There is nothing to uninstall at the other end, because there was never an app or an account. That is the part I like about sharing a link instead of handing out a login. A login has to be changed and everyone told. A link is one action and it is done.
The link is not a record
One boundary worth saying out loud. A live link is a window on one vehicle for a set period, not a record, and anything someone saw while the link was open cannot be unseen. The trip history behind it stays in the platform, queryable for the length of your contract rather than a fixed retention window.
Operators already running links every day
None of this is theory. Maltese operators run these links day to day with their own clients, for deliveries and for subcontracted work, not only for school runs. The questions they ask us are about the list and the expiry, not about the act of sending.
When the sending should happen by itself
Once you are sending several links a day, doing it by hand stops making sense. If a booking or dispatch system already knows the job, it can create and send the link itself , with the expiry, the schedule and the valid period taken from what that system already holds. Our API is already integrated with trip booking and dispatch systems in use by fleet operations in Malta. Connecting a new system of that kind usually takes under two days, depending on what is being integrated.
A live link is a window on one vehicle for a set period, not a record, and anything someone saw while the link was open cannot be unseen.
Book a 15-minute walkthrough and bring the questions you would ask any supplier.
Chris Bartolo, Yipii IoT and Mobility