Travel eSIM in the operator app
Show a travel plan where the roaming of the plan stops, sell it at your price, and remind before departure.
Short answer: A travel plan in your app starts on the roaming page and ends with data at the destination. The app shows it only where the roaming of the plan stops, the customer pays in your checkout, and the home line stays in the phone.
- Only where roaming stops
- Your checkout and your price
- The home line stays on
From the roaming page to data at the destination.
Four steps of a travel plan in your app. Pick one to see it.
Check the roaming
The app checks the country of the trip against the roaming of the plan. Inside the roaming, it shows no offer.
- Trigger
- Customer opens the roaming page
- Measure
- Roaming pages with an offer
Show the travel plan
Outside the roaming, the page shows one to three travel plans for the trip, at your price.
- Trigger
- Country outside the roaming
- Measure
- Attach rate on the roaming page
Pay in your checkout
The customer pays in your checkout, and the API returns the eSIM to install.
- Trigger
- Plan added
- Measure
- Orders per 1,000 roaming pages
Install before departure
Two days before the trip, the app reminds the customer to install on Wi-Fi. The home line stays in the phone.
- Trigger
- Departure in 2 days
- Measure
- Installs before departure
How to run it.
01Set up
- Map the roaming of your plans and the countries it leaves out.
- Connect the eSIM API to the roaming page and the add-on list.
- Agree your prices and the refund rules with the RoamWorks team.
02In the app
- Show the travel plan only for countries outside the roaming of the plan.
- Show one to three plans that cover the days of the trip.
03Before departure
- Remind the customer to install on Wi-Fi two days before the trip.
- Say that the home line stays in the phone.
04Care
- Give the care team the same plans for customers who ask about roaming.
- Use the order lookup of the API for install questions.
Three numbers to review in a pilot.
- Attach rate on the roaming page
- Orders per 1,000 roaming pages
- Installs before departure
The products behind it.
eSIM API
Add eSIM to your product with one API.
See eSIM API →
White-label eSIM
A co-branded eSIM store for large platforms.
See White-label eSIM →- Data only, with no local number. The home line stays in the phone.
- Show the offer only where the roaming of the plan does not cover the trip.
- The phone must be unlocked and support eSIM.
- No network data: the trip comes from the customer.
Mobile operators
Add a travel eSIM to your app for the trips your plans do not cover. The customer keeps the home line in the phone and gets data at the destination.
See the solution →You set the retail price.
Buy at partner rates, keep the customer relationship, and agree the support split privately. One catalogue, three commercial shapes.
Wholesale pricing before your retail price.
You decide what the customer pays.
Support, refunds, and volume in the agreement.
From first step to first order.
Start with a short pilot. Review it, then add the next desk, route, or market.
Scope
Pick the plans and the countries outside their roaming.
Pilot
Show the travel plan on the roaming page for one plan family.
Extend
Add the add-on list, the reminder, and the care team.
Before you choose
Short answers to the common questions. The partner agreement sets the final terms.
Does it replace our roaming?
No. It covers the countries your plans leave out. Your roaming stays as it is.
Do you see where our customers are?
No. The trip comes from the customer in your app. RoamWorks gets the destination, the dates, and the order.
Can customers pay on the bill?
You choose the checkout. The API returns the plans and the order status, and the customer pays where you sell.
What does the customer need?
An unlocked phone that supports eSIM. The travel plan installs next to the home line.