GO UP
ALERTIFY ORIGINAL RESEARCH / 08 OCTOBER 2026

The eSIM Recovery Test: Who Gets You Back Online When Connectivity Fails?

Every eSIM provider promises connectivity. Far fewer explain what happens when that promise fails. Alertify examines the recovery procedures of seven travel eSIM providers, from troubleshooting and profile replacement to human support and refunds.

Research: Recovery readiness Sample: Seven eSIM providers Method: Public-document audit Review date: 31 October 2026

It is 11:30 at night. You've just arrived in a foreign city. Your travel eSIM is installed. Your phone shows signal bars. But the map will not load, the taxi app cannot connect, and the hotel confirmation is buried in an inbox you cannot open.

You purchased connectivity. What you need now is recovery.

This distinction receives surprisingly little attention in the travel eSIM market. Providers compete on price per gigabyte, country coverage, 5G availability, activation convenience and increasingly unlimited data.

Yet when something goes wrong, the customer encounters a different product entirely: troubleshooting instructions, account systems, replacement policies, automated assistants, customer support agents and refund procedures.

The connection may depend on several companies. The customer usually sees only one.

That is the central problem investigated in the eighth Alertify eSIM Research study: how recoverable is a travel connectivity product when its initial promise breaks down?

RESEARCH THESIS

Connectivity reliability is not only the probability that a service works. It is also the ability to restore that service when it stops working.

THE PROBLEM

A working network and a recoverable product are not the same thing.

Travel eSIM products combine different layers of technology and commercial responsibility. The customer purchases a plan from a provider, installs a digital SIM profile, registers on an available mobile network and expects usable internet access.

Between those steps, several things can fail. A profile may not install correctly. The device may select the wrong data line. A plan may not be provisioned for the destination. The eSIM may register with a local operator without establishing a usable data session. Network selection, APN settings or roaming permissions may require correction.

The underlying operator can also experience local coverage or network problems. In that case, the travel eSIM provider may not directly control the failed infrastructure, but it still owns an important part of the customer relationship.

The provider can explain the problem, identify available alternatives, authorize another profile where appropriate, direct the customer toward a supported network or clarify the applicable remedy.

That response is part of the product experience. It should be evaluated separately from network speed.

The recovery chain

STAGE A Failure identified

The customer recognizes that mobile connectivity is unavailable.

STAGE B Diagnosis

The issue is narrowed to device, plan, network or provisioning.

STAGE C Intervention

Settings are corrected, a network changes or a provider takes action.

STAGE D Usable recovery

Mobile data works again, or the customer receives a clear remedy.

A provider may perform well at one stage and poorly at another.

Extensive troubleshooting articles can reduce simple support requests. But they do not automatically demonstrate effective escalation. A chatbot can provide immediate answers without solving an account-specific problem. A refund may compensate the customer financially while leaving them disconnected for the remainder of the trip.

These are different outcomes. Combining them into one generic customer satisfaction score would conceal useful information.

WHAT THE DOCUMENTS REVEAL

Four findings from the recovery-readiness audit.

Alertify reviewed publicly available provider instructions covering connection failures, replacement or reinstallation procedures, support access and financial remedies.

The documents reveal meaningful differences in the recovery options available to customers. They do not establish which provider answers support messages fastest or resolves the highest proportion of real incidents.

FINDING A / PROFILE CONTROL

Reinstallation policies differ substantially.

Some providers publish self-service reinstallation paths. Others use single-use activation codes or require provider intervention. Recovery depends partly on which product the traveler purchased.

FINDING B / SUPPORT ACCESS

Support availability is not proof of resolution.

Around-the-clock assistance and automated troubleshooting can improve access to help. Neither establishes how quickly an agent diagnoses a specific account or network problem.

FINDING C / CUSTOMER REMEDIES

Replacement, refunds and credits are different outcomes.

A replacement may restore service. A refund may compensate the buyer. Store credit may support a future purchase. Customers should understand these distinctions before an incident occurs.

FINDING D / ACCOUNTABILITY

Recovery becomes more complicated when responsibility is divided.

A travel eSIM brand may sell the plan while another company provides the underlying network. Clear escalation and ownership of the customer problem become important differentiators.

The deletion problem is particularly revealing.

Removing an eSIM is sometimes presented casually as a troubleshooting action. That can be a costly mistake.

Apple explicitly advises users not to erase an eSIM as a troubleshooting step unless directed by their carrier. Its guidance explains that obtaining another eSIM may require contacting the carrier. [1]

Provider-specific procedures can be more flexible than that general warning suggests. But flexibility is not universal.

The distinction is important: a recoverable eSIM account does not necessarily mean a reusable activation code.

