Provisioning is part of the customer journey
An eSIM journey starts before a profile is downloaded. A customer needs an eligible offer, an order, the right subscription context and a way to understand the next action. The provisioning result then has to reach the systems responsible for service and support.
We focus on the software connecting those parts of the journey: the BSS customer and order workflow, the OSS activation process and integration with the selected provisioning ecosystem.
Choose the provisioning context first
Consumer and IoT eSIM deployments have different interaction models. Device capabilities, user participation and fleet management requirements affect the integration design. A consumer activation flow should not be assumed to fit an unattended device deployment.
Our engineering discussions cover the order states, profile references, partner interfaces and failure handling needed for your chosen context. Operating a provisioning platform and integrating with one are separate responsibilities and should be assigned explicitly.
We map profile references, device and subscription identifiers, partner callbacks and the status a digital channel can safely show. The workflow also needs a clear route for a delayed download, an incomplete activation or a change of device.
- eSIM onboarding and activation journeys
- Provisioning partner integration
- Customer and subscription state handling
- Recovery paths for incomplete activation
Make activation outcomes understandable
A provisioning request is not the same event as a working subscription. Define the evidence available from each system and decide which status can be shown to the customer or support team.
This connects naturally with our Order Orchestration Platform and Telco CRM. The implementation scope should explain how an activation is initiated, how progress is recorded and who owns an exception.
Technical references
Primary references for the concepts discussed here.