eSIM for organisations

Why organisations move from roaming to eSIM

Operator roaming is usually billed per device per day and is hard to control when a team travels on different dates. An eSIM is billed as a purchased plan, so a per-trip budget is exact.

When an organisation sends people abroad, connectivity rarely gets planned the way flights and hotels do. It is left to each traveller to sort out on arrival. The result is a team of ten coming back with ten different solutions, ten different receipts, and expenses finance has to reconstruct afterwards. The real problem is not the per-person price; it is the uncertainty spread across the whole process.

This page is written for whoever owns that job inside a company — procurement, HR, an executive assistant, or the team lead taking people to a trade fair. It concentrates on process: buying, handing profiles to staff, preparing devices, and dealing with someone who gets stuck mid-trip, rather than on the plans alone.

What an organisation gains by planning this in advance

The first gain is a known cost. A plan bought in advance is a fixed amount per person per trip, unlike leaving each traveller to switch roaming on, where the terms and charges belong to whichever carrier that person happens to use and the company controls nothing until the bill arrives.

The second is the traveller's time. Someone flying in for an important meeting should not spend the first hour after landing looking for a SIM counter or filling in a registration form in a language they cannot read. A profile prepared in advance has them online before they have left the aircraft.

The third is paperwork. Buying centrally produces one set of receipts that matches the trip, instead of scattered slips from overseas shops — some in a local language, some missing whatever finance needs.

Central purchasing, or letting staff claim it back

Organisations that send people out regularly usually find central purchasing pays for itself in time and paperwork even when the per-head cost is similar. Somewhere that sends people abroad occasionally can reasonably stay with reimbursement — as long as the rules on limits and required documents are set in advance.

Name one owner and set the sequence

This process fails most often when nobody clearly owns it. One person buys, another sends the email, a third answers questions, and in the end no one knows who has installed what. Name a single owner from purchase through to the end of the trip, and make sure every traveller knows who to message first.

1. 1Collect the team's details before orderingYou need each person's destination, outbound and return dates, and the phone they will carry. Those three decide which plans and how many.
2. 2Check every device is capableThe phone must support eSIM and must not be carrier-locked. On company devices under a management system, check with IT that policy allows adding a profile at all.
3. 3Order as one batch and ask for the paperwork before payingTell us what documents you need before payment so they are issued in the company's name correctly the first time. Correcting them afterwards is far more work.
4. 4Hand each profile to its own personSend install details to each individual rather than posting them in a group chat, and state clearly whose plan it is, which country it covers and which dates.
5. 5Have everyone install before departure and report backSet a deadline of at least a day before the flight and ask for confirmation, so there is time to help anyone who gets stuck before they are at the airport.
6. 6Publish the support route and what to includeTell the team in advance where to go if the connection fails and what to include: phone model, OS version, country and symptom. Having that ready cuts the back-and-forth considerably.

The devices are where the plan usually stumbles

Personally owned phones

If people use their own phones, check two things: whether the handset supports eSIM, and whether it is locked to a carrier. Some contract handsets are locked and cannot take another provider's profile — a condition set by that carrier, so the employee has to ask them directly.

Company phones under device management

Phones managed through a device-management system may carry policies that restrict adding network profiles or changing certain settings. Those restrictions come from your own IT team rather than from the plan supplier, so have that conversation before ordering rather than after someone fails to install.

Check whether your team's phones support eSIM

Sizing the team's data by the kind of work

People on the same team do not use the same amount. Someone working a stand uses more than someone flying in for two days of meetings, and anyone joining video calls back to head office every evening uses more than both. Giving everyone the same size usually misses in both directions: some finish with most of it unused, others run out mid-trip.

Estimate each traveller's data need

Teams covering several countries in one trip

Where an itinerary spans countries, a regional plan is usually easier to administer than one country plan per person per stop, because it cuts down how often a traveller has to touch settings on the move — the moment most mistakes happen. What to verify is the covered-country list: every country on the schedule has to be on it, including transits if people need to work while they wait.

A common case is one team with different schedules — two countries for some people, five for others. There is no need to buy the same thing for everyone; match each person's real route and record who got what, so questions during the trip can be answered immediately.

Validity against a schedule that can change

Work trips move more often than holidays: meetings shift, flights are cancelled, and someone occasionally stays two extra days at short notice. How validity is counted is set by each plan, so read the terms on the one you buy and leave more room than an exactly-fitting schedule.

If someone extends and the plan is running out, the options are topping up, where that plan supports it, or buying another. Which applies depends on the plan held, so have the owner message us before buying again — and do it while data remains, because installing a new profile needs a connection.

Documents for finance and procurement

Always state your documentation requirements before payment: the exact legal entity name, what has to appear on the document, and the format your finance team needs. Getting it right the first time is much easier than asking for a correction later, particularly when one order covers several travellers.

If your organisation splits costs by cost centre or project, say how you want the orders separated at the point of buying. Splitting them up front saves finance apportioning totals afterwards. Talk it through with us on LINE at https://lin.ee/skDPoNx (@esimonline) or by email at esimonline.asia@gmail.com before you order.

When a traveller gets stuck

The most common problem is landing and finding nothing connects, which the traveller can usually clear themselves in a few minutes. Put short instructions in the pre-trip email: cycle aeroplane mode once, confirm the purchased line is switched on, confirm mobile data is assigned to it, and confirm data roaming is enabled for that line. Where those settings sit varies by manufacturer and OS version.

If that does not do it, message us. What speeds things up most is complete information in the first message — questions bouncing back and forth across time zones cost hours.

• The traveller's name and the email used for the order
• Phone model and OS version
• The country and city they are in at the time
• What they are seeing, with a screenshot if they can take one
• What has already been tried, such as aeroplane mode or manual network selection
• How the traveller can still be reached, such as hotel Wi-Fi

After the trip, keep what you learned

Spend ten minutes when the team is back and ask three questions: who ran out early, who came home with most of it unused, and who had trouble installing. Those answers make the next order far more accurate, especially on sizing, which is hard to reason about in theory and easy to read from what just happened.

If your organisation travels regularly, keeping that record for a few rounds gives you your own benchmarks per trip type — far more useful than a general traveller average, because they reflect how your people actually work.