CoverageBrandTalk to sales
Home/Use cases/eSIM for staff deployments
NGOs and aid agencies

eSIM for staff deployments

Order codes with the travel, pack labelled SIM packs in the kit, and add a new eSIM for each further 30 days.

Short answer: A deployment with data starts with the deployment order and goes on for the whole rotation. Logistics orders the codes with the travel, staff install before the flight, the kit carries packs for phones without eSIM, and a new eSIM covers each further 30 days.

  • Codes with the travel
  • No names leave your roster
  • A new eSIM each 30 days
The flow

From the deployment order to the last day of the rotation.

Four steps of a deployment with data. Pick one to see it.

01 / Step

Order with the travel

When the deployment is confirmed, logistics orders one code for each person with an eSIM phone, by country, dates, and team size.

Trigger
Deployment confirmed
Measure
Codes ready before the flight
Playbook

How to run it.

01Set up

  • Agree the plans for your countries of operation with the RoamWorks team.
  • Add data to the deployment checklist of logistics.
  • Keep labelled SIM packs for the kit.

02Before the flight

  • Send one code to each work email account. The roster of names stays with you.
  • Ask staff to install on Wi-Fi before the flight.
  • Check the SIM registration rules of the destination.

03In the field

  • Order a new eSIM before each plan ends in a long rotation.
  • Where the networks are down, use the satellite and radio kit.
Measure

Three numbers to review in a pilot.

  1. Codes ready before the flight
  2. Staff online on arrival
  3. New eSIMs per rotation
Behind it

The products behind it.

What to pass
CountryStart dateDeployment lengthTeam sizePhone format
Good to know
  • Data only, with no local number.
  • The plan works where the local mobile networks work.
  • No names: you assign the codes.
  • SIM registration rules differ by country.
The solution

NGOs and aid agencies

Order data for each deployment before the flight: one-time codes for staff with eSIM phones, and labelled SIM packs in the deployment kit. The roster of names stays with you.

See the solution →
Commercial model

You set the retail price.

Buy at partner rates, keep the customer relationship, and agree the support split privately. One catalogue, three commercial shapes.

01
Partner rates

Wholesale pricing before your retail price.

02
Your retail price

You decide what the customer pays.

03
Private terms

Support, refunds, and volume in the agreement.

Pilot

From first step to first order.

Start with a short pilot. Review it, then add the next desk, route, or market.

01

Scope

List your countries of operation and your deployments for a quarter.

02

Pilot

Run one deployment with codes and a kit with packs.

03

Extend

Add the other teams and the long rotations.

Start a pilot
Answers

Before you choose

Short answers to the common questions. The partner agreement sets the final terms.

Last updated 28 October 2026 · Reviewed by Roamworks
Does the plan work when the networks are down?

No. The plan works where the local mobile networks work. Where they are down, the team uses its satellite and radio kit.

Do you need the names of the staff?

No. You assign the codes. RoamWorks needs the country, the dates, and the number of codes.

What about SIM registration?

SIM registration rules differ by country. Check them for each destination before the deployment, and plan the ID that staff need.

What if a phone has only a SIM slot?

Put a labelled SIM pack in the kit, one for each 30 days of the deployment.