Support While You're Roaming

Connectivity problems have terrible timing. They happen on arrival, at night, in a country where you do not speak the language and have not yet found breakfast. Our support is built around that reality: written rather than telephone-first, documented rather than improvised, and readable on a device that currently has no data.

Written support is not a way of avoiding people. It is the only model that works when members are spread across every time zone. A queue that is awake in Chicago is useless at three in the morning in Chiang Mai; a written checklist you can follow immediately, plus a real reply while you sleep, is not.

What we can fix, and what we cannot

We can reissue a profile when a download fails or an activation code is consumed. We can check the provisioning state of a profile and tell you whether it has ever attached to a network. We can escalate to a partner when attachment is failing across a market rather than on one device. We can refund or replace where the fault is on our side.

We cannot unlock a carrier-locked handset — that is a request only your original operator can grant. We cannot add an embedded UICC to a phone that does not have one. We cannot make a partner network faster, and we cannot restore a profile you deleted, because the activation code was consumed at first download and the profile is gone with it. Saying so early is more useful than a hopeful ticket that stays open for a week.

The troubleshooting library

• Written to be read offline. Short, printable pages with no video and no assumptions about bandwidth.
• Device-specific settings paths for current iOS and the major Android manufacturers, because the menus genuinely differ.
• Symptom-led structure — no service, searching, bars but no data, or data that stops after a few minutes — rather than organised by our internal categories.
• Activation failure guidance, including what to do when a QR has already been scanned once.

How escalation works

First response is from a support engineer who can read provisioning logs, not from a script. If the problem is on a partner network, it is escalated with the identifiers that partner needs — the ICCID, the market, the attachment attempts and their timestamps — rather than a retelling of your description. You are told when that happens and what the partner's expected response window is.

Where an escalation stalls, we say so plainly. “Waiting on the partner, no update since Tuesday” is an unsatisfying message to receive but a far better one than silence, and it lets you decide whether to buy a local SIM as a stopgap while it is resolved.

What we log, and why it helps you

Every provisioning event is recorded: when a profile was issued, when it was downloaded, which EID it landed on, and every attachment attempt with its market and timestamp. That log is what turns a vague report into a diagnosis. It tells us whether a profile has ever attached to a network at all — which separates a device problem from a partner problem in seconds rather than days.

It contains no traffic. We cannot see the sites you visit or the contents of anything you send, because as a reseller of connectivity that information never reaches our systems. When you ask us what we hold about you, this is the honest answer, and it is set out in full in our Privacy Policy.

Hours and channels

Written support is staffed Monday to Friday, 08:00 to 20:00 Central Time, and activation failures are monitored outside those hours. There is a telephone line for members who prefer to speak to someone during office hours, though for technical faults writing is usually faster — screenshots of your settings screen tell us more in one message than ten minutes of description.

Everything arrives in the same queue, including complaints. Write to support@digitalroamink.com, or use the form on the contact page with the topic set so it is routed correctly the first time.