Roaming pre-arrival: sell the bundle before the customer is abroad

Scenario

Customer flies to Istanbul for the weekend. Did not think about a roaming bundle before the trip. Arrived — after the first WhatsApp message 5k UZS was debited. Only then remembered that roaming bundles exist, opened the app, bought a 24-hour bundle. The lost minute is costly, but the issue is bigger — the operator missed the chance to sell a weekly bundle, and the customer lost trust.

Pre-arrival — catch the customer before they end up on a foreign network and offer the bundle when they still have time to decide.

Triggers

A) Booking data through partnership. If the operator integrates with an airline / OTA — at booking time send the offer.

B) Behaviour in the app. The customer opened the “Roaming” section in the app or searched for a country.

C) Geofence in the airport. A customer with the operator’s MSISDN inside the departures terminal — a strong signal of an upcoming trip.

D) Calendar permission. If the customer granted the app calendar access — entries like “flight to Istanbul” — a clear trigger.

Any of these signals triggers the pre-arrival flow.

Action

Push in the app: “Flying to Türkiye? Roaming bundle 1GB for 7 days — 50k UZS. Activates automatically on landing. [Buy]”.

Content includes the specific country, specific price, specific options.

After purchase the bundle activates via geofence in the destination country, with no manual action.

What is measured

Pre-arrival conversion rate — what share of customers who received a pre-arrival offer bought a bundle before landing.

Revenue per pre-arrival vs reactive (post-shock) — bundle size comparison.

NPS of customers with pre-arrival vs without — usually significantly higher.

Penetration by signal source — what works best (booking, geofence, app behaviour).

What not to do

Do not offer a generic “roaming bundle” without country and price — low conversion.

Do not push if the customer declined — repeat offer in 6 hours adds perceived spam.

Do not activate a bundle without customer confirmation — even with a strong signal.

Do not use calendar data without explicit consent — privacy bomb.

How SamaraliSoft engages

Sprint Roaming Use Case — 4-6 weeks. Audit of existing roaming flow, partnership opportunities (airlines, OTA), trigger logic, communication design, pilot.

Related

• /en/use-cases/telecom-bill-shock-prevention/ — bill shock
• /en/insights/telecom-roaming-economics/ — roaming economics
• /en/solutions/telecom-tourist-services-platform/ — tourist platform
• /en/architecture/telecom-realtime-decisioning-architecture/ — decisioning