It installs on a phone. It is not in an app store.
Those two sentences are the whole product today. The rest of the line, on both sides of it, follows before anything else on this page.
Where LiveTrack stands today
Four things, and they work now.
The portal installs on the home screen. It carries the forwarder’s company name and icon, and opening it goes straight to the customer’s dashboard — not to a sign-in page and not to a browser tab that has to be found again.
Four push notifications. Delayed, arrived, out for delivery, delivered — four of the record’s status codes, and the only four that fire.
Each push opens that shipment. Tapping one lands on the tracking page for the shipment it is about, not on a home screen the customer then has to search.
Dead subscriptions are cleared automatically. A phone that reinstalled its browser or wiped the icon stops counting as a reachable subscriber, without anyone tidying a list.
One thing, and it is the obvious one.
There is no app store listing. Not on the App Store, not on Google Play. A customer installs it the way any web page is installed on a phone — open the portal, add to home screen. From then on it has the forwarder’s icon and it behaves like an app, but nobody found it by searching a store, and this page will not carry a sentence that implies they could.
That is why the label on this page is Stage 1 and not something warmer. When the store listing exists, this paragraph changes. Until then it stays.
The customer stops asking because the phone already told them.
Four moments matter to the person waiting for the cargo, and they are the four that are sent — including the one nobody wants to send. Every one of them names the clock it was read in.
What installs is the portal, not a second product.
There is no separate app, no separate password and nothing to keep in step. The icon on the customer’s home screen opens the same fifteen screens they would reach in a browser — the shipments in progress, the quotations waiting, the invoices that still carry a balance.
The sales page is not allowed to be ahead of the code.
One of the twenty checks that stop a release does not read the product at all. It reads pages like this one.
check_mockup_claims
It fails a release when the place that sells the thing claims more than the thing does. This feature is marked state: 'building' where it is defined, so the word on this page is Stage 1. Not “live”, not “real-time”, not a screenshot of a store listing that does not exist.
Why it is stated here
A forwarder who buys this and then tells its own customer to search the App Store has spent its credibility on CBMGO’s behalf. Finding the edge in a demonstration costs both sides forty-five minutes. Finding it in front of a customer costs more than that, and the forwarder is the one standing there.
Stated once more, plainly.
Installed on the forwarder’s own phone during the demonstration.
The portal is put on the forwarder’s home screen during the call, and a delivered push is fired at a demonstration shipment to show where it lands. If Stage 1 is not far enough, that is a fair answer and it takes five minutes to find out.