How we review content
Who reviews what, and the checklist that decides whether a page ships.
Last updated September 5, 2026
Three layers of review
- Technical: install steps, iOS and Android menu names, handset limitations.
- Language: readable by someone who has never used an eSIM, no unexplained jargon.
- Integrity: no overclaims, no unsourced facts.
What blocks publication
- A speed or coverage claim with no source.
- Claiming a handset is supported without manufacturer specifications.
- Promising refund terms that do not match the actual policy.
- Promising a fixed reply time we do not actually measure.
Who is in the room before a page goes live
Every article passes through both of our co-founders, Bob Kanokphon Thongdee and Porsch Kunnipat Siramanakul, before it goes live. One is the writer, responsible for the structure and completeness of the content. The other is the reviewer, reading with a different lens and looking for the kind of gap a writer can miss simply from being too close to the material. The byline therefore shows the author and, under Reviewed by, the second founder. Splitting the role this way does not make everything perfect, but it cuts the chance that a single mistake reaches a reader with nobody having flagged it.
For pages that touch money or a device's safety, such as pricing pages, refund terms and installation guides, the reviewer reads those parts in a separate pass: prices against the supplier catalogue, refund wording against the policy that applies, and install steps against the manufacturer's documentation, rather than trying to catch everything in a single read.
From draft to publication
- 1Draft the contentThe writer gathers information from acceptable sources, as described on our sources page, then drafts the piece so that every language version says the same thing.
- 2Technical checkThe reviewer checks the draft against manufacturer and operator documentation: iOS and Android menu names, handset limitations, and terms that vary by provider.
- 3Language and clarity checkEach language version is read separately to check whether someone who has never used an eSIM would actually follow it, not just for grammar.
- 4Integrity and disclosure checkThe page is checked for overclaims and for figures with no source behind them, and its source list must give the publisher and the date each source was last checked.
- 5Publish and keep watchingOnce published, a page shows its published and last-updated dates and stays open to reader reports at any time, not only at the moment it first goes live.
Checklist for installation guides
Installation guides get some of the strictest review, because a single wrong step can leave a reader unable to complete setup, or worse, cause them to delete an existing profile by accident. A reviewer reads step by step against the manufacturer's published instructions, rather than skimming for the general shape, and must flag anywhere a step differs by brand or OS version instead of collapsing it into one instruction that does not actually hold for every handset.
Checklist for device compatibility tables
A device compatibility table must always trace back to a checkable source. A reviewer will not let a handset model into the table just because someone said it works. Without manufacturer specifications or a checkable announcement behind it, the model is left out of the table, however often it is asked about, because getting this wrong has a direct effect on a reader's buying decision.
Checklist for destination and coverage content
Destination pages tend to get read while someone is actively planning a trip, so a reviewer pays particular attention to writing coverage as something that depends on the provider and the actual area within that country, rather than as a flat claim that it works everywhere. Where part of the picture depends on a provider and cannot be confirmed at review time, the page says so plainly rather than guessing and writing it as settled fact.
Checklist for pricing and plan pages
Prices and data allowances on plan pages come from the supplier catalogue, not from a number a writer typed into the copy. Where any content mentions a price, the reviewer checks it against the plan page at that time, and where a price carries a condition, such as being limited to certain countries or a certain window, that condition has to appear on the same page, not tucked away somewhere else.
Checking that every language says the same thing
Pages are published in more than one language, but the reviewer does not check this by translating word for word, since a literal translation often reads unnaturally in the target language. What gets checked is that the meaning matches: a warning that appears in one version has to carry the same weight in the others, not softened or added to along the way. Finding a warning present in one language and missing from another counts as an error that has to be fixed before publication.
Independence between review and anything sales-related
Every plan on this site is sold by us directly, through suppliers we connect to ourselves. There are no partner or sponsor deals that could influence what an article writes or warns about. The information behind an article comes from official primary documentation and supplier data alone. If a plan does not suit the situation an article is discussing, the reviewer lets the content say so plainly, rather than softening the wording to avoid friction with anyone.
What sends a page back for revision before it ships
| What is found | What happens |
|---|---|
| A speed or coverage figure with no source | It is removed, or rewritten to say the answer depends on the provider, before publishing |
| An install step does not match the real menu in the stated OS version | It goes back to the writer to recheck against the manufacturer's documentation before it is corrected |
| A price stated in an article does not match what the checkout system shows | The figure is corrected to match the system first; the page does not go live until it is fixed |
| Language versions carry unequal warnings | All versions are aligned to carry the same warning with the same weight |
Review after a page is already live
Review does not end at publication. Pages are pulled back into review when something changes, as described on our content update policy page. Prices follow the supplier catalogue, and installation guides are re-read when iOS or Android ships a major release, since a menu can move or be renamed in a way we do not control. The updated date on each page shows when it last changed.
When you spot something that looks wrong
Our review process does not claim to be error-free. If you follow a step and it does not match what your device actually shows, or a figure looks off, send the page link via LINE at https://lin.ee/skDPoNx (@esimonline) or email at esimonline.asia@gmail.com, with what you found and where. We check it against the original source before deciding how to fix it, rather than changing a page purely on someone's say-so without rechecking it.
What this review process cannot guarantee
Review lowers the chance of a mistake; it does not erase it entirely. A provider can change terms without warning us first, a manufacturer can shift a menu in a minor update we have not caught yet, and one handset in a series can behave differently from another with seemingly identical specifications. What this process can do is keep the risk as low as it can be checked at the time of review. It is not a promise that every word on every page stays correct forever with no exceptions.
The role reader questions play in the review loop
A question that comes in on LINE or by email does not end once it is answered once. If the same question keeps arriving from different people, that is a signal to go back and look at where the related page is unclear, then feed it back into the review cycle so it gets clearer, rather than leaving the next person to ask the same thing all over again.
Why iOS and Android get checked separately
A reviewer does not read an installation guide as one single flow for both systems, because iOS and Android menus do not follow the same order, and the term Apple uses for a function does not always match the term a given Android manufacturer uses for the same thing. Review therefore runs in two separate passes: one against Apple's own support documentation, another against the guides each Android manufacturer publishes. Where a step cannot use the same wording across every brand, the reviewer has to flag it plainly as varying by brand and OS version, rather than writing one instruction that sounds complete but does not actually hold for every handset.
What a reader can see on every page
We would rather you did not have to take this page on trust, so every article shows what can be checked on the page itself. The byline names the co-founder who wrote it, and Reviewed by names the other co-founder who checked it. The page shows its published and last-updated dates, and a source list giving the publisher of each source and the date we last checked it. Those sources are official primary pages from government bodies, operators, manufacturers, standards bodies, or competitors' own sites. If a page does not match the source it lists, you can see that for yourself and tell us.
Where the photos come from
Japan travel articles use photos of places from Wikimedia Commons under free licences, and each one is credited beneath the photo with the author, the licence and a link to the file page. Other pages use stock photos from Pexels. We do not present any of these as our own photography, and we do not use a photo to suggest we were somewhere we were not. If you spot a credit that is missing or wrong, tell us and we will fix it.
When a provider changes terms while an article is already live
If a provider adjusts terms after an article has already gone live, such as a coverage area or usage condition, the affected page is pulled back into review right away. Letting outdated information sit could leave a reader making a purchase decision based on something that is no longer true. A fix like this is treated as more urgent than most other work, because it affects a buying decision directly.
Why the reviewer is never the same person as the writer
Even the most experienced writer tends to read past their own mistakes more easily than someone else would, since the brain stays anchored to what it meant to say rather than what actually ended up on the page. So we keep a simple rule: whoever writes a page is never the one who reviews it, however confident they feel about having got it right. With two co-founders, that means the other founder always does the review. This rule applies to every page with no exception for ones that look short or simple, because the most serious mistake sometimes hides inside the page that looks least complicated.
- Before any page goes live, we check that no speed or coverage figure appears without a source behind it
- We check that install steps match the manufacturer's documentation for the stated brand and OS version
- We check that any price stated in the content matches what the checkout system shows
- We check that all language versions carry the same warnings with the same weight
- We check that no page claims 24/7 support when actual support hours say otherwise
FAQ
Does a real person review every page?+
Yes. Each article is reviewed by the co-founder who did not write it, and that name appears under Reviewed by in the byline.
Does eSIMonline earn a commission that could influence what an article recommends?+
No. We sell every plan ourselves, through suppliers we connect to directly. Our revenue is only the margin on those plans, not a commission from anywhere, and it does not depend on which plan an article recommends.
What if I find an install step that does not match my device?+
Send it via LINE at https://lin.ee/skDPoNx (@esimonline) or email at esimonline.asia@gmail.com, with your handset brand, model and OS version. We check it against the manufacturer's documentation before making a fix.
How often is content re-reviewed after it first goes live?+
Pages are pulled back into review when something changes: a provider changing terms, a major iOS or Android release, or a reader reporting a mismatch. Prices follow the supplier catalogue, and the updated date on each page shows when it last changed. Details sit on our content update policy page.
Does this process guarantee zero mistakes?+
No. It keeps the risk as low as it can be checked at review time, but a provider or manufacturer can change something we have not caught yet.
Instagram and TikTok have no web share button, so we open your phone's share sheet or copy the link instead.