The platform
One portal, three kinds of user, the same data
Employees arrange their own connection. IT manages, integrates and sees the whole picture. Finance gets the numbers. Everything the portal can do is available through the API, so you can have it land entirely in your own systems.
Self-service
Users arrange it themselves, through SSO
Automation
Joiners and leavers follow the source systems
Insight
Usage, costs and alerting in one place
Open
Full API, operator independent
Who does what
Every role sees exactly its own part
Employee
- Log in with the existing company account
- Order an eSIM, run a SIM swap, change device
- See your own usage and bundle balance
- Order a Travelsim for your own trip
- Block on loss or theft
IT team
- Set roles, permissions and approval rules
- Rollout through Intune or Jamf, or delivery by email
- All connections, sites and terminals in one list
- Alerting on outages, bundles and unusual usage
- Logging and an audit trail per action
HR and finance
- Joiners and leavers do not have to be reported separately
- Costs per department, site or cost centre
- Scheduled reports and exports
- One invoice stream, even across several services
Functionality
What the portal does for telecom management
Mobile, IoT and Starlink are managed in one place, whichever operator supplies the connection.
Connection management
Request, activate, swap, block, transfer
Usage and costs
Per user, department, site and country, with history
Alerting
Thresholds per bundle or profile, alerts before things go wrong
Roles and permissions
Who may order, who has to approve, who sees which group
Reporting
Exports and scheduled reports, including per cost centre
Audit trail
Every action recorded, including who did it and when
Alerting and caps
Step in before the invoice arrives
Explaining usage afterwards costs more time than capping it up front. You set the thresholds yourself, per profile or per group, and decide what happens when they are hit.
Setting thresholds
- A percentage of the bundle, or a fixed amount of data
- Separate thresholds for inside the EU, outside the EU and per country
- Per profile, department or individual user
- Several levels in sequence, for example 80 and 100 per cent
Who gets the alert
- The user, so they can adjust their behaviour
- The administrator or the department manager
- A shared mailbox or the service desk
- Your own system, through a webhook
What happens next
- Signal only, and let the user carry on
- Hard cap: data stops at the set limit
- Top up the bundle automatically instead of blocking
- A one-off unblock by the administrator, recorded
High usage
Flagging usage that deviates sharply from the user's own pattern, even within the bundle
Roaming up front
An alert on arrival in a country outside the bundle, before costs mount up
Outage
Connections, IoT cards and Starlink terminals that go offline or stop sending
Silent cards
Connections that keep running but have had no traffic for weeks
The API
If you would rather not use the portal, you do not have to
Every view and every action in the portal is available as an API. Organisations that want to keep their own service portal, data warehouse or ITSM as the front end feed it directly from our platform. The integration is machine to machine, with its own keys and permissions per integration.
Request the documentation →- Retrieve connections status, bundle, user
- Create orders eSIM, SIM swap, Travelsim
- Apply changes activate, block, transfer
- Retrieve usage per period, user or group
- Receive webhooks thresholds, outages, status changes
For telecom operators
The same platform under your own brand
Operators use the portal as the self-service layer for their own business customers: their own styling, their own domain, their own rates. We supply the platform and the integrations; the customer relationship stays with the operator.
- White-label portal and email communication
- Integration with the existing operator APIs
- Fewer tickets on your own service desk
Want to see the portal some time?
In half an hour we walk through the portal, the integrations and the API. After that you know whether it fits.