Send usage, orders, installs and support events into the systems you already run, from Slack to Xero to your CRM, for automation, reporting and compliance. eSIM Copilot handles the mobile side; your rules decide what happens next.
Automation flow
Trigger
Usage threshold
Notify
Slack approval
Ask for top-up approval
Spend controlled before overage
Finance
Monthly close
Export
Xero report
Sync orders and usage
Line-level costs reconciled
Support
Install failed
Route
Zendesk ticket
Attach eSIM diagnostics
Support starts with context
Events
orders, usage, installs
Controls
approve, top up, disable
Reports
teams, customers, costs
What you can automate
When something happens on a mobile line, the right system hears about it: finance, support, HR, or your own product.
Create orders, assign plans and send install links when someone joins, a customer onboards, or a trip is approved.
Watch usage and renewals, and trigger approvals, top-ups or caps before costs surprise anyone.
Send line-level costs, plan status and diagnostics into Xero, Zendesk, your CRM or your data warehouse.
Let Claude or an internal assistant check usage, prepare orders, and pass anything sensitive to a human.
Business automations
Start with a moment your team already handles by hand. These are the patterns teams set up first.
Rising usage lands as an approval in the channel your team already watches, with an audit trail built in.
Trigger
Action / destination
TeamsOrders, renewals and usage export with the account, plan and cost-centre detail finance needs.
Trigger
Action / destination
A CRM stage change sets up the account, issues the first plans, and writes activation status back.
Trigger
Action / destination
Failed installs and network issues open tickets with the device, plan and usage context already attached.
Trigger
Action / destination
Scheduled exports keep a daily view of usage, spend and issues in the tools ops already reads.
Trigger
Action / destination
An assistant can search plans, check usage, create orders, and hand off anything that needs judgment.
Trigger
ClaudeAction / destination
Start with the event your team cares about and connect it with the API, webhooks, MCP, or a no-code tool.
Trigger
Action / destination
The exact payloads live in the docs. Automations can start from eSIM Copilot or from the SaaS tool your team already treats as the system of record.
Business events
When something changes on a line, eSIM Copilot tells the systems that need to know. The technical event names live in the docs.
A plan is purchased
Send the install link through your channel of choice, and mark the record as connected in your CRM or portal.
An eSIM is online
Update billing or product state, or send a "you’re online" message in your own app.
Usage needs attention
Alert the owner in Slack or Teams and raise a top-up approval before a hard cap hits.
A plan renews
Log it to accounting and update spend forecasts.
Company access is stopped
Run your offboarding flow: stop access, drop the cost-centre charge, and record it in the audit log.
A plan is cancelled
Update the customer account, stop renewal messaging, and hand off to support with context.
Full event reference, signature verification, and replay tooling at docs.esimcopilot.com.
AI assistants
Connect Claude or your own assistant and it can do what an admin can: search plans, place orders, check usage, and guide installs, inside the permissions you set.
Your AI support agent can answer plan questions, check usage, add top-ups, guide install, and hand off to a human with the right context.
Let an agent answer "who needs more data?", "which installs failed?", or "create a plan for this trip" with real actions against eSIM Copilot.
Natural language replaces dashboard clicks: "stop access for everyone leaving this month", "show me plans over 80% usage". The agent does the rest.
MCP server reference, authentication scopes, and a sample agent walkthrough at docs.esimcopilot.com.
Capabilities
Programmatic access to plans, orders, eSIMs, subscriptions, usage, users, reports, and webhooks. Full spec published.
Business moments such as plan purchased, eSIM online, usage needs attention, or access stopped. Signed payloads, retries, replay.
Expose eSIM Copilot to AI agents. Search plans, create orders, check usage, guide install, and route support in natural language.
Multi-tenant by design. Isolated users, billing, and spending controls per customer, partner, or sub-brand.
Secure admin view for orders, usage, reports, approvals, support cases, and webhook replay when someone needs to inspect the automation.
Connect eSIM Copilot to SaaS tools without writing backend code. Good for approvals, alerts, reporting, and support flows.
API keys per environment, role-based access control, audit logging on every mutation. SAML SSO for the dashboard.
Provision in batches, export account activity, and reconcile usage by customer, team, country, or cost centre.
API access, signed webhooks, and MCP tooling are part of paid plans. The connectivity itself is priced by the plan: country, duration, data, and business requirements.
Platform fees
0
No per-call charge. No webhook delivery fee.
Included
API + webhooks + MCP
Built into paid plans so automation can start without a separate integration meter.
Ready to automate
Full reference, OpenAPI spec, webhook signatures, and SDK examples are live at docs.esimcopilot.com. Get a sandbox key from the dashboard, or talk to us about the workflows you want eSIM Copilot to run.
FAQ
At docs.esimcopilot.com. REST endpoints, OpenAPI spec, webhook signatures, MCP server reference, and code samples. Generate a sandbox key from the dashboard once you sign up.
Available on request. Talk to us with your stack and we’ll get you set up. The OpenAPI spec also generates an SDK in any language if you prefer to self-serve.
No. Embedded checkout is one use case. The API is also used for internal automations: provisioning from approvals, usage alerts, finance exports, support tooling, webhook replay, AI agents, and no-code workflows.
HTTPS POST to your endpoint, JSON payload, HMAC-SHA256 signature in a header. Retries on 5xx or timeout with exponential backoff. Replay endpoint available for debugging.
A Model Context Protocol server that exposes the eSIM Copilot API to AI agents. The agent (Claude, ChatGPT, your custom assistant) can read plans, create orders, manage eSIM lifecycle, and answer customer-support questions. All in natural language. Auth is per-user, per-tool.
Yes. The install URL, QR code, and one-tap install page can all carry your brand and domain. Customers never see eSIM Copilot. For deeper customisation, the API returns the LPA activation code so you can build a native install flow.
No. The platform is fully managed. Carrier integrations, BSS, and compliance all sit on our side. You can BYO carrier deal, but the platform itself is SaaS.