PROVIDER DOCUMENTATION AUDIT

Seven providers. Different recovery pathways.

This comparison examines what each provider publicly documents about recovering from connectivity or installation problems.

It is a comparison of published options and conditions, not a ranking of actual customer service performance.

How to read this table: "Self-service" indicates that a published route allows at least one relevant recovery action without first obtaining an individual support decision. "Conditional" means the remedy depends on circumstances or eligibility. "Support-led" indicates that provider assistance may be necessary. None of these labels guarantees a successful outcome.
Provider Documented recovery path Important conditions Evidence
Airalo Travel eSIM marketplace IN-ACCOUNT REMEDY
Eligible orders can access an account-based refund request. Installation issues or non-working eSIMs may also have a replacement option.
Eligibility depends on order status. The documented in-app refund route uses Airmoney credit. Support is available through app chat or WhatsApp. Refund and replacement guidance ↗
Nomad Travel eSIM provider CONDITIONAL
Troubleshooting is documented. Non-functioning profiles may qualify for replacement or refund after provider assessment.
Some plans are single-use and device-specific. Refund requests generally must be submitted within 30 days. Removing certain single-use profiles can affect eligibility. Replacement guidance ↗

Refund policy ↗
Ubigi Transatel / NTT SELF-SERVICE OPTION
The Ubigi app documents reinstallation of an accidentally deleted eSIM profile.
The published reinstallation limit is five times. Account-specific problems can be escalated through the customer support form. Refunds are conditional. Reinstallation procedure ↗

Support channels ↗
GigSky Travel connectivity SELF-SERVICE REPLACEMENT
The GigSky app documents a replacement process for accidentally deleted profiles associated with active plans.
The documented self-service replacement allowance is up to two times. Support becomes necessary when the limit is reached or the option is unavailable. eSIM recovery procedure ↗
Saily Travel eSIM provider SELF-SERVICE OPTION
Saily documents eSIM reinstallation through the same account. Live chat and email support are also available.
Reinstallation must follow Saily's account procedure. Refunds for activated or used plans are not automatically guaranteed. Reinstallation guide ↗

Refund policy ↗
Yesim Travel connectivity SUPPORT-LED
Yesim publishes detailed connection troubleshooting instructions and provides live chat and email support.
The published connection guidance warns users not to delete the profile or scan the QR code again. Provider assistance may be required for unresolved issues. Connectivity troubleshooting ↗

Contacting support ↗
Orange Travel Travel eSIM service SUPPORT-LED
Device troubleshooting and technical assistance are documented.
Its published iPhone QR-code instructions warn that an eSIM can be downloaded only once and that customer service cannot issue another QR code under that procedure. Installation warning ↗

Troubleshooting guide ↗

Source: Alertify review of publicly accessible provider documentation, 31 October 2026. The sample is purposive, not statistically representative of the travel eSIM industry. Product rules may differ by plan, market, device and purchase date.

WHAT THE COMPARISON MEANS

The most revealing difference is what happens after the customer loses control.

The seven-provider review does not reveal a universal recovery model.

Instead, it reveals three broad approaches.

Self-service recovery

Some providers let customers perform specific recovery actions from an account or application.

Ubigi documents reinstallation of an accidentally deleted profile, subject to a published limit. GigSky provides an app-based replacement path for eligible deleted profiles. Saily also documents reinstallation through the same account.

These policies offer something valuable: a customer may not need to wait for an individual support decision to begin a qualifying recovery process.

However, the existence of a self-service feature does not prove that recovery succeeds in every case.

Support-mediated recovery

Other situations depend more directly on provider support.

Yesim's troubleshooting guidance explicitly warns against deleting and rescanning an installed profile. Nomad describes support involvement for certain replacement and refund scenarios.

That does not make either provider inherently less reliable.

A well-trained support team with access to provisioning and network information might resolve a complex problem faster than an automated procedure.

But it creates another research question: how quickly can the customer reach someone who can actually change the outcome?

Financial recovery

Refunds add a third layer.

Airalo documents eligible in-app refund and replacement routes. Nomad distinguishes unused plans from activated plans and applies conditions to partial refunds. Saily documents a full refund route for qualifying non-activated plans within 30 days, while activated-plan refunds depend on further conditions.

These are useful commercial protections. But they solve a different problem.

A refund can compensate for a failed purchase. It does not necessarily restore navigation, online payments or business communications during the trip.

THE IMPORTANT DISTINCTION

Refundability measures whether money can be recovered. Recoverability measures whether connectivity can be restored. A serious eSIM comparison needs both.

HUMAN SUPPORT

The problem with measuring support by whether it is available.

