The operational problem in a travel eSIM business is not complexity, it is arithmetic. Every task that requires a person costs roughly the same whether the order was $10 or $10,000, and at an average order value around $28 there is very little room for anything manual.
This covers what breaks at each stage of growth, which tasks have to be automated and in what order, what to document before the second person joins, and the single metric that determines how large the business can get.
What actually breaks as you grow
- Support volume, because it scales with orders unless the causes are removed.
- Reconciliation, because every profile is a charge you need to match to a payment.
- Refunds, which stop being individually reviewable somewhere in the hundreds.
- Rate management, as your destination list and volume tiers multiply.
- Your own knowledge, once more than one person answers customers.
What breaks, and when
| Stage | What works | What starts to break | What to build |
|---|---|---|---|
| First sales | Doing everything manually | Nothing yet | Nothing; learn from each order |
| Tens per month | Manual support, personal replies | Repeating the same answers | A help centre and canned responses |
| Hundreds per month | One person can still see everything | Reconciliation and refund consistency | Written policies, automated retention, order search |
| Thousands per month | Nothing manual survives | Support headcount, rate management | Deflection, self-service reissue, dashboards |
| Multiple markets | Single-language operation | Time zones, languages, local expectations | Coverage that follows customers, not your office |
The transition that catches people out is between hundreds and thousands of orders a month. Up to a few hundred, one attentive person can hold the whole business in their head, remember individual customers and make sensible one-off decisions. Past that, the same approach produces inconsistency, slow responses and a founder who cannot leave the business for a week.
Global travel eSIM retail spend
Source: Kaleido Intelligence. Growing with the category means your operational load grows with it unless the per-order costs come down.
Source: Kaleido Intelligence, 2026.
The tasks that must stop being manual
| Task | Manual cost at scale | What removes it |
|---|---|---|
| Resending an activation code | A ticket per occurrence | Codes retrievable in the account area |
| Reissuing a redeemed profile | An escalation to your provider | Self-service reissue in your own tooling |
| Answering "how do I install this" | Repeated identical replies | Platform-detected instructions at delivery |
| Checking remaining data | A lookup per request | Usage visible to the customer in-product |
| Matching orders to provider billing | Hours at month end | Automated daily reconciliation |
| Deciding individual refunds | Inconsistency and escalations | A written rule applied by default |
Each row is a fixed cost per order. At a $28 average order value, any of them left manual will cap how large the business can get.
Order matters here. Code resends and install questions are the highest-volume items and the easiest to remove, which makes them the right starting point. Self-service reissue is next because it eliminates an entire escalation path to your provider. Reconciliation is less visible but becomes the most painful if deferred.
Documenting before you hire
What to write down before hiring
- The refund decision rule, with the common cases
- Diagnosis steps for the five recurring failures
- When to reissue versus when to refund
- What to escalate to the provider, and how
- Which data an agent may access and why
- The response you send for each common case
Signs you are scaling badly
- Support headcount rising in line with orders
- Month-end reconciliation taking days
- Different agents giving different refund answers
- Nobody able to answer outside one time zone
- Rate cards maintained in a spreadsheet nobody trusts
- The founder still handling escalations
The refund rule is the document that matters most. Two agents making reasonable but different decisions about the same situation is how a business acquires a reputation for being arbitrary, and customers compare notes publicly. Writing the rule down is a smaller job than it sounds and prevents a category of problem that is difficult to unwind.
The right-hand column is worth reading as a checklist. Support headcount rising in step with orders is the clearest signal that you are scaling the cost of a design problem rather than solving it.
A sequence for growing
Measure contacts per hundred orders
This single number tells you whether you can grow. If it stays flat while orders rise, your support cost rises linearly and eventually exceeds your margin. Driving it down is the whole of operational scaling.
Automate the six recurring tasks
Code resends, reissues, install instructions, usage checks, reconciliation and refund decisions. Each is a fixed per-order cost, and at this order value any one left manual will cap your growth.
Reconcile daily, not monthly
Every profile issued is a charge against your wholesale account. Daily matching catches discrepancies while they are traceable; monthly matching turns them into an investigation nobody has time for.
Write the playbook before the second hire
Diagnosis steps, refund rules and escalation paths need to exist as documents rather than in your head. The cost of not doing this is inconsistency that customers notice and compare.
Follow your customers into their time zones
Support demand concentrates when travellers land, which has nothing to do with your working hours. Self-service and asynchronous channels carry most of it; coverage should follow your destination mix as it grows.
Review rates and quality on a schedule
As destinations multiply, rate cards and carrier changes stop being memorable. A quarterly review of rates, volumes and refund clusters by destination keeps both margin and quality from drifting.
Step one is the discipline that makes the rest legible. Most operators track orders, revenue and perhaps refund rate, and never look at contacts per order, which means they cannot tell whether an improvement worked. Once you are watching that number, every automation and every instruction improvement has a visible effect, and the ones that do not work become obvious quickly.
Frequently asked questions
Automate the tasks that cap your growth
eSIM Island provides API access, profile diagnostics, self-service reissue and real-time usage, so code resends, reissues and usage checks stop being tickets. Tell us about your volumes and we will set up access.
Book a Free Demo
Leave a Reply