Common Belgium eSIM Activation Errors丨Invalid QR Code, No Service, Tech Support

In the common activation errors for Belgium eSIM, Invalid QR Code is mostly due to the QR code being already used, blurry screenshots, or exceeding the operator’s typical limit of 1-2 installation attempts. No Service is commonly seen when the APN is not automatically written, data roaming is not turned on, or the local network attachment has not been completed. When troubleshooting, first confirm that the phone is connected to the internet for scanning, IMEI/EID match, and the plan activation time is accurate to the minute, then restart and manually select the network; if there is still no signal after 5-10 minutes, you should contact technical support to check the configuration.

Invalid QR Code

When “Invalid QR Code” appears, follow these 3 steps to check: Step 1, see if the code is still usable, as many operators’ eSIM QR codes only correspond to a single installation; Step 2, check if the phone actually supports eSIM and if the system has been updated to a version that can normally add an eSIM; Step 3, look at the installation environment, including the network, screen brightness, screenshot cropping, and email forwarding compression.

Apple states that iPhones can add an eSIM via a QR code provided by the operator and also support manual information entry; Google also lists “Add SIM / Set up an eSIM” as a standard entry point.

Code Issues

When “Invalid QR Code” appears, do not rush to scan the code repeatedly. In many cases, the same eSIM QR code only corresponds to 1 installation action; if the order backend has already recorded it as installed or activated, scanning it a second time will typically result in an error 3 to 10 seconds after scanning, or the process will stop at the “Add Cellular Plan” page and not continue. Apple’s official documentation also mentions that the QR code provided by the operator can be used to add an eSIM, and some scenarios may require an additional confirmation code; if the previous installation record still exists or the verification information does not match, rescanning may fail.

Many people focus on the “code” first, but what truly needs to be checked is “what status this code is currently in.” If the order page, email, or operator App already shows status terms like Installed, Activated, Consumed, or Downloaded, you should stop and verify whether it has already been installed on another device, or if it was installed on this phone before and subsequently deleted. Apple also reminds users that after deleting an eSIM or restoring a device, the cellular connection may be lost and you need to contact the operator to restore it, rather than continuing to use the old QR code for repeated installations.

The following scenario is very common with travel eSIMs:
After purchasing the plan, the user tries to install it on an old phone; it fails, so they switch to a new phone to continue scanning; if that still doesn’t work, they screenshot the QR code and send it to a chat app, then reopen it from a computer or tablet. By this stage, the problem is usually no longer just about “whether it can be scanned,” but whether the QR code still retains its original data, white borders, and contrast, and whether the backend has already logged the first request as “used.”

The GSMA eSIM specification includes Activation Code, QR code scanning, and manual entry in the installation paths, indicating that the system verification is not about “whether it was scanned,” but whether the encoded content is complete and consistent with the backend records.

You can go through the following table first; it will be much faster than blind retries:

Check Item	Common Symptom	Suggested Action
Code Already Occupied	Error appears seconds after scanning; order status has changed	Check status on the order page; request resend if necessary
Image Compressed	Clear in album, but system prompts “Invalid”	Reopen from original email, webpage, or App
Borders Cropped	Scanner frame recognizes it, but installation fails	Keep full white borders around the code; do not zoom or crop
Code Content Outdated	Scanning old code after switching devices, deleting card, or restoring	Ask operator if the old code can be reused
Manual Field Error	Scan fails, and manual entry also fails	Check SM-DP+, Activation Code, and Confirmation Code

If you have a screenshot rather than the original file, check 3 details first:

First, are the white borders around the edges still there? Second, are the black and white modules blurry? Third, has it been secondary-compressed by a chat app? Many instant messaging tools re-encode long images or email screenshots, potentially compressing the size from over 1000 pixels to just a few hundred, and edges may be automatically cropped. Consequently, while the camera recognizes it as “a QR code,” the installation process cannot read the complete data, resulting in an “Invalid QR Code” error.

Another situation that is easily overlooked:

The QR code isn’t broken, but you used the wrong one. If more than 2 eSIMs are purchased under one account, or if multiple activation emails are received in the same inbox, it is easy for a user to confuse a Belgium plan with a plan for another country. During scanning, the system only verifies if the code can be accepted by the current installation process; it won’t judge for you whether “the one you actually wanted to install was a different one.” In this case, the order number, ICCID, plan country, and purchase time—these 4 fields—must be checked together; missing even one could lead you astray.

During manual entry, the error rate is usually higher than scanning. The GSMA documentation lists the Activation Code involved in manual installation separately, and Apple also specifies that some operators will require an additional confirmation code. In other words, at least 2 to 3 sets of information may be involved in verification:

• SM-DP+ Address
• Activation Code
• Confirmation Code (Provided by some operators)
  If even one character in these items is incorrect, the system may uniformly display the result as “Invalid QR Code” or “Could Not Add Plan.”

It’s not usually the long string itself that is typed incorrectly, but similar characters. It is recommended to check these positions one by one:

• Letter O and number 0
• Uppercase I and number 1
• Check if the hyphen - is missing
• Check if there is an extra space at the beginning or end
• Check if a line break was included during copying

If you are copying activation information from a PDF, webpage, or email, it is best to double-check the first and last 4 to 6 digits after pasting. Many failures are not due to the entire string being wrong, but because the beginning is missing 1 digit or the end has an extra space.

Some users ask why the second scan also fails if the first scan wasn’t successful. There are usually two types of reasons.

One is that although the first attempt didn’t show success, an installation request record was already left in the backend; the second is that the network was unstable during the first attempt, and the status synchronization between the device and the server didn’t finish, so the system temporarily hangs the code in a “Processing” state. Apple’s “If you can’t set up an eSIM” support page suggests users toggle Airplane Mode, check cellular settings, and restart the device before trying again, indicating that an installation failure doesn’t necessarily mean the code is completely invalid—it could be that the current record hasn’t refreshed yet.

In this case, it is not recommended to scan 5 times or 8 times consecutively. A more stable approach is to wait for 10 to 15 minutes, reopen the original email or order page, and then try again through the system’s eSIM entry point; if it still doesn’t work, switch to manual entry. Both Apple and Pixel official paths treat “Add eSIM from Settings” as the standard entry point, rather than simply scanning with a normal camera and finishing there. For iPhone, the path is Settings > Cellular > Add eSIM; for Pixel, it is Settings > Network & internet > SIMs > Add SIM > Set up an eSIM.

Consider another often-underestimated detail: the screen displaying the QR code.

If you are using another phone, tablet, or laptop to display the code for the current phone to scan, low screen brightness, a yellowish eye-protection mode, or a reflective film on the surface will all affect readability. In practice, keeping the display brightness between 70% and 100% is more stable; keep the scanning distance at 10 to 20 cm so the QR code fits completely within the viewfinder, rather than occupying just a small part of the center. If it’s too far, the camera sees the screen’s pixel grid first; if it’s too close, it easily loses focus. You don’t need to try a dozen more times; switching to a clearer display method is usually more effective.

If the QR code is from a printed paper, be careful as well. Paper wrinkles, uneven toner, or shrinking to an undersized dimension will deform the edges of the dense modules. Compared to a printed version, the original email page, official website order page, or the original QR code inside the operator’s App is more stable. On iOS 17.4 and above, Apple also supports adding an eSIM by long-pressing a QR code in the default Mail App or browser, which involves less imaging loss than “taking a photo of another device.”

The following sequence of judgment is practical and suitable for users to follow in the main text:

1. Check the status terms on the order page first to see if it already shows “Installed” or “Downloaded.”
2. Then confirm the source of the QR code: is it the original email, original webpage, or a screenshot/forwarded image?
3. Then verify if you have the wrong order, the wrong country plan, or the wrong code from your inbox.
4. Do not immediately and repeatedly retry after a scan failure; switch to checking manual fields first.
5. When checking manual fields, clearly distinguish O/0, I/1, spaces, and hyphens.
6. If both methods fail, contact the operator to see if the code can be reissued.

