Corrections policy
Tell us when we get something wrong — here is what happens next.
Last updated September 6, 2026
Send the details to esimonline.asia@gmail.com or via LINE with a link to the page. We acknowledge within two business days.
What we do with a report
- We check it against the original source.
- If it is wrong we fix it and update the page date.
- If the error could have affected a purchase decision, we add a correction note on the page itself.
- If it turns out to be correct, we reply with the source.
Why accuracy matters here
Someone reading this page is often about to decide on a plan, or trying to install an eSIM mid-trip. Even one wrong detail — an outdated device-menu step, say — can cost that person time or lead to a bad decision at a moment when there is no time to recover. This policy exists to make clear what happens once you spot something wrong.
Scope of this policy
This policy covers every kind of content our own editorial team writes: installation guides, comparison articles, destination pages, glossary explanations and other policy pages. It does not cover the text of listings sold by another seller, since those are written and maintained by that seller — though we still take a report and forward it on.
What counts as an error worth reporting
A worthwhile error is something checkable as actually wrong: an installation step that describes a device menu in the wrong place, a coverage description that does not match what an order page itself states, a broken link or one that goes to the wrong page, or a Thai translation that shifts meaning enough to mislead.
It is worth reporting even something small, like a typo or a menu name that has moved with a newer OS version, since small things like that add up and affect how trustworthy the whole page reads.
What this policy does not cover
Getting a different real-world speed than expected is not a content error, since speed depends on the destination network, conditions, and your own device — none of which we ever guarantee a figure for. In the same way, disagreeing with a comparison article's conclusion is not a checkable error in this sense. If you disagree but have new information behind it, send it and we will consider it.
Where to send a report
Send the details via LINE at https://lin.ee/skDPoNx (@esimonline), email at esimonline.asia@gmail.com, or phone at 089-942-0818 / 088-521-6848, with a link to the page where the issue appears. We take reports around the clock, every day.
Information that helps us fix it faster
- The full link to the page where you found the issue
- A short description of what is wrong and what it should say instead
- A source if you have one, such as a screenshot or a provider announcement
- Your order number, if the issue concerns a plan you have already bought
- Your handset brand and model, if the issue concerns installation steps or a device menu
What happens after you report it
- 1We acknowledge firstWithin two business days, as stated earlier on this page, so you know it has reached us
- 2We check it against the original source or the relevant orderWe do not decide from memory, but against something verifiable, such as a provider's documentation or your own order page
- 3We fix it and move the updated dateIf it could have affected a purchase decision, we add a correction note on the page itself too
- 4We reply back to youTelling you what was fixed, or if it turned out correct, explaining that with the source we used to check it
How we prioritise a correction
Not every error affects you at the same level. This table shows how we handle a correction differently depending on how much it matters.
| Level | Example | What we do |
|---|---|---|
| Minor | A typo or a broken link | Fixed as soon as it is found, with no special note needed |
| Factual | An outdated device-menu step | Content is fixed and the page's updated date moves |
| Purchase-affecting | Miscribing a plan's coverage | Fixed immediately, with a correction note added on the page itself |
Correction versus scheduled review
This policy covers correction triggered by someone reporting something wrong. Scheduled content review, such as reviewing device tables when a new model launches, happens on its own, without waiting for a report. The two processes run in parallel, and a single page can be touched by either one at a different point in time.
Common misunderstandings
| Common misunderstanding | What's actually true |
|---|---|
| A price that changed means the site got it wrong | Providers set their own prices; we update the page to match, so a price change is not a mistake on our part |
| Getting a different speed than expected means the article was wrong | Actual speed depends on the destination network and the handset, not a figure we can guarantee |
| Disagreeing with a comparison's conclusion counts as an error | That is a difference of opinion, not a factual error — if you have new information behind it, send it and we will consider it |
When we check and the original turns out correct
Not every report turns out to be an actual error. Sometimes the original was correct but explained in a way that could still confuse. In that case we reply with the source we used to check, and if it helps, we tighten the wording even though the original fact was already correct.
An example that speeds up a report
The clearest reports usually follow a simple pattern: the link to the page, what looks wrong, and what it should say instead. For example, an installation guide might point to one menu location, but a newer OS update has since moved that menu. Stating both the location the guide currently gives and the one you actually found lets us verify and fix it precisely without several rounds of back and forth.
It does not need to be long or formal. A short message with a link and a to-the-point description is more useful than a long explanation that never says which page it concerns.
When an error touches more than one page at once
Some errors do not sit on just one page. A menu step for one handset model, for instance, might repeat across several installation guides that mention the same model. If you spot this kind of error on one page, report the link for that page first, and we then check whether other pages repeat the same detail.
We fix every page carrying the same error in one pass, rather than page by page each time someone reports it again, so other pages are not left holding the same wrong detail unnoticed.
Reporting an error versus requesting a refund
Reporting an error under this policy means pointing out that content on the site does not match reality. Requesting a refund concerns an order you have already paid for that does not work as stated. The two can occasionally connect, such as when a plan page misdescribes coverage and leads to buying the wrong destination, but each is assessed under its own separate policy.
If you are not sure whether your situation is a correction report or a refund request, send the details through the same channel either way — we will help sort out which process it belongs to.
When you are not sure whether something is actually wrong
If you find something that looks odd but you are not sure whether it is genuinely wrong or just different from what you expected, send it anyway. You are not expected to verify it yourself before reporting — checking it against the original source is our job, not yours.
Reporting something that turns out to be correct after all is not wasted time on either side, since every check is also a chance for us to review whether the original wording was clear enough or worth tightening.
What this policy is trying to prevent
The purpose of this policy is not only to fix wrong content, but to stop the same error from affecting other readers who reach that same page later. Having a clear channel and a predictable process makes someone who runs into a problem more willing to report it quickly, rather than letting it slide because they have no idea what happens after they do.
We do not treat the number of reports we receive as something to be embarrassed about; it is a sign readers trust us to fix things. The faster a report reaches us, the shorter the window during which anyone else runs into the same wrong detail.
Reviewing this policy itself
We review this policy whenever the reporting process or contact channels change, not on a fixed schedule. If the steps written here do not match what actually happened when you reported something, tell us through the same channel.
FAQ
How long does it take before a correction is made?+
We acknowledge within two business days. The time to actually fix it depends on how many sources need checking — minor issues are often fixed as soon as they are found, while ones needing several checks can take longer.
Is there a public log of past corrections?+
Corrections that could have affected a purchase decision carry a note on the page itself, under our content update policy, rather than being collected into a separate combined log.
If I report something and the original turns out to be correct, will I hear back?+
Yes, always, along with the source we used to check it, so you can verify it yourself.
Do I need an account to report an error?+
No. Just send the details to the LINE or email listed here — unless the issue concerns your own order directly, in which case we will ask for the order number too.
How to report a correction so we can check it quickly
A few details let us check a report quickly: the link to the page, the sentence or heading you think is wrong, and what you found instead. If the issue depends on hardware or location, include the device model, the operating system version, and the country you were in, because the answer to many questions changes with all three.
When a change alters what a page means, we record what changed and when. Typographic fixes and rewording that leave the meaning intact are corrected silently, so the correction record stays useful instead of filling up with entries that change nothing for the reader.
- Send the page link together with the sentence you think is wrong
- Include device model, OS version and country when the issue depends on the device
- Attach a screenshot if you have one; it shows the real on-screen context
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.