Roaming goes wrong in the UAE in one specific way: the package is activated, but one setting on the phone is not, and the phone finds data through the wrong door. The result is the classic roaming bill. The fix is a five-minute pre-flight checklist.

The checklist, in order

  1. Activate the roaming package, not just roaming. Both operators sell country-specific and regional roaming bundles. Activating the switch without a package routes you to pay-per-MB rates that are genuinely punitive. Current bundle shapes are in the roaming guide.
  2. Set data roaming on, mobile data off until arrival. The phone should be allowed to roam but not hungry for data in transit - otherwise it burns pay-per-MB data the moment the plane lands in a transit airport.
  3. Turn on billing alerts at the maximum. Both operators support usage notifications on roaming; set them at the package's ceiling, not at some abstract percentage.
  4. Check what the package actually covers. Regional packages exclude some countries; "unlimited roaming" packages are usually unlimited-at-throttled-speed. The fine print is short - read it. Our roaming plans breakdown translates the published tiers.

The transit-airport trap

Landing in a transit country for two hours, with data roaming on and no package covering that country, is enough to run a bill. If your route transits anywhere, either buy a package that covers the transit stop or keep data off until the final destination.

The return trip

Deactivate roaming the day you return, or the package may renew on schedule while your phone quietly sits on a roaming network in some border area. The Etisalat roaming guide lists the deactivation path per operator.

One more thing: every guide we publish lives in one index - browse the whole library via the TelecomDesk UAE sitemap.