Customer support availability is one of the most frequently advertised benefits in travel connectivity.

Several providers offer assistance around the clock. Saily documents continuous live chat through its application, with email ticketing as another route. Yesim publishes live chat and email support, including the ability to continue some conversations over email. Ubigi describes a support form for account-specific assistance alongside automated guidance.

Those details matter.

But they describe access to support, not independently verified recovery outcomes.

A chatbot that replies instantly may create a very short first-response time. That response might merely repeat information the customer has already read.

Conversely, an agent who takes longer to respond but immediately identifies a provisioning problem may create a shorter total recovery journey.

The distinction becomes important when comparing automated support systems with human-assisted troubleshooting.

First response is not first meaningful response.

Alertify proposes separating three events in future live recovery testing:

  • Initial acknowledgment: the first automated or human reply confirming that the request was received.
  • First meaningful diagnostic response: the first action or explanation that materially advances the investigation.
  • Usable service restoration: the point at which cellular data works again under a defined verification test.

These should be measured separately.

A provider could perform well on the first metric and poorly on the third. Traditional support availability claims would not reveal that difference.

PROPOSED FIELD-TEST SCENARIOS

Three failures that would expose the real quality of recovery.

To move beyond published policies, a future field test should evaluate actual incidents under comparable conditions.

The scenarios below define what should be investigated. They are not presented as experiments already completed.

SCENARIO A

Signal, but no internet

The eSIM is installed and the phone registers on a mobile network, but applications cannot transfer data.

The test should establish whether support checks the correct data line, roaming configuration, APN, plan status and supported local network.

KEY MEASURE: TIME TO USABLE DATA
SCENARIO B

Installation or activation failure

A legitimate purchase cannot complete installation or activation despite a compatible, unlocked device and suitable internet access.

The test should examine whether the provider identifies the failure, offers a valid next step and authorizes replacement or another remedy where appropriate.

KEY MEASURE: TIME TO WORKING PROFILE
SCENARIO C

Connectivity disappears after a border crossing

An existing travel eSIM works in one supported country but does not establish usable service after entering another.

The test should determine whether the provider can identify the permitted local networks and restore service without unnecessary profile removal or repurchase.

KEY MEASURE: CROSS-BORDER RECOVERY

These scenarios should use genuine, documented incidents and controlled device configurations. A credible test must not manufacture false faults or deceive support agents into investigating fictional technical failures.

A BETTER MEASUREMENT FRAMEWORK

What should the eSIM industry measure?

The most valuable metric may not be customer support response time.

It may be the total time a traveler remains without usable connectivity.

Introducing Time to Usable Recovery

Alertify proposes Time to Usable Recovery (TTUR) as a central measurement for future recovery research.

TTUR measures the elapsed time between a clearly identified service failure and independently verified restoration of usable mobile data.

A simple verification method would require disabling Wi-Fi, confirming that the intended eSIM is selected for mobile data, successfully loading two independent websites and maintaining a usable connection for a predefined observation period.

The test should record whether restoration required the traveler to use Wi-Fi, another SIM, a replacement plan or assistance from the provider.

These dependencies matter because recovery can be especially difficult when the failed eSIM was the traveler's only available internet connection.

Time to first meaningful response

Time until the customer receives a relevant diagnostic action or case-specific explanation, excluding generic automated acknowledgments.

Time to usable recovery

Total elapsed time from a defined failure event to verified restoration of usable cellular internet access.

First-contact resolution

Whether the problem is resolved during the initial support interaction, without a further handoff or new case.

Customer intervention burden

Number and complexity of actions required from the traveler, including repeated diagnostics, screenshots and changes to network settings.

Replacement accessibility

Whether a qualifying customer can obtain a replacement profile or equivalent working service, and which conditions apply.

Remedy completion

Whether an unresolved incident receives a clearly communicated outcome, such as an approved refund, replacement, credit or documented denial.

A future benchmark should publish results for these measures separately. Combining them prematurely into one weighted score would hide the differences between technical restoration, customer effort and commercial remedies.

It should also report the number of tested incidents and the proportion that remained unresolved. Excluding failed recoveries would make an average recovery time misleading.

INDUSTRY IMPLICATIONS

Recovery is becoming a distribution problem.

The implications extend beyond standalone travel eSIM applications.

Connectivity is increasingly offered through other customer relationships: travel platforms, loyalty programs, financial services, accommodation providers and digital services.

A traveler who purchases an eSIM through a third-party distribution channel may not understand which company controls activation, which company owns the underlying network relationship or which company can issue a replacement.

That uncertainty creates a commercial problem for embedded connectivity.

The customer remembers where the purchase happened.

Imagine an airline selling connectivity during the booking journey. The passenger lands, cannot connect and asks the airline for help.

The airline may have no technical control over the eSIM service. But from the customer's perspective, the airline introduced the product and facilitated the purchase.

A similar problem arises when connectivity is bundled into a banking, hotel or loyalty application.

This makes recovery design part of partner selection.

B2B buyers should therefore investigate more than API availability, wholesale pricing, destination coverage and commercial commissions.

They should ask who owns the incident, how technical escalation works, whether profile replacement can be automated, what customer data is required for diagnosis and how service failures are reported.

Recovery capability may become more valuable than another coverage claim.

Adding a country to a coverage map can expand the addressable market. Improving recovery can protect the existing customer relationship.

For a traveler, that distinction is practical rather than theoretical. A failed connection during a short trip can consume a meaningful part of the value of the purchase.

For a distributor, unresolved failures can create extra support contacts, refund administration, complaints and reputational exposure.

Those consequences are reasonable business risks, although this documentary audit does not quantify their frequency or financial cost.

The next generation of eSIM partnerships should evaluate recovery procedures before they become customer-facing problems.

PRACTICAL BUYER INTELLIGENCE

Four questions worth asking before buying.

Travelers cannot always predict a connectivity failure. But they can reduce uncertainty about the available recovery options.

Can the eSIM be reinstalled?

Check whether the provider uses a single-use activation code, permits reinstallation or provides a replacement process. Do not assume that deleting a profile will allow the same QR code to be used again.

Can support investigate a technical problem?

Look for a clear support route and understand whether assistance is available through an app, website, email or another channel. The ability to contact support without relying exclusively on the failed eSIM is particularly useful.

What happens if the plan never works?

Review the provider's installation, replacement and refund conditions. An unused plan and an activated plan may receive different treatment. Keep purchase confirmation and relevant error messages.

What should never be done without instructions?

Avoid deleting the installed eSIM, repeatedly scanning an activation code or resetting settings without understanding the consequences.

The safest next step depends on the provider's documented procedure and the condition of the installed profile.

Travelers facing an active connectivity problem can also use the Alertify eSIM Troubleshooting Assistant for device-specific guidance.

RESEARCH TRANSPARENCY

Methodology and limitations

This edition is an independent public-document recovery-readiness audit. It examines published provider procedures rather than claiming to measure live customer support performance.

Alertify reviewed official help-center articles, replacement instructions, troubleshooting documentation, support-channel descriptions and relevant refund policies available during the research review.

Provider sample

Airalo, Nomad, Ubigi, GigSky, Saily, Yesim and Orange Travel. The sample was selected to compare different published recovery models. It is not a statistically representative sample of the market.

Research scope

Connection troubleshooting, installation failure, profile replacement, support access and refund or credit procedures.

Evidence classification

Findings are classified as documented self-service options, conditional procedures or support-mediated processes. These labels describe available pathways, not measured success rates.

What was not measured

No purchases, controlled failure simulations, live support response measurements or independently verified recovery times were conducted for this edition.

Policy limitations

Provider documentation can change. Rules may differ by plan, country, purchase channel, device or customer circumstances. Published remedies do not guarantee eligibility in every case.

Editorial independence

Providers are included for comparative relevance. Commercial relationships, affiliate arrangements or advertising do not determine the conclusions. No paid ranking is presented.

Future research: A controlled field edition should measure real incidents across comparable destinations, devices and plans. It should publish raw recovery timings, unresolved-case rates, escalation records, test conditions and limitations.

This distinction between documented capability and independently measured performance is essential to the credibility of the Alertify eSIM Research Series.

PRIMARY SOURCES

Research references

The following official manufacturer and provider documentation supports the observations in this study. Accessed or reviewed on 31 October 2026.

ALERTIFY RESEARCH / CONCLUSION
The next eSIM competitive advantage may be how quickly customers recover.

Travel eSIM comparison has spent years concentrating on what happens before a customer purchases a plan: price, data allowances, country coverage, network access and installation convenience.

Those factors remain important. But they provide an incomplete picture of product quality.

This research finds that published recovery procedures differ significantly. Some providers document self-service reinstallation or replacement. Others rely more heavily on support intervention or impose important restrictions on profile reuse. Refund conditions add another layer of variation.

These differences do not yet tell us which provider restores connectivity fastest in practice. That requires controlled testing.

They do demonstrate why recovery deserves to become a separate dimension of travel eSIM evaluation.

The most useful future comparison may not be which provider promises the most reliable connection. It may be which provider can demonstrate what happens when reliability fails.

An eSIM is not truly dependable simply because it connects successfully on the first attempt. Dependability also means having a clear, effective path back online.