Connect usage, network state, orders, installs, support, and reporting to the tools your team already runs. eSIM Copilot handles the mobile layer; your business 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
Use eSIM Copilot when a network state, customer action, admin request, or billing moment needs to update another system.
Create orders, assign plans, and send install links when a customer is onboarded, an employee joins, or travel is approved.
Watch usage, balance, network state, and renewals. Trigger approvals, top-ups, caps, or alerts before costs surprise finance.
Push line-level costs, plan state, diagnostics, and install status into Xero, Zendesk, Jira, CRMs, or your data warehouse.
Let Claude or an internal assistant search plans, check usage, prepare orders, and hand off anything that needs approval.
Business automations
Use the API as an automation layer for mobile operations. A spend threshold, CRM change, support case, or finance close can move the right task into the right system.
When usage or monthly spend crosses a threshold, eSIM Copilot can ask for approval, add a top-up, cap access, and leave a clean audit trail.
Trigger
Action / destination
TeamsOrders, renewals, top-ups, and usage can be exported with the account, user, country, plan, and cost-centre metadata finance needs.
Trigger
Action / destination
Use CRM stage changes to create a sub-account, issue the first business phone plans, and write activation state back to the customer record.
Trigger
Action / destination
Failed installs, disabled profiles, low balance, or network issues can land in support with ICCID, device state, plan, usage, and recent events.
Trigger
Action / destination
Schedule exports for usage, active plans, spend, countries, and failed actions so ops teams can review the estate without logging into another tool.
Trigger
Action / destination
Through MCP, an AI assistant can search plans, inspect usage, create orders, guide install, and prepare a human handoff when the request needs judgment.
Trigger
ClaudeAction / destination
Start with the mobile event your team already cares about: a customer action, network change, billing moment, device issue, or admin request.
Trigger
Action / destination
The exact payloads live in the docs. The important part is that the automation can start from eSIM Copilot or from the SaaS tool your team already treats as the system of record.
Business events
When a plan is bought, a line comes online, usage changes, or access is stopped, eSIM Copilot can notify the systems that need to act. The technical event names live in the docs.
A plan is purchased
Send the install link by your channel of choice. Mark the record as connected in your CRM, HRIS, or customer portal.
An eSIM is online
Sync to your billing or product state. Push a "you are online" message in your app. Update the customer-success dashboard.
Usage needs attention
Push a Slack or Teams alert. Create a top-up approval. Notify the owner before a hard cap hits.
A plan renews
Reset your internal billing cycle. Log to accounting. Update spend forecasts and customer-facing reports.
Company access is stopped
Trigger your off-boarding flow. Stop company mobile access, remove the cost-centre charge, and sync the action to your audit log.
A plan is cancelled
Update the customer account. Stop renewal messaging. Hand off to support or customer success with context.
Full event reference, signature verification, and replay tooling at docs.esimcopilot.com.
The MCP angle
The MCP server gives an agent scoped access to the same platform actions a human would use: search, order, inspect usage, guide install, and prepare support handoff.
Your AI support agent doesn’t just answer questions about plans. It can 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 navigation. "Stop access for everyone leaving this month." "Show me plans over 80% usage." The agent does the rest, signed in as the admin.
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.
Useful next stops for embedded checkout, app experiences, workplace mobile, integrations, and the network layer underneath.
