Editorial contact

A factual correction is more useful than a generic compliment.

Write to us if an explanation is unclear, a technical detail needs correction or a useful reader question is missing. Direct email is available at [email protected].

Shared desk with laptops, phones and coffee cups

What this contact route is for

esimg is an independent information site. We welcome notes about an unclear sentence, a device-menu change, an out-of-date public reference or a topic that would help readers plan mobile connectivity abroad. Specific context makes a correction easier to assess: the page, the sentence or heading, the device and software version where relevant, and a source if one is available.

We cannot check a plan balance, inspect an activation code, remove a handset restriction, change a carrier account or diagnose a live provider outage. Those matters belong with the company that issued the plan, the carrier that manages the line or the device manufacturer. The FAQ may help you identify which party is appropriate.

If you need context before writing, the full guide and device checks explain the common terminology we use.

Compose an email

This form opens your email application with the fields placed in a draft. No data is transmitted to or stored by this site.

A note on support boundaries

A useful independent site should say where its knowledge stops. We can explain why a phone might show an installed profile but have the wrong data line selected. We can explain how a carrier lock differs from eSIM hardware support. We cannot see the state of a plan you obtained elsewhere, and we should not pretend otherwise.

For technical questions tied to a specific subscription, retain the activation instructions and error wording, then contact the issuer of that subscription. For a device menu or lock question, start with the handset manufacturer or relevant carrier. This approach is slower than a promise of instant support, but it sends the question to the party with the information needed to answer it.

Please also read our privacy policy before sending personal information. We do not need account credentials, activation codes or identity documents to consider an editorial correction.

Send only what the editorial question needs

A page URL, a quoted sentence, the handset model and a public reference are usually enough to report a factual issue. Please leave out activation codes, account credentials, payment details and identity documents. We do not need them, cannot verify a live subscription with them and do not want sensitive details sent through an editorial inbox.

The form deliberately opens an email draft rather than posting to a database. You can inspect and edit the message before sending it through your own mail application. If that application is not configured, use the visible [email protected] address instead. Our privacy policy describes the limited handling of email correspondence.

We aim to keep the editorial route human and proportionate. A correction may lead to an update, a clarification or a note that the specific answer belongs with a device maker, carrier or plan issuer. It will not create a support case for an external mobile service.

Sunlit office interior with shared tables and chairs — The editorial contact route is for clear, evidence-based notes.