When messaging customer service, the more complete the information, the fewer rounds of back-and-forth. A useful set of content is:

• Order Number
• Purchase Email
• Device Model
• System Version
• Error Screenshot
• Current Country
• Number of steps you have already tried, e.g., “Scanned 2 times, manual entry 1 time”

This allows customer service to judge more quickly whether the problem is “code already used,” “field mismatch,” or “backend status not refreshed.” Simply sending “QR code invalid” usually requires another 2 to 4 rounds of questions, which drags out the time.

There is also a situation that occurs during the device transfer process. Both Apple and Google provide eSIM transfer paths where installation information is regenerated or recalled during the transfer. If a user scans an old QR code again mid-transfer, the system will easily error out. Apple’s support page regarding cross-device transfer also mentions that when scanning is not possible, manual methods can be used to complete the process; the Google Pixel help page writes “Transfer SIM from another device” and “Set up an eSIM” separately, indicating that “installing a new eSIM” and “migrating an eSIM from an old device” are fundamentally two different processes.

Therefore, when you see “Invalid QR Code,” focusing your attention on “whether this code is still valid, whether it’s the original file, and whether it corresponds to this specific installation” is more critical than constantly adjusting the network or resetting the phone.

Device, System, and Entry Point

Even if there is no problem with the QR code itself, errors can still appear. Common reasons are on the device side: the phone does not support eSIM, the system version is too old, operator restrictions haven’t been lifted, or the user is using the wrong installation entry point. Apple currently states clearly that the iPhone needs to be an iPhone XS, iPhone XS Max, iPhone XR, or later model, and must be paired with an operator that supports eSIM; Google’s instructions mention that for some Pixel and Android devices, eSIM functionality is only relatively complete on Android 11 and above, with lower versions being more prone to errors during the activation phase.

Look at the “Device Support” layer first. Many users assume that because their phone is a model from the last few years, it can naturally install an eSIM, but you actually need to check two more things: first, whether the model itself has the eSIM hardware, and second, whether this specific regional version is restricted by operators or market rules. The Apple support page mentions that iPhone support for eSIM starts from the XS / XR series; the Google Pixel help page breaks down the generations more finely—for instance, Pixel 4 and later models support eSIM, but some versions of Pixel 3a, certain regional and operator versions of Pixel 3, as well as earlier models, will have additional restrictions.

If you cannot find entry points like “Add eSIM,” “Set up an eSIM,” or “Add SIM” after opening Settings, do not continue scanning the QR code. The official Apple path is Settings > Cellular > Setup Cellular or Add eSIM; the official Pixel path is Settings > Network & internet > SIMs > Add SIM > Set up an eSIM. If the path is incorrect, a normal camera might scan the QR code, but the system may not necessarily hand the scanning result to the cellular configuration module. The user might see “QR code recognized,” but the next step will report “Invalid QR Code” or “Could Not Add Cellular Plan.”

The following table is worth checking first:

Next, consider the system version. The Google Fi official help page states that Android 11 and above are required for new user activation or eSIM activation; multiple Pixel instructions repeatedly note that “some steps only apply to Android 11 and above.” This instruction has a very practical meaning: even if the phone hardware supports eSIM, as long as the system remains on an old version, the settings menus, network permissions, and download configuration components may be incomplete, resulting in the scan proceeding halfway before the installation gets stuck.

There are also version differences for iPhone. Apple now supports multiple installation methods: importing during initial setup, importing from a QR code, importing via an operator link, importing via an operator App, or importing via manual entry. Since iOS 17.4 and above, users can even long-press a QR code in the default Mail App or browser and select Add eSIM; if the system is too old, this path does not exist. Apple also mentions that iOS 18 and above can call more diagnostic processes in certain failure scenarios.

Many cases of “device clearly supports it but still errors” are actually due to carrier locking. Google Fi’s official instructions say if you’re not sure if your phone is unlocked, contact your previous carrier or retailer to confirm. In a locked state, the device might show the eSIM menu and read some activation info, but it will fail at the stage of writing configuration or switching networks. The surface symptoms users see are often similar to QR code issues: successful scanning, a period of verification, then an error.

If the phone was bought second-hand, issued by a company, on an installment plan, or originally tied to a specific operator, checking the unlocked status is more necessary than checking the QR code. Moving down to the “Dual SIM and existing configurations” layer:

Apple states that an iPhone can manage 8 or more eSIMs; however, “can store many” does not equal “can enable many at the same time.” The Google Pixel help page also notes that on some Pixel models and operator combinations, you can use 2 eSIMs simultaneously, or 1 eSIM + 1 physical SIM, subject to operator restrictions. When a user has a main number, a travel card, and a secondary number all existing at once, and tries to import a new eSIM, the system might not be “unsupported” but rather “the current enabled combination is incompatible.” A common fix here is to temporarily turn off 1 old SIM before adding the new card.

Think of this step as “whether the device conditions are met.” Meeting the conditions usually requires at least these 4 items:

• Model supports eSIM
• System reaches the required version
• Device is in an unlocked state
• The current SIM combination hasn’t filled all available slots

If even 1 of these items is not met, the scanning result might be fine, but it could fail in subsequent installation steps. Especially in travel scenarios, many people put their original number, work number, and temporary data card on the same machine; the system menu shows 2 to 3 profiles, and as a result, the new card simply won’t go in.

Regarding “using the wrong entry point,” iPhone has two common paths:

1. Tap Use QR Code during the first-time setup;
2. After setup is complete, add via Settings > Cellular > Add eSIM.
   Pixel also has two:
3. Download SIM in the setup wizard;
4. Go to Network & internet > SIMs > Add SIM > Set up an eSIM.
   If a user opens a QR code in WhatsApp, email, or a webpage first and then uses a generic scanning method, the system might not always smoothly transition to the operator configuration page; whereas going through the official settings entry point, the device will default to calling the correct configuration module.

Sometimes users are actually trying to “transfer an eSIM from an old device” rather than “install a new eSIM.” These two processes cannot be mixed. Apple’s documentation separates eSIM Quick Transfer, Carrier Activation, QR Code installation, and transferring from Android or other devices into different methods; the Pixel help page also lists Set up a new eSIM and Transfer SIM from another device separately.

The following table is more suitable for users to check based on their actual phone interface:

Apple has another requirement that is easily overlooked: in many scenarios, a new iPhone requires a connection to Wi-Fi or a hotspot to complete activation; only eSIM-only models in certain regions can finish without Wi-Fi. In other words, if a user tries to install an eSIM outside at an airport, station, or hotel with a recently restored phone and unstable Wi-Fi, they will misjudge “network conditions not met” as “QR code invalid.” The QR code is responsible for passing the configuration entry point, but when actually downloading the operator configuration, the device still has to pull the data down.

Apple also provides a troubleshooting direction: if an eSIM cannot be set up, you can check for operator network issues, system updates, or whether the device needs to be restarted; on some versions, you can continue to check via additional diagnostics from Apple Support. What this reflects is that the system state itself also affects eSIM installation. If a user has already scanned more than 2 times and is getting errors in the same place, performing a system update plus a restart is more useful than scanning for a 3rd or 4th time.

Here is a more time-saving check sequence:

First confirm if the model is after iPhone XS / XR or a supported Pixel / Android model; then look at the system version, for Android at least see if it’s 11 or above; then confirm the phone is unlocked; then enter via the official eSIM entry in settings; if it’s a device switch, choose between “Transfer SIM” and “Set up eSIM” correctly; when there are already multiple cards, turn off 1 old card before adding the new one. Only after checking these steps is it worth focusing attention back on the QR code itself.

No Service

When a Belgium eSIM shows “No Service,” it’s usually not because the card has failed, but because the phone has not completed local network registration. The 4 most common areas users encounter are: default data card not switched to eSIM, Data Roaming not turned on, automatic network selection failing to connect to the partner operator, or APN not written correctly. In the first 1–5 minutes after landing, at underground platforms, inside train carriages, or inside airports, the probability of “No Service” is higher. Don’t jump around randomly when troubleshooting; follow these 5 steps: Line Settings → Roaming → Network Selection → APN → Network Mode. You can usually determine the cause within 10 minutes.

Which Category Does It Belong To?

When “No Service” appears on a Belgium eSIM, do not treat it as a single problem. The same prompt the user sees on the phone usually falls into 4 types of states: completely not registered on the local network, only having emergency call capability, connected to the wireless network but no data session established, or network icons looking normal but access failing. While the surface appearance is similar, the processing order differs significantly. Classifying the phenomenon first will reduce repeated steps and usually compress the judgment time to 3–8 minutes.

Look at the text and icons at the very top of the status bar first; don’t just stare at the two words “No Service.” Different phone systems display this differently, but it generally falls into a few combinations: no signal bars at all, showing SOS, showing 1–4 signal bars but no LTE/4G/5G, or showing LTE/5G but webpages won’t open. Just based on these 4 manifestations, the problem location is already different.

If the user doesn’t distinguish between these at the start, they will end up toggling between APN, network selection, and restarts, often wasting 10 minutes without locating the issue.

What You See	Which Layer is it Closer To?	Common Locations	What to Check First
No signal bars, says No Service	Not registered on local network	Line not enabled, network selection failed, device restriction	eSIM toggle, manual network selection
Shows SOS / Emergency Calls Only	Only emergency calls maintained	Roaming not finished, partner network rejects registration	Roaming, Network Selection
Signal bars present, no 4G/5G	Basic attachment incomplete	Default data card not switched, network mode issue	Data line, 4G/LTE mode
Has LTE/4G/5G, webpage won’t open	Data session not established	APN, DNS, IP allocation	APN, Airplane mode reconnect

The first category is the easiest to judge: no usable signal bars at the top of the screen, the operator name doesn’t show, or it stays on “No Service.” This usually means the phone hasn’t entered the local Belgium partner network. Don’t touch the APN here yet, because the prerequisite for the APN to work is that the device has completed basic registration.

If the user changes the APN now, there will often be no change. What’s more worth checking first is whether this eSIM is actually enabled, whether the phone is stuck in a failed automatic network selection state, or if the device is in an underground platform, train car, or thick-walled building. In the first 1–3 minutes after landing, at Brussels Airport, subway platforms, or train cars, short-term “No Service” is not uncommon.

• Is eSIM enabled?
• Was Airplane mode just turned off?
• Did you just cross a border and switch networks?
• Are you underground or deep indoors?
• Is automatic network selection stuck?
• Have you waited for 60–120 seconds?

If the screen shows SOS or Emergency Calls Only, the situation is different. The phone isn’t completely disconnected from the network; instead, it has only retained the lowest layer of emergency call capability. Many users treat SOS as “completely broken,” but it actually shows that the radio side has at least captured an available cell, even if regular service registration didn’t pass. Common reasons include: Data Roaming not turned on, the currently selected operator is not a partner for this eSIM, network authentication is still in progress, or the device’s frequency band support is average. If you can already see 1–2 signal bars at this stage, the direction has shifted from “is there a signal” to “can it complete formal registration.”

SOS and “No Signal” are not the same state.
The former means the phone has sensed a nearby network; the latter is closer to not even starting basic attachment.

Next is the third category: there are signal bars, but the status bar doesn’t have LTE, 4G, or 5G—it only shows the operator name or basic signal. This category is easily misjudged. Many users will say, “I already have a signal, why isn’t it working?” but from a system perspective, it might not have actually established the data service yet.

The most common cause is that the default data line hasn’t been switched to the Belgium eSIM, or the primary SIM is still occupying the mobile data priority. On Dual SIM phones, the occurrence rate of this problem is high. On the surface, both cards are present; in reality, the system is still directing traffic to the original SIM. The original SIM has no data permissions in Europe, resulting in it “looking connected but actually unable to browse.”

Symptom	Explanation	Higher Probability Location
2–4 signal bars, no 4G/5G	Network attachment incomplete or data line not switched	Default Data Card, Roaming
Signal bars appear and vanish	System trying to switch between two cards	Auto Data Switching
Voice normal, data not working	Basic service and data service are separate	APN, Data card selection

At this point, the user can make a quick judgment: open the phone settings and see if the Belgium eSIM is set as Cellular Data / Mobile Data. If not, the problem usually isn’t the plan itself but the system allocation. After changing it, don’t immediately change the next item; give the device 30–90 seconds to perform a new network attachment. Many users see that the webpage hasn’t opened by the 10th second and switch back, thereby interrupting a session that was halfway established.

The fourth category is the most confusing: the status bar already displays LTE, 4G, or 5G, and there are even 3–4 signal bars, but Google Maps, Safari, WhatsApp, and Speedtest all fail to open. This is no longer a question of “whether it’s connected to the network,” but “whether the data is usable.” The radio access layer may have passed, but subsequent steps like IP, APN, DNS, and policy routing have not finished. On the surface, the phone looks connected; from the user experience, it’s about the same as having no network.

Having a 5G icon doesn’t mean you definitely have usable data.
The icon only indicates the phone is on a certain type of radio access layer; whether a webpage can open depends on the data path behind it.

This category usually shows a few detailed differences that are useful for distinguishing:

• All Apps fail to open: Looks more like an APN or data session issue.
• Individual Apps work, webpages don’t: Looks more like DNS or IPv6/IPv4 compatibility.
• Recovers for 20–40 seconds after Airplane mode then cuts out: Looks more like unstable session reconstruction.
• Speed is extremely slow, images take over ten seconds: Could also be plan throttling rather than a complete outage.

Usage Symptom	Closer Problem Location
All services fail	APN / IP data session
Individual services work	DNS / Routing
Intermittent connection	Network mode / Network switching / Session timeout
Slow to the point of not opening	Throttling, congestion, weak coverage

In addition to checking the status bar, you can use the 4 function sets—”SMS, Calling, Webpage, Maps”—for cross-judgment. Because they rely on different network layers, they can help narrow the phenomenon further. For example, being able to receive a text usually means basic registration has a result; being able to make an emergency call but not browse means there is radio access; both maps and browsers failing points to an underlying data session issue. If only one specific app has a problem, don’t start by suspecting the eSIM itself. Using these 4 sets of tests, users can often narrow the direction to 1–2 categories in about 2 minutes.

• Can receive SMS, webpages won’t open: Check APN first.
• Can make calls, maps won’t open: Check data line first.
• Only browser fails, chat software works: Check DNS.
• All functions fail: Check registration and network selection first.

The environmental location also affects which state you see. While coverage within Belgian cities usually isn’t a major issue, on the way from the airport to the city, entering train stations, on subway platforms, in mall basements, or in hotel elevators, the device is more likely to jump between states. A user might see SOS, then 1 signal bar, then LTE within 30 seconds, followed by the webpage still not opening. This change doesn’t mean the phone is “getting more confused”—it shows it’s progressing step-by-step from radio access toward a data session.

Scenario	More Common State
Just landed inside the airport	No Service / SOS
Subway platform	SOS / Low signal
High-speed or cross-border train	Signal present but data is intermittent
Thick-walled hotel room	4G/5G icons change frequently
Outdoor street (stationary)	Best for judging the real problem

Many users also confuse “expired plan” with “No Service.” In reality, a plan having no data, being throttled, or not yet being activated can all manifest as being unable to browse, but they are not at the same level as a complete lack of signal. When there’s no data, the status bar often still shows LTE/4G; when not registered on the network, even the signal bars might be absent. If the user classifies the phenomenon first, and then thinks about settings, network, plan, or device, the path becomes much clearer. Breaking a general phenomenon into several categories is the foundation for all subsequent steps.

A simple chart suitable for saving and reference is as follows:

Phenomenon Category	What to Do First	What Not to Do First
Completely no signal	Check eSIM toggle, manual selection	Don’t change APN first
SOS	Check roaming, partner operator	Don’t delete the card first
Signal present, no 4G/5G	Check default data line	Don’t contact support first
Has 4G/5G but no web	Check APN, Airplane mode, DNS	Don’t repeatedly select network first

Once you can distinguish which category you belong to, “No Service” is no longer a vague prompt but a starting point that can be further broken down. Whether you check settings, roaming, APN, or contact technical support next, your information will be more accurate.

Settings Mismatch

The Belgium eSIM is already installed in your phone, and the line name is visible on the status page, but it still shows “No Service” or has signal but no internet. Often, the issue isn’t the plan itself, but that the system has placed the line, data, roaming, or network selection in the wrong “slots.” This is more common in dual-SIM phones: the eSIM is responsible for internet while the original SIM is kept for calls, but the system still assigns mobile data to the original card; or the eSIM is enabled, but Data Roaming is off, so the phone finds the network but cannot complete data registration.

First, check if the line is actually “in use,” not just “installed.” A successful installation only means the configuration profile is written to the device; it doesn’t mean the card has taken over mobile data. Many users see the Belgium eSIM in iPhone’s “Cellular” or Android’s “SIM Manager” and assume it can access the internet, but there are at least 4 locations within the system that affect the result: line activation status, default mobile data, voice line assignment, and data switching permissions. If even 1 item is wrong, you may experience “card present, no data” or “SOS.”

The most error-prone areas are usually concentrated in these locations:

• eSIM is installed, but the toggle is still off
• Default mobile data has not been switched to the Belgium eSIM
• The primary card still retains mobile data priority
• Data automatic switching is turned on
• Both voice and data are bound to the original SIM
• After turning off Airplane Mode, you didn’t wait 60–120 seconds for re-attachment

Many people try changing the APN, restarting, or deleting the card first, but those should come later. It is better to first verify the system assignment relationships.

Setting Item	Status You Should See	Behavior After Common Error
eSIM Switch	Enabled	Completely no signal
Cellular Data / Mobile Data	Belgium eSIM	Card present but no internet
Voice Line	Primary card or any	Generally does not affect internet
Data Switching	Off is more stable	Network connects and disconnects intermittently
Primary Card Mobile Data	Turn off first for clearer testing	System diverts the data traffic

In dual-SIM scenarios, the system tends to “act on its own.” For example, if the primary card has always been responsible for data, after the user installs a new eSIM, the system might visually show both cards are available while the background still prioritizes the original line. If the original line has no data package in Europe or roaming is off, the status bar will look normal, but no webpages will open. This issue occurs more frequently right after landing, exiting Airplane Mode, or restarting the device, because the system re-evaluates which card carries data, resulting in a 30–90 second switching delay.

The following checklist is best done in order, without skipping steps:

• Turn on Cellular Network / Mobile Network
• Confirm Belgium eSIM is enabled
• Switch default mobile data to Belgium eSIM
• Temporarily turn off primary card mobile data
• Temporarily turn off automatic data switching
• Keep primary card calls active (does not affect testing)
• Wait 1–2 minutes and then check the status bar

If you reach this point and still have no service, check roaming. Most travel and regional eSIMs in Europe rely on roaming to access local partner networks. Users often turn off “Data Roaming” out of fear of extra charges; this is a very common mistake. The problem is that once this switch is off, the phone might still show the line name or briefly show 1 to 2 bars of signal, but data registration cannot be completed. The result isn’t an immediate error, but it looks like it’s “almost connected” while ultimately opening nothing.

Think of it this way: the phone has seen the door but hasn’t been allowed through. So when checking, don’t look at “whether roaming will charge,” but first look at the plan type.

• Travel eSIM: Mostly requires Data Roaming to be on
• Regional eSIM: Relies more on roaming when switching countries
• Local operator physical card: Sometimes works without it
• Belgium eSIM: Recommended to turn on in most cases

Switch Status	Possible Phenomena Seen
Roaming Off	Signal present but no data, or long-term SOS
Roaming On	Enters registration process; may recover within 1–3 minutes
Roaming toggled repeatedly	System reconnects constantly; judgment becomes slower

Some users will toggle the switch three or four times in a row, hoping for immediate recovery. Doing this actually causes the device to repeatedly initiate attachment requests, causing the network list and authentication status to refresh constantly, making the wait even longer. The better way: after turning on roaming, don’t touch other settings and give the device 60–120 seconds to complete a full registration.

If the line and roaming are matched, see if “automatic switching” is interfering. Another often overlooked setting is the “Network Selection” method.

Phones default to automatic network selection, but automatic doesn’t mean it gets it right every time. Especially at Brussels Airport, Antwerp Central, metro platforms, or cross-border trains, the device might get stuck on a visible network that doesn’t allow registration. A user sees “Automatic” is on and thinks everything is fine, but in automatic mode, it can get stuck on the wrong network for 2–5 minutes. Instead of deleting the card, turn off automatic and manually try 2 to 3 visible operators, waiting at least 60 seconds for each.

When manually selecting a network, these are common incorrect actions:

• Tapping multiple operators in rapid succession as soon as the list appears
• Waiting only 5–10 seconds for each network
• Immediately trying to change the APN after a selection fails
• Switching back to automatic and immediately reconnecting via Airplane Mode

Operation Method	Result
Wait over 60 seconds for each network	Easier to judge if registration is possible
Tap 3 or more networks continuously	Phone keeps re-scanning, making it slower
Switching repeatedly between auto and manual	Status becomes chaotic and hard to judge
Giving up after testing only 1 network	Easy to miss the partner carrier

There is another issue in device settings that isn’t the most frequent but, when encountered, leads users to misjudge it as a “broken card”: the system retains old line preferences after an update. This is especially true for devices that have had other European eSIMs installed, configurations deleted, or primary cards swapped, where network priorities and cache may not have been cleared. On the surface, the Belgium eSIM is enabled, but in reality, old mobile data configurations are still influencing the selection. Typical symptoms include: no service upon first power-on, brief recovery for 20–40 seconds after Airplane Mode, and then disconnecting again; or working for a while after a restart but failing after entering or leaving a building.

This type of situation is better handled as follows:

• First confirm all the above settings are correctly matched
• Turn off Wi-Fi to avoid misjudgment
• Toggle Airplane Mode once
• Restart the phone if it is still abnormal
• If all else fails, consider resetting network settings
• Remember saved Wi-Fi passwords before resetting

Resetting network settings clears Wi-Fi, Bluetooth, VPN, and cellular preferences. It shouldn’t be the first step, but after the first 4 to 5 items have been verified, it is more stable than repeatedly deleting the eSIM. Reinstalling an eSIM after deletion usually requires re-scanning the QR code and re-downloading the configuration; if the plan allows only a limited number of installations, the cost is higher.

One more easily ignored point: “line displaying normally” does not equal “correct system path.” When a user sees the operator name, the eSIM name, and the 4G/5G icon, it’s easy to feel settings are complete. In reality, whether mobile data truly exits through the Belgium eSIM depends on whether the default data line is set to it, whether roaming is on, whether automatic switching has diverted the traffic, and whether network selection has landed on a registrable network.

A summary checklist suitable for saving and following is as follows:

• eSIM: Enabled
• Default Data: Belgium eSIM
• Primary Card Data: Off for testing
• Data Switching: Off
• Data Roaming: Enabled
• Manual Network Selection: Test 2–3 times if necessary
• After each change: Wait 60–120 seconds

Following this order of inspection is generally easier for narrowing down the problem to a specific setting than immediately contacting customer service, deleting the card, or restarting repeatedly.

Network Present but No Data

The status bar already shows 4G, LTE, or 5G, but webpages are still spinning. This situation is usually not “no signal” but rather the phone failing to actually establish a data session. The 5 most common areas for users are: APN not automatically written, default data line not assigned to the Belgium eSIM, Data Roaming switch not on, network mode and local frequency bands not working well together, or the system successfully attaching but the DNS or IP session failing to get a usable address. On the surface, they all look like “network icon but no network speed,” but the actual layers and processing orders are different.

First, distinguish a phenomenon: there are 2–4 bars of signal, 4G/5G is visible, but Google Maps, Safari, WhatsApp, and Speedtest won’t open. This usually means wireless access was successful, but the data exit is blocked.
If you can receive SMS but cannot load webpages, it usually means basic registration is complete, and the problem is closer to the APN, data line, or IP assignment.

Look at the APN first. Many travel eSIMs automatically issue an APN, but not every device receives it stably. For iPhones and Androids, differences in system versions, operator configuration files, and dual-SIM combinations can result in “connected icon normal, but no data.” The most common mistake is entering the APN for the primary card instead of the Belgium eSIM. Another situation is the APN being left blank; the local network allows registration but provides no data exit.

A single space, dot, or letter wrong in an APN string can cause the system to show 4G while failing to establish usable data.
In screenshots submitted by users to customer support, the most valuable thing to look at first is often the APN page, not the signal bars.

Next, look at the default data line. In dual-SIM phones, this step is easily botched. eSIM installation being complete doesn’t mean the system has set it for cellular data. A common scenario: the primary card keeps calls, the eSIM handles internet, but the system still sends data traffic to the original SIM. If the original SIM lacks data permissions in Europe or roaming isn’t on, the status bar looks normal but no pages open.

This issue is more common on dual-SIM Androids and not infrequent on iPhones, especially when “Allow Cellular Data Switching” is on, as the system tries to switch between cards, causing issues in weak signal areas.

• Belgium eSIM is enabled

• Default mobile data must select Belgium eSIM

• Primary card can retain voice

• Primary card mobile data is recommended to be turned off for testing

• Automatic data switching is recommended to be turned off first

• Wait 60–120 seconds after switching before judging results

Many users change settings and, seeing no internet within 10 seconds, continue changing things randomly.
In reality, network re-attachment and data session reconstruction usually take 30–90 seconds, and close to 120 seconds during some cell site handovers.

Then look at Data Roaming. Most cross-border or regional eSIMs rely on roaming to access local partner carriers. If you don’t turn this switch on, the network might allow you to “hang on,” but won’t necessarily give you a normal data path. Users often hesitate at the word “roaming”—this is a common psychological reaction. For a purchased Belgium eSIM, this switch is usually not optional but required. When it’s off, the typical symptom is not a complete lack of signal, but having a network icon with no data, or only tiny amounts of background handshake data while foreground apps fail completely.

“Having a 5G icon” does not mean this eSIM has acquired a usable data channel.
The icon displays the current access layer status; whether a webpage can open depends on subsequent steps like IP, DNS, APN, and policy routing.

If the APN and data line are both fine, next check the network mode. 4G coverage is sufficient in most Belgian cities; 5G availability is affected by the plan, model, frequency bands, and partner networks. Some users set their phones to “5G Auto” or certain Android models default to NR priority. If they enter a mall, metro, or thick-walled hotel, the 5G attachment might be unstable and the 4G fallback slow, manifesting as signal but no data, or webpage loading times exceeding 15–30 seconds. Switching the network mode to LTE/4G for testing often recovers it within 30–90 seconds.

• Airport indoors: 5G might be unstable

• Metro platforms: 4G fallback is more common

• Hotel upper floors or thick-walled rooms: Icon jumps between 5G and LTE

• High-speed/cross-border trains: High cell handover frequency makes data interruptions more obvious

If it stabilizes after switching to LTE, the problem is closer to wireless negotiation than plan expiration.
Users don’t need to suspect the eSIM is broken right away; putting 5G aside temporarily will lead to faster judgment.

Going down another layer, check if the phone actually got a usable IP. Some networks allow a device to register and assign wireless resources, but the IP configuration is incomplete or the DNS doesn’t return a normal resolution. This feels like “the whole internet is down”: browsers won’t open, apps report network errors, but a few services occasionally work. A simple way for users to distinguish: see if App Store, Google Play, Maps, and messaging apps all fail simultaneously; if “all fail,” it’s likely the underlying data session wasn’t completed; if “some work, some don’t,” suspect DNS or IPv6/IPv4 compatibility.

Some European networks behave differently in IPv6 and IPv4 dual-stack negotiation.
With certain old systems, models, and operator config combinations, address allocation might succeed but external access remains abnormal, especially with systems 1–2 major versions out of date.

Another often-overlooked situation: the plan is exhausted or throttled to the point of being unusable. Travel eSIMs marked “unlimited data” often actually have fair use limits. After reaching a threshold, speed might drop to 128 kbps, 256 kbps, or 512 kbps. Map loading, image downloads, and video playback will feel like “no internet,” while in reality, the speed is simply too low for a usable experience. If you downloaded many videos, shared a hotspot, or performed cloud syncs the day before, this layer is worth investigating.

• Map base-layer failing to load isn’t necessarily a total disconnection

• Waiting ten-plus seconds for a 2–3 MB image could mean throttling

• Video platforms stuck at 240p or failing to buffer is common below 256 kbps

• Hotspotting to a laptop will magnify data consumption significantly

When a user simply says “no data” in a support chat, it’s hard for support to distinguish between disconnection and throttling.
Providing a Speedtest screenshot or explaining the difference between “webpage won’t open at all” and “takes over 20 seconds to open” makes troubleshooting much faster.

Also, watch out for system cache and the network stack. After changing eSIMs, countries, or operators, network parameters saved in the phone don’t necessarily refresh immediately. Some devices retain old DNS, sessions, or network preferences after repeated card swapping, making a new eSIM look connected but unable to stably exit the network. Simply restarting once isn’t always enough; toggling Airplane Mode for 10 seconds, turning off Wi-Fi, waiting 1–2 minutes, and resetting network settings if necessary has a higher success rate. Resetting network settings clears saved Wi-Fi, Bluetooth pairings, VPNs, etc., so confirm you remember your passwords before doing so.

Not every “recovery after restart” means the problem is solved.
If it drops again every 10–20 minutes, it means the underlying configuration is still mismatched; temporary recovery does not equal stability.

Following the order saves a lot of time. Check APN, then default data line, roaming, network mode, IP/DNS, and finally data plan and device compatibility. Stepping through like this usually narrows the cause down to 1–2 areas within 5–10 minutes, rather than toggling settings back and forth a dozen times.

Tech Support

When the Belgium eSIM exhibits Invalid QR Code, Activating for over 15 minutes, or No Service for over 30 minutes, and you have already finished basic steps like restarting, toggling Airplane Mode, checking data roaming, and manual network selection, the issue usually no longer lies with local settings but with order status, eSIM config profile, carrier access, or device identification info.

What to do then isn’t to keep deleting and reinstalling, but to send the order number, error screenshots, phone model, system version, city, and steps already tried to Tech Support all at once. This allows support to judge within 1 round of communication whether to re-issue the QR code, reset the configuration, or escalate to the technical team.

When to Contact Tech Support

Many users interpret an eSIM error as “maybe it will work if I try one more time,” leading to 2 consecutive scans, 3 reboots, and 4 to 5 airplane mode toggles. Ultimately, a problem that only required a single customer service check turns into a much longer wait. A more appropriate way to judge is not by how long you have tried, but by the error type, duration, completed steps, and current environment. As long as you have finished basic setting checks and remain in the same state, the problem is usually beyond the scope of local adjustments.

Look at the time first. If you see Invalid QR Code after scanning, there is no need to wait 10 or 30 minutes, because this is an instant error; the system has already made a judgment within 1 to 3 seconds. When this type of message appears, scanning more than 2 additional times yields little results. If the installation is successful but consistently shows Activating, you can give the device and the carrier some synchronization time; a common observation window is 10 to 15 minutes. If it hasn’t become available beyond this interval, it is not suitable to continue toggling settings repeatedly. If No Service is displayed after arriving in Belgium, waiting 20 to 30 minutes in normal coverage environments like outdoors or airport halls is usually sufficient to determine if there is an anomaly.

The table below is more suitable for a user’s first round of judgment:

Current Status	Suggested Self-Check Time	More Appropriate Action After Timeout
Invalid QR Code	Instant judgment	Contact Tech Support
Activating persists	10–15 minutes	Contact Tech Support
No Service	20–30 minutes	Contact Tech Support
Signal exists but no internet	10 minutes	Check APN first, then contact
Unable to reinstall after deletion	Instant judgment	Contact Tech Support
Manual network selection all failed	5–10 minutes	Contact Tech Support

Beyond time, you also need to look at what checks you have performed. For most iPhone, Pixel, and Samsung models, basic troubleshooting usually involves no more than 6 items: confirming the device supports eSIM, confirming plan coverage for Belgium, enabling Data Roaming, setting the eSIM as the default data line, restarting the device once, and toggling airplane mode (off after 30 seconds). If these 6 items are completed and there is still no change, continuing with a 2nd or 3rd round of the same operations usually won’t yield new results.

The same error can be judged differently depending on the environment. For example, if you just landed at Brussels Airport, having no signal within 5 minutes of landing isn’t necessarily abnormal. However, if you have already cleared customs, connected to the airport Wi-Fi, and stayed in the ground area for 25 minutes while the eSIM still hasn’t registered to any network, then you shouldn’t continue to wait.

Conversely, if you are testing in an underground parking lot, train tunnel, mountain road, or a hotel room with thick walls, a network registration failure doesn’t necessarily mean there is a problem with the plan itself. A more reliable approach is to test once above ground, outdoors, or in a non-underground space before deciding whether to contact customer service.

Some situations look like setting issues but are actually closer to the scope of customer service handling. For example, if the system prompts “This plan cannot be added” after scanning, or if you can clearly see the eSIM name on the Cellular page but the status stays on Turning On, Activating, No SIM, or Not Provisioned. The difference here is important: the former mostly happens during the installation stage, while the latter has already entered the configuration or registration stage.

Errors in the installation stage often involve expired QR codes, repeated scanning, device restrictions, or reached installation limits. Errors in the registration stage often involve backend authorization, partner network access, data synchronization, or APN delivery anomalies. Neither category of problem can be reliably solved by simply restarting twice more.

You can compress the judgment into a more actionable set of standards:

Completed Check	Count or Status
Restart Device	1 time
Airplane Mode Toggle	1 time, keep for 30 seconds
Data Roaming	Enabled
Default Data Line	Switched to Travel eSIM
Automatic Network Selection	Attempted
Manual Network Selection	Attempted 1–2 local networks
Coverage Environment	Outdoors or airport ground area
Waiting Time	10, 20, 30 minutes for different errors

As long as most items in this table are satisfied and your error remains unchanged, you should turn to Tech Support. The reason is simple: trying 3 more times will still provide the same status to customer service; but if you start preparing the order number, device model, OS version, screenshots, and city at this point, it will be easier for customer service to judge whether to reissue a QR code, check configuration, or have you perform one specific test in the first round.

In fact, signal bars only indicate that the device may be receiving a wireless network; it doesn’t mean the plan has completed data access. You might see 1 to 2 bars of signal, but web pages won’t open, maps won’t load, and speed test tools won’t start. When this state occurs, the only local step left is usually an APN check; if the APN page is normal, roaming is on, and the default data line is correct, and there is still no data after 10 minutes, there is no need to restart the phone for a 4th time.

Another common situation is finding out it cannot be reinstalled after deletion. Many travel eSIM configurations only support 1 installation or a limited number of reinstalls. If a user deletes the eSIM without customer service confirmation and then scans again, the system may prompt within 2 to 5 seconds that the QR code has expired, been used, or cannot be added again. At this step, the handling method has usually changed from “continue setting up” to “let customer service check installation counts, reset configuration, or reissue a new code.” In other words, as long as you have deleted it once and cannot reinstall, further local attempts are not recommended.

If any one of the following phenomena occurs, it is usually sufficient to enter Tech Support:

• Arrived in Belgium, waiting locally for over 20 minutes with No Service
• eSIM shows Activating for over 15 minutes
• Invalid QR Code appears on the first scan
• Manual selection of 2 or more local networks fails
• Reinstallation after deletion fails
• Same order still cannot be installed on another compatible device
• Device settings are all normal, but data connection tests fail 3 consecutive times

Moving a step further, many users worry about whether “customer service is slow because my description isn’t professional.” In reality, the standard for entering Tech Support isn’t how many technical terms you know, but whether you can describe the status clearly. For example, “I am in Antwerp, iPhone 14, iOS 18, eSIM installed, data roaming enabled, manually tested Proximus and Orange Belgium, still No Service after 25 minutes”—this type of information is much more likely to get an effective reply than “it’s still not working.” Because of this, identifying the need to contact support early reduces useless waiting.

Also, consider device differences. iPhone’s eSIM page is usually easier to confirm successful installation, while some Android models might behave more complexly under dual SIM activation, carrier locks, or regional version restrictions. You might see the eSIM written, but the status bar never shows a network; or you might see the network appear, but data connection cannot be assigned. For users, there is no need to understand the logic of every model; just remember one thing: If the basic checks are complete and the status hasn’t changed beyond a reasonable time, hand the problem to the support team instead of continuing to toggle through menus.

To reduce misjudgment, use the following “Try Yourself” vs. “Contact Support” boundary:

Situation	Better to Try Yourself	Better to Contact Support
No response a few seconds after scanning	Yes	No
No network 3–5 minutes after landing	Yes	No
Activating unchanged for 15 minutes	No	Yes
No Service unchanged for 30 minutes	No	Yes
QR code invalid immediately upon scanning	No	Yes
Unable to reinstall after deletion	No	Yes
Have tried 6 basic checks	No	Yes

Sometimes, there is nothing wrong with the plan itself; the problem is simply that the initial access process hasn’t been completed. For example, some products start timing after the first connection to a Belgian partner network, some require you to arrive locally before enabling the data line, and some may have successful installation but registration delay when the system update is older. Even so, users do not need to wait indefinitely. Most normal access scenarios will show visible changes within 10 to 30 minutes: from Activating to available, from No Service to a network name, and from no internet to pages loading.

If you don’t see a change, it means it’s time to change the handling path.

Compress the judgment into one actionable sentence: When the error is instant, like Invalid QR Code or unable to reinstall; or when the error is persistent, like Activating for over 15 minutes or No Service for 20 to 30 minutes, and you have completed basic setting checks, you should enter Tech Support.

What Information to Send

Many eSIM support tickets go back and forth for 3 to 6 rounds not because the problem is particularly complex, but because the first message lacks enough information. Customer service usually looks at 4 types of content: Can the order be found, can the device be identified, did the error occur at the installation or networking stage, and what steps have you already tried. If you only send “My Belgium eSIM doesn’t work,” the other party can often only reply with a template and then ask one by one for your email, order number, phone model, location, and screenshots. For every missing piece of information, there is usually one more round of confirmation; in cross-timezone support scenarios, one round of back-and-forth could take 15 minutes, 30 minutes, or even longer.

Sending order information first is to allow customer service to find your plan and configuration records in the backend. The 3 most useful items are usually: Order ID, Purchase Email, and Plan Name. It is best to copy the Order ID completely without omitting characters; use the email used when placing the order, not another email you usually use; also write the plan name in full, such as 1GB/7 Days or 5GB/30 Days, because the same platform often has multiple Belgium products with different partner networks, activation methods, and validity periods.

The following table is suitable for inclusion in your first message:

Information Item	Suggested Content	Why Send This
Order ID	Full order number	Check order and config status
Purchase Email	Ordering email	Match purchase records
Plan Name	Full plan name	Distinguish 1GB, 3GB, Unlimited, etc.
Purchase Time	Order date and time	Compare activation and delivery logs
Country/Region	Belgium	Confirm coverage product match

After order information, add device information. Customer service needs to know more than just “iPhone” or “Android”—they need the brand, model, and OS version. For example, iPhone 14 vs. iPhone SE, Galaxy S24 vs. Galaxy A series, or Pixel 8 vs. Pixel 6 may differ in eSIM menus, dual SIM logic, and network registration performance. The OS version is also important, as some issues only appear on older systems or involve menu position changes after updates. If you write “Samsung phone,” customer service has to ask again; but if you write “Samsung Galaxy S24, Android 15,” they can usually judge more quickly if it’s a general issue or model-specific.

Device information is better sent in this format:

Device: iPhone 14
OS: iOS 18.x
eSIM installed: Yes
Primary SIM: Physical SIM active
Default data line: Belgium eSIM

This writing style has two benefits. First, customer service can see at a glance if you are in a dual SIM state. Second, they can judge if there is a common situation like “successful installation but default data line not switched.” Many users have actually installed the eSIM successfully, but mobile data is still pointing to the original physical card, resulting in the page showing settings while there is actually no traffic.

Next is the error itself. What affects reply speed most here isn’t how much you write, but whether what you write can be categorized. For customer service, common statuses are roughly divided into 4 groups: QR code issues, installation issues, activation issues, and networking issues. When you send “cannot use,” all 4 groups could apply; if you send “Invalid QR Code,” “Stuck on Activating for 20 minutes,” “No Service after arrival in Brussels,” or “Signal bars show, but no data connection,” customer service can quickly triage the problem.

Refer to these correspondences:

How You Describe It	What Support Can Judge Better
Invalid QR Code	Expired QR, reuse, installation limits
Unable to Add eSIM	Installation stage failure, device restrictions
Activating for 15–20 minutes	Backend config, data sync, registration delay
No Service in Brussels	Coverage, activation status, selection issues
Signal bars but no internet	APN, data access, data line settings

Many users only send error text without time. Actually, time is very useful. For example, you can write: Arrived in Belgium at 14:10 local time, enabled eSIM at 14:20, still No Service at 14:45. This way, customer service can judge that you have waited 35 minutes, rather than just 2 minutes after turning it on. For backend troubleshooting, timestamps can also correspond to their configuration delivery logs or network registration records.

Besides text, screenshots are often more effective than extra explanation. It is recommended to prepare at least 3 to 5 images—not too many, but each with a purpose. The most practical ones are usually:

• Screenshot of the error pop-up
• Cellular / Mobile Data settings page
• eSIM list page
• Network Selection page
• APN page
• The QR code or activation code page from the order email

Sending only the first error pop-up is not enough, as customer service can only see “what the error is” but not “what status the device is in.” Settings page screenshots tell them: if the eSIM is actually installed, if it’s on, if it’s set as the default data line, if data roaming is on, and if automatic network selection is enabled. These are parts where reply speed is heavily affected. Sending all 4 images at once usually saves more time than back-and-forth updates.

Here is the priority for screenshots, suitable for preparation in this order:

Priority	Screenshot Content	Problem Solved
1	Error Page	Identify error type
2	eSIM List Page	Check if installation succeeded
3	Data Line Settings	Check if default card is correct
4	Roaming/Network Selection	Check roaming and selection status
5	APN Page	Check data access parameters

Beyond screenshots, there is another type of information often ignored: what steps you have already taken. It’s not surprising if customer service sends a template, because most users’ first messages don’t include this part. As long as you list your attempted steps clearly, the other party is less likely to ask you to do them again.

A more useful way to write looks like this:

• Restarted device 2 times
• Airplane mode turned on for 30 seconds and then off
• Data roaming is on
• Mobile data line switched to Belgium eSIM
• Tried manual network selection: Proximus and Orange Belgium
• Waited 25 minutes after arrival in Brussels
• Still showing No Service

This set of content has several benefits. First, customer service knows you have completed basic troubleshooting. Second, they can see you didn’t just start testing. Third, if an escalation to the technical team is needed, this information can be transferred without secondary reorganization. For many support teams, “what you tried” is just as important as “current status.”

Location also affects processing speed. Writing “I’m in Belgium” is not enough, because network access performance varies greatly between Belgian airports, metro stations, mountain areas, borders, and indoor hotel environments. More appropriate descriptions would be city names like Brussels, Antwerp, Ghent, or Bruges, followed by whether you are at the airport, a hotel, or an outdoor street area. For example, “Currently in Brussels Airport arrivals hall” and “Currently in central Antwerp, outdoors” mean completely different things to customer service.

You can write location like this:

Wording	Information Completeness
In Belgium	Low
In Brussels	Medium
In Brussels Airport, arrivals area	High
In central Bruges, outdoors, after 25 minutes	Even Higher

Some platforms will request EID, IMEI, or ICCID. Users often worry these numbers are too technical, but they are mainly used to verify the relationship between device and configuration. They aren’t needed every time, but if customer service mentions them, be ready. EID is the eSIM device identifier, IMEI is the device identifier, and ICCID usually corresponds to the SIM profile data. You don’t have to send them all in the first message, but it’s best to know where to find them so you can provide them within 1 to 2 minutes if requested. The faster you provide them, the faster the ticket moves forward.

Below is a structure better suited for sending in the very first message—it’s short but complete:

Order ID: XXXXX
Purchase email: xxx@email.com
Plan: Belgium eSIM 3GB / 15 Days
Device: iPhone 14
OS: iOS 18.x
Current location: Brussels, Belgium
Issue: eSIM installed successfully, but still shows No Service after 30 minutes
Tried: restarted twice, data roaming enabled, manual network selection tested, airplane mode toggled once
Attached: screenshots of error page, eSIM settings, mobile data settings

This type of message usually only takes 8 to 10 lines but covers what customer service asks first. Compared to a single “Can you help me?”, processing efficiency will be significantly higher. Here is a copyable English template suitable for most Belgium eSIM support scenarios:

Hi, I need help with my Belgium eSIM.
Order ID: [your order ID]
Purchase email: [your email]
Plan: [plan name]
Device: [device model]
OS: [iOS/Android version]
Current location: [city in Belgium]
Issue: [Invalid QR Code / Activating / No Service / No Data]
I have already restarted the device, enabled data roaming, toggled airplane mode, and tried manual network selection.
The issue is still there after [X] minutes.
I’ve attached screenshots of the error page, eSIM page, and mobile data settings.

By sending complete information, it’s easier for customer service to judge in the first round whether it’s a QR code issue, installation issue, registration issue, or data access issue.

Continuing to Follow Up

Many eSIM tickets aren’t stuck because “no one replies,” but because the same content appears round after round. Customer service sends a standard step, the user replies “still not working,” and then another similar step is received; back and forth for 3 rounds, and 30 to 90 minutes may have passed, but the problem status has no new information.

To reduce this back-and-forth, change your thinking: every reply should add time, action, result, and screenshot changes. Customer service doesn’t just look at whether you followed instructions; they need to know if doing so changed the status from Invalid QR Code to Unable to Add eSIM, from Activating to No Service, or from No Service to having signal but no data.

Understand an effective follow-up as 4 parts: what you did at what time, how long it lasted, where the result stopped, and whether there is a change compared to the last round. For example, if support asks you to restart and wait 5 minutes, it’s not suitable to just reply “done” or “still not working.” A better way to write is: “Restarted at 14:20 local time, waited 10 minutes, still showing No Service, data roaming remains on, attached updated screenshot.” This single sentence includes the 4 points support needs most: time, action, wait duration, and current status.

This table shows the difference between the two reply styles:

Reply Style	Information Gained by Support	Common Result
“Tried it, still not working”	Low	Receive template steps again
“Restarted at 14:20, still No Service after 10 mins, attached new screenshot”	High	Easier to move to next step
“I tried everything”	Low	Support continues to ask questions
“Tested Proximus and Orange Belgium, both unable to register network”	High	Easier to escalate troubleshooting

Many users provide complete data in the first round but start getting shorter by the second or third, eventually only saying “still not working,” “same,” or “still no net.” This makes the ticket vague again. Because customer service swaps, shifts, or teams change—especially in cross-timezone support—it’s not uncommon for the same ticket to be handled by 2 to 3 different people within 6 to 12 hours.

You might think the previous person already knows the background, but the next person might not quickly catch the status change in dozens of records. So every reply should be able to stand alone, including at least the device, location, current error, and results of the operations just performed.

A structure better suited for continuous follow-up can be written in this order:

• Current time
• Current city or location
• Operation just performed
• How long you waited
• Current status
• Is there a difference from the last round
• Whether a new screenshot is attached

For example:

Current time: 15:05 in Brussels
I turned airplane mode on for 30 seconds and then off
Waited 8 minutes
Status is still No Service
No change from previous check
Attached updated network settings screenshot

This format looks like it adds a few lines, but it saves later back-and-forth confirmations. Customer service won’t need to ask “When did you do it?”, “How long did you wait?”, “Is it still the same?”, or “Do you have a screenshot?”.

Many people overlook that “status change” itself is important. For example, moving from Activating to No Service looks like it still doesn’t work, but for the support team, it means installation or data delivery might be finished, and the problem has moved toward the network registration stage. Another example is moving from no signal at all to 1-2 bars but no data; this indicates the device may have connected to the local wireless network but the data layer isn’t open. If you only reply “still not working,” these changes are lost; but if written clearly, the troubleshooting direction narrows faster.

Try to write down these status changes during follow-ups:

Before Change	After Change	Probable Judgment Direction
Invalid QR Code	Unable to Add eSIM	Installation entry change, config issue
Activating	No Service	Installation ended, entering registration
No Service	Signal but no data	Network connected, data access incomplete
Signal but no data	Can open web but slow	APN or line quality issue
Auto selection fails	Manual selection sees local carriers	Coverage exists, access not finished

If customer service asks you to test in steps, it’s best to do only one at a time—don’t change 4 settings at once. For example, if they ask to toggle airplane mode, don’t simultaneously restart the device, delete the eSIM, and swap primary/secondary cards. If the result changes, support won’t know which step caused it. The most time-saving way for a user is not doing everything useful at once, but doing them in order, adding only 1 variable each time.

You can make a simple log of this:

Time	Action Performed	Wait Duration	Status Result
14:20	Restart device	10 minutes	No Service
14:35	Toggle airplane mode	8 minutes	No Service
14:50	Manually select Proximus	5 minutes	Registration failed
15:00	Manually select Orange Belgium	5 minutes	Registration failed

Sending this kind of record to support is more helpful than “I did it many times and it’s useless.” it allows the other party to see you completed tests in sequence and makes it easier to judge whether to check plan configuration, installation counts, or network authorization.

Some support teams repeatedly send template messages; this doesn’t necessarily mean they haven’t read your content. Many first-line agents are required to complete fixed steps first, like confirming a restart, roaming, and manual selection. In this case, the best thing for a user to do isn’t to complain, but to turn the template requirement into verifiable feedback. For example, if support says “please enable data roaming and restart the device,” you reply:

Data roaming was already enabled before this step.
Restarted the device at 16:10 local time.
Waited 12 minutes.
Current status: still No Service in Antwerp.
Attached screenshot of roaming setting and current network page.

Writing this way serves 3 purposes: it tells them the step is done; it shows the step didn’t bring change; and it conveniently adds the location and screenshot. Seeing this, support can more easily move from the basic script to the next layer of processing.

Also, be careful not to frequently open new tickets or switch channels. Many users send live chat, email, in-app tickets, and social media DMs all within 20 minutes. It looks like it’s faster, but it actually fragments information. Different channels aren’t necessarily synced automatically; support might ask you to restart on channel A and then ask for your order ID again on channel B. A safer bet is to keep 1 main communication line, like live chat; if you need to switch to email, bring along previous ticket numbers, order numbers, and completed steps.

This table helps you decide when to switch channels:

Scenario	More Appropriate Channel
Need net immediately after landing, troubleshooting on-site	Live Chat
Need to send 4–6 screenshots or long explanations	Email
Already have a ticket number, need to add materials	Reply in original ticket
Need to keep processing records	Email or Ticket System
Social media can only send brief messages	Only for nudging, not for main comms

There is also a common follow-up issue: support asks you to delete the eSIM, but you don’t confirm if it can be reinstalled first. Many profiles only support 1 installation, some support limited reinstalls, and some need a backend reset before reuse. Once you delete it, you might receive “code already used” or “plan cannot be added again” within 2 to 5 seconds. At that point, you’ve added another round of reissue or reset. So when support mentions deletion, it’s better to reply first:

Before I remove the eSIM, can you confirm whether this QR code supports reinstallation?
If not, please confirm a replacement QR code will be issued.

This confirmation reduces an unnecessary back-and-forth and avoids deleting a configuration that could have been kept.

If support has sent similar basic steps for 2 consecutive rounds and you’ve already fed back results completely, you can organize a clear update message and ask them to continue checking. Keep the language steady; no need to be emotional. For example:

I have completed restart, airplane mode toggle, data roaming check, and manual network selection.
The issue remains unchanged after 35 minutes in Brussels.
Current status is still No Service.
Please help check the eSIM profile status or network activation on your side.

Such a message has several characteristics: steps are complete, wait time is clear, status is clear, and request direction is clear. It doesn’t sound blunt and is more likely than “please fix this now” to push the ticket forward. Look at a small checklist for long-term follow-up. Before every reply, check these 6 items:

• Did I write the current time in this reply?
• Did I write the current city or location?
• Did I write the action just completed?
• Did I write how many minutes I waited?
• Did I write the current status?
• Did I attach an updated screenshot?

If more than 3 of these 6 items are missing, what support sees is often an incomplete picture. Especially when a problem drags on for over 1 hour, the status may have changed more than once, making these details even more important.

To keep communication coherent, you can also use “from last round to this round” to express change. For example:

Since the last update, the status changed from Activating to No Service.
I am now in central Ghent, outdoors.
Waited another 20 minutes.
Still unable to access data.

Here, status change, location change, and wait duration are all included. Support can immediately see the problem isn’t static but has moved from one stage to another.

Use this table as a reference for “continue following steps” vs. “request escalation”:

Situation	Better to Follow Steps	Better to Request Deeper Check
Just received the first round of standard steps	Yes	No
Status changes after following steps	Yes	No
Status remains unchanged after two rounds of steps	No	Yes
Same status after waiting 30–60 minutes	No	Yes
Already provided order, device, screenshots, and location	No	Yes
Fails again after deleting and reinstalling	No	Yes

If you need to request further processing later, the language doesn’t need to be aggressive; just state the completed information clearly. For example:

I’ve completed the requested checks and provided updated screenshots.
The issue has remained unchanged for 45 minutes.
Could you please review the profile status, installation limit, or network activation from your side?

This expression is more likely than repeatedly saying “still not working” to get the ticket to the next step because what you provide is verifiable information, not emotion.

Finally, remember: don’t make every reply shorter and shorter. Many users send 8 lines for the first message, 3 for the second, and only 2 words for the third. The further a ticket goes, the more complete the content needs to be, as support needs to confirm if the latest status is consistent with before. Adding 20 to 40 words each time you follow up can often save an entire round of back-and-forth.