eSIM Copilot

Show a digest of account activity — KPI tiles (spend, orders, eSIMs, plans), a spend-over-time chart, top destination countries, eSIM status breakdown, and top plans. Uses the active account. Optional `days` (default 30) controls the window. Admins only on the platform — non-admins see an error in the response.

account_insights

Browse the eSIM plan catalogue. Use when the user asks "what plans are available?" or "show me data plans for Japan". The account context (currency, country) is resolved server-side from the signed-in user — do not pass identifiers in args. **Always pass ISO 3166-1 alpha-2 country codes — never country names.** "Japan" → `"JP"`, "United States" → `"US"`, "United Kingdom" → `"GB"`, "United Arab Emirates" → `"AE"`. Passing a country name (e.g. `"Japan"`) returns no matches because the portal looks up codes. Translate before calling. **Always scope the search.** Calling this with no filters returns hundreds of plans, which is not useful. If the user named a destination, pass `country` (single ISO-2 code) or a multi-country list via `countries` (array of ISO-2 codes). If they didn't name one but their request implies travel ("I'm going to Europe", "trips to Asia"), pass `region`. Otherwise default to a small list of popular travel destinations — pass `countries: ["US","GB","FR","ES","IT","JP","TH","AE","TR","MX"]` (pick ~6–10 relevant to the user's stated context, language, or account country) so the response is browseable. Only call without filters when the user has explicitly asked for the entire catalogue.

browse_plans

Create the user's first account. Use this only during onboarding — when `get_me` returns no accounts. Required: `name`, `country` (ISO alpha-2), `currency` (ISO 4217), `type` ("personal" or "business"). After creation the response advances the onboarding widget to the payment step. The widget normally drives this from its form; the model can also call it if the user has supplied all the inputs in chat.

create_account

Identify the current user. Returns the authenticated user profile and the list of accounts they belong to. Always call this first if the user has not been identified yet. **If `account_context.accounts` is empty, call `start_onboarding` next** — the user has no account yet and needs to go through the welcome flow before any other tool will work.

get_me

Open a step-by-step install guide for one of the user's eSIMs. Use when the user asks "how do I install this?", "I can't scan the QR", "help me set up my eSIM", or has just received a new eSIM. The widget shows the QR code, a one-tap install link on mobile, manual SM-DP+ / activation code details, and platform-specific instructions for iOS and Android. Pass `service_id` from `list_my_esims` or any earlier eSIM detail.

install_help

List the current user's eSIMs. Each entry includes ICCID, status (Ready to Install / Installed / Enabled / Disabled), label, and the account it belongs to. Use when the user asks about "my eSIMs", "my SIMs", or wants to see their lines. The account is resolved server-side from the signed-in user.

list_my_esims

List the user's plans (subscriptions) — data usage, renewal dates, and status. Use when the user asks "show my plans", "what data do I have left?", or "how many plans do I have?". The account scope is resolved server-side.

list_my_subscriptions

Take an action on a plan: cancel, renew, resume (after cancel), terminate (immediate, irreversible), or set_auto_renew (toggle auto-renewal). Mutating actions (cancel, renew, terminate) require `confirm: true` — call again with `confirm: true` after the user agrees. `resume` and `set_auto_renew` run immediately. The response is the refreshed plans list so the widget always reflects the new state.

manage_subscription

List the account's recent orders or payment history. Pass `kind: "orders"` for placed orders, `kind: "payments"` for the payment ledger. The account scope is resolved server-side.

account_history

List saved cards on the account, set the default, or delete one. Adding a new card from inside ChatGPT is not yet supported — point the user to the portal for that. Always pass `account_id` from `get_me`. Deleting a card requires `confirm: true` — without it the tool returns the card list with the chosen card flagged as `pending_delete` so the user can confirm.

manage_payment_methods