Buy data for the next country, from inside the app
push.tt runs on a data connection, so the moment it is most likely to fail is the moment somebody crosses a border. A built-in eSIM store closes that gap without a shop, a SIM tray, or a roaming bill nobody approved.
Why this belongs in a push-to-talk app
Every other feature on this site assumes a connection. For a crew that stays in one city that assumption is safe, and for a crew that crosses borders it is the single thing most likely to take them off the air.
- A driver who lands without data is not on the channel, and nobody finds out until they are needed
- Roaming is bought under time pressure at an airport counter, or not bought at all
- Company-issued handsets are exactly the case where an admin should be able to sort this centrally
How it works
Choose a data plan in the Android app or management console, pay from the organisation's prepaid wallet, and assign it to the person who needs it.
- Buy one eSIM or a batch, assign immediately or keep them in the organisation pool for later
- Administrators control whether members can see plans, buy for themselves, and how many each member may hold
- Managed Android 15+ handsets can install through Device Manager; personal phones use Android's consent flow
What it does not change
An eSIM is a data pipe. It sits underneath push.tt in exactly the same place your home Wi-Fi does, and it changes nothing about who can read your traffic.
- Your conversations stay locked to your team’s handsets. The mobile network carries them without being able to open them, the same as any other network
- We do not gain the ability to read anything by also selling you the connection
The honest cost: buying anything means a payment processor and an eSIM provider learn that a purchase happened, for which destination, and when. That is new metadata leaving your organisation, it is unavoidable in any store, and it will be listed in the security model rather than left for you to work out.
The constraints that remain
These decide whether an eSIM is useful for a particular trip or handset, and none of them are things an app can engineer away.
- The handset must support eSIM and not be carrier-locked — a lot of fleet hardware is neither
- Coverage, pricing and throttling are the provider's, not ours, and vary by country
- Some countries restrict eSIM provisioning outright
- Rugged and older devices frequently have no eSIM at all, which is the hardware frontline crews often carry
Connect the next trip before departure
Choose the plan centrally, assign it to the traveller, and let the handset handle the installation route it supports.