The support tickets an eSIM reseller gets
Five tickets make up almost all eSIM support, and four of them are preventable before checkout. What each one costs and what removes it.
Small in volume, brutal in timing
eSIM support has an unusual shape. The volume is low — most orders complete with no contact at all — but the timing is the worst of any product category, because the customer contacts you precisely when they have no working connectivity, in a different time zone, having just landed.
That combination misleads people twice. It looks cheap when you model the business, because the ticket rate is a few percent. Then it turns out that a few percent of orders needing an answer within the hour, at hours you do not work, is a staffing problem rather than an inbox problem.
The useful metric is not tickets per order. It is what share of your tickets arrive outside your working hours, and how many of those become refunds or chargebacks because nobody answered.
The five tickets
Across travel eSIM resale, almost all contacts fall into five categories. Four are preventable before the sale, which is the entire point of this article.
1. The device cannot use an eSIM at all
The customer bought a product their handset physically cannot accept. Nothing you do after the sale fixes it, and a refund is usually the only right answer. This is pure prevention: it is decided by what your product page said before they paid.
2. The device is carrier-locked
The handset supports eSIM but is locked to the network that sold it, so a third-party profile will not activate. Also unfixable by you, also a refund, and also preventable with one sentence before checkout.
3. The QR code has already been used
An eSIM profile is generally installable once. A customer who installs it, resets their phone and tries again finds it will not install a second time. Whether a replacement is possible depends on your provider, and whether you eat the cost depends on a policy you should decide now rather than during the conversation.
4. Installed, but no data
The profile is on the phone and nothing works. In practice this is nearly always a settings problem — data roaming off, the wrong line selected for mobile data, or an APN not applied — rather than a faulty eSIM. It is the one ticket that genuinely needs a reply, and it is the one a good delivery e-mail answers before it is asked.
5. Wrong destination, wrong dates, wrong size
A buying mistake rather than a product failure. Your exposure here is decided entirely by your refund policy and by how clearly the package was described. Validity that starts on activation rather than on purchase is the detail customers most often misread.
The copy that removes four of them
Three of the five are decided before the customer pays, and the fourth is decided by what you send after. None of this requires software.
- Put a device-compatibility check in front of the buy button, not in a help page. A short list of what is required and a link to how to verify it on their own phone removes tickets one and two almost entirely.
- Say the words "not carrier-locked" explicitly. Customers who have never heard the phrase will go and check, and the ones who cannot will not buy — which is the outcome you want.
- State when validity starts, in the package name if you can. "Starts when you activate" prevents more disputes than any refund policy.
- Make the delivery e-mail answer ticket four before it is asked: turn on data roaming, select this line for mobile data, and what to do if there is still no signal after ten minutes.
- Publish your refund rule for an eSIM that has been installed. Not because customers read policies, but because it means you are not inventing a decision at two in the morning.
Deliberately absent from that list: device-specific step-by-step instructions. They go stale with every OS release, your provider maintains better ones, and linking to theirs is both cheaper and more accurate than owning a page that quietly rots.
The refund decision, made in advance
The expensive thing about eSIM support is not the replies. It is making the same judgement call repeatedly, under time pressure, without a rule.
| Situation | Sensible default | Why |
|---|---|---|
| Device cannot take an eSIM | Refund in full | They bought something unusable; arguing costs more than the sale |
| Carrier-locked handset | Refund in full | Same, and not their fault in any useful sense |
| Installed, never used, unused validity | Refund at your discretion | You may be able to reclaim it; check with your provider before promising |
| Installed and data used | No refund | The product was delivered and consumed |
| Wrong destination, not yet installed | Swap rather than refund | Keeps the sale and costs you a support reply |
| Marginal or unclear | Refund quickly | Cheaper than a chargeback plus its fee plus the ratio |
That last row is the one that saves money and feels wrong. A chargeback costs you the sale, a fee on top and a mark against a ratio that can eventually cost you the merchant account. A refund costs you the sale. Argue about the twenty-dollar cases and you will lose more than you keep.
One thing to check before you write any of this down: what your provider will and will not credit back to you. Your refund policy to your customer and your supplier’s refund policy to you are two different documents, and the gap between them is money out of your margin.
Covering it without hiring anyone
Most resellers at this scale are one person, and the honest answer is not "provide 24/7 support". It is to make the hours you do not cover survivable.
- Publish your actual response time and hold to it. "We answer within one working day" that is true beats "24/7 support" that is not, and it beats saying nothing at all.
- Write five canned replies — one per ticket above — and keep them where you can send them from a phone. Most of your support load is five answers repeated.
- Put the four commonest fixes in the delivery e-mail. Every customer who solves their own problem at midnight is a ticket that never existed.
- Set an auto-reply outside hours that names the next reply time and links the self-service fixes. Silence is what turns a problem into a dispute.
- If you sell into one time zone in particular, move your support window to overlap their evening rather than your own.
And if none of that is workable for you, that is worth knowing before launch rather than after. Support is the disqualifier that catches most people who otherwise had a good business.
Frequently asked questions
How much support does an eSIM reseller business need?
The ticket rate is low — most orders complete silently — but the timing is punishing, because customers contact you when they have no connectivity, abroad, often outside your working hours. Plan for the hours rather than the volume: the useful question is what share of tickets arrive when nobody is answering.
What are the most common eSIM customer problems?
Five account for almost all of them: the device cannot use eSIM at all, the device is carrier-locked, the QR code has already been used, the profile installed but there is no data (usually a roaming or line-selection setting), and the customer bought the wrong destination, dates or size.
Should I refund an eSIM that has already been activated?
If data has been used, no — the product was delivered and consumed. If it was installed but never used, it depends on whether your provider will credit it back, so check that before you promise anything. For genuinely marginal cases, refund quickly: a chargeback costs you the sale plus a fee plus a mark on your dispute ratio.
How do I stop customers buying eSIMs their phone cannot use?
Put the compatibility requirement in front of the buy button rather than in a help page, name carrier locking explicitly, and link to how they can check on their own handset. Those two ticket types are entirely preventable and they are the two where a refund is the only possible outcome.
Do I need 24/7 support to sell travel eSIMs?
No, but you do need to be honest about your hours and to make the uncovered ones survivable — canned replies you can send from a phone, self-service fixes in the delivery e-mail, and an auto-reply that names the next reply time. Silence, not delay, is what turns a support problem into a chargeback.