new subscriber onboarding taking days because SIM provisioning, KYC, and billing account creation all require manual steps in separate systems?
number porting rejected at a higher rate than your competitor because the orchestration between your porting request system and the network provisioning layer has gaps?
Telecom Subscriber Management Software
Custom subscriber management for MVNOs, ISPs, and telecom operators -- SIM provisioning, identity verification, plan management, and account lifecycle in one system, not a patchwork of back-office tools that require manual intervention for every plan change or port-in.
Built for operators where onboarding a new subscriber involves four separate systems and a plan change mid-cycle requires a support agent to manually update three records that don't talk to each other.
SIM and eSIM provisioning linked to network activation with automated status tracking
KYC and identity verification integrated at onboarding with document check and sanctions screening
Plan management with mid-cycle upgrades, downgrades, add-ons, and suspension handling
Number porting orchestration from customer request through donor notification to network cutover
RaftLabs builds custom telecom subscriber management software covering SIM and eSIM provisioning, KYC and identity verification, plan assignment and mid-cycle changes, number porting orchestration, account lifecycle management from acquisition through churn, and BSS integration with billing and network provisioning systems. Most subscriber management projects deliver in 14-18 weeks at a fixed cost.
100+Products shipped
·24+Industries served
·FixedCost delivery
·14-18Week delivery for subscriber management
The cost of disconnected subscriber management
Most MVNOs and ISPs reach a point where subscriber management is no longer a back-office inconvenience -- it is a direct driver of customer churn and support cost. Onboarding friction caused by manual steps across separate provisioning, KYC, and billing systems means some new subscribers wait days to get a working SIM while a competitor activates in minutes. Support agents spend time on plan change requests that could be automated. Porting errors send customers to competitors before the port-in even completes.
The underlying problem is almost always the same: subscriber management was never built as a unified system. SIM provisioning lives in one vendor platform, KYC in a third-party tool that stores results somewhere else, the billing system holds plan data, and the CRM holds contact records. None of these systems share state in real time. Every workflow that crosses a boundary requires a human to carry data from one system to the next.
Custom subscriber management software connects those workflows into a single data model. SIM provisioning triggers KYC initiation. KYC completion triggers billing account creation. Plan assignment propagates to network provisioning automatically. Port-in requests flow through porting orchestration without an agent coordinating between systems. The result is faster onboarding, fewer porting errors, lower support volume from plan change requests, and a subscriber record that is always consistent across provisioning, billing, and CRM.
What we build
SIM and eSIM provisioning
IMSI assignment from your assigned range with conflict detection and inventory tracking. HLR and HSS provisioning via MAP or Diameter to activate the subscriber on the core network with the correct service profile. Activation workflow that tracks each provisioning step -- SIM shipped, SIM inserted, network registration, service activation -- with automated retry on failure at each stage. eSIM profile management via SM-DP+ with QR code delivery to the subscriber and profile download confirmation. Wholesale SIM activation via your host MNO API with status mapping from their codes to your internal state model. Status dashboard showing every SIM in inventory, in transit, active, suspended, or decommissioned, with filter by batch, plan, and date range. The provisioning layer that eliminates the manual steps between a subscriber signing up and a SIM working on the network.
KYC and identity verification
Document upload via web and mobile with guided capture to improve image quality before submission. Automated document check via Onfido, Jumio, or your preferred provider -- identity document authenticity, face match against document photo, and liveness check to prevent spoofing. Sanctions and PEP screening against current watchlists with manual review queue for flagged cases. Age verification for age-restricted products using date of birth extracted from the identity document. KYC status stored against the subscriber record with the verification timestamp, document type used, and provider decision code. Re-verification workflow for expired documents or when a fraud signal is raised post-activation. Audit trail of every KYC decision with the supporting evidence retained for your regulatory compliance period.
Plan management
Plan assignment at activation with validation that the selected plan is available for the SIM type and network the subscriber is on. Mid-cycle upgrade and downgrade with pro-rata billing calculation sent to the billing system and immediate or scheduled effective date depending on plan rules. Add-on activation -- bolt-on data, roaming packages, international calling -- with entitlement tracking separate from the base plan allowance. Pooled plan management for business accounts sharing a single data or voice allowance across multiple SIMs, with per-SIM consumption tracking and pool exhaustion alerts. Suspension and reactivation with configurable rules for voluntary suspension, non-payment suspension, and fraud suspension, each with different service flag states sent to the network. Plan catalogue management in the admin interface so commercial teams can create and retire plans without involving engineering.
Number porting orchestration
Port-in request capture from the subscriber -- losing number, account details with the donor network, and preferred porting date. MNP database query to identify the donor network and validate that the number is eligible for porting. Donor notification via the industry clearing house with standardised message format for your market's porting regime. Porting date confirmation handling -- acceptance, rejection with reason code, and counter-proposal from the donor. Network cutover coordination on the confirmed porting date, triggering provisioning changes at the exact cutover time with rollback capability if the cutover fails. Porting failure handling with automated retry where the failure reason is retryable, and agent escalation queue for cases requiring manual intervention. Porting volume reporting showing port-in and port-out volumes by week, rejection rate by reason code, and average time from request to cutover.
Account lifecycle management
Prospect to active subscriber flow covering plan selection, identity verification, SIM provisioning, and billing account creation as a single coordinated workflow rather than separate steps across systems. Identity change handling for name changes and address updates with document verification where your policy requires it. Ownership transfer between individuals or from a personal account to a business account with the supporting verification steps. Deceased account process covering service suspension, final invoice generation, and account closure with appropriate document requirements. Voluntary churn workflow capturing the cancellation reason, applying any retention offer configured for that reason and customer segment, and processing the port-out or number release on the requested date. Involuntary churn triggered by payment failure after the dunning sequence completes -- suspension, final notice, and disconnection with number release back to the pool. Account reinstatement after suspension with payment confirmation from the billing system as the trigger.
BSS integration
Two-way integration with your billing system -- subscriber management pushes plan data, activation dates, and mid-cycle changes to billing, and billing pushes payment status, dunning flags, and suspension triggers back. Network provisioning system integration to send service profile changes, suspension flags, and plan entitlement updates, and to receive network registration events and SIM status confirmations. CRM integration to keep contact details, communication preferences, and interaction history consistent between subscriber management and the customer-facing team tools. Regulatory reporting feeds providing subscriber count by plan type, porting volumes, and churn metrics in the format required by your market regulator. Wholesale cost feed integration for MVNOs -- matching subscriber activations and plan assignments to host MNO cost records for margin tracking at the subscriber level.
Frequently asked questions
Subscriber management software is the operational core that tracks what each subscriber is entitled to and orchestrates the provisioning changes that deliver those entitlements on the network. A CRM manages customer relationships and communication -- it holds contact details, interaction history, and sales pipeline data, but it does not know whether a SIM is active on the HLR or what service flags are applied to it. A billing system rates usage and generates invoices -- it knows what a customer owes, but it relies on subscriber management to tell it what plan the customer is on and when that plan changes. Subscriber management sits between the two: it owns the authoritative plan record, drives provisioning changes when that record changes, and sends the plan data that billing needs to rate correctly. When these three systems are separate with manual data transfer between them, any workflow that touches all three -- onboarding, plan change, porting -- requires human coordination at each handoff. Subscriber management software replaces those handoffs with automated, event-driven integration.
eSIM provisioning uses a different technical path to physical SIM provisioning but needs to be managed within the same subscriber record and lifecycle. Physical SIM provisioning sends IMSI and service profile data to the HLR or HSS via MAP or Diameter. eSIM provisioning sends a profile download order to the SM-DP+ server, which generates an activation code -- usually delivered as a QR code -- that the subscriber scans on their device. The device then downloads the profile from the SM-DP+ directly. The subscriber management system tracks both paths: for physical SIM it monitors HLR provisioning status, for eSIM it monitors SM-DP+ profile download confirmation. Both paths converge on the same activated state in the subscriber record. Operators moving from physical-only to eSIM or running both in parallel need the system to handle both provisioning workflows, both inventory pools, and both status state machines within a single subscriber record without treating eSIM as a special case that requires separate tooling.
Number porting rules differ by market in ways that affect the orchestration logic: the clearing house used, the message formats, the timing rules, the rejection code set, and the cutover coordination approach. In the UK, porting uses the Syniverse PAM platform and follows Ofcom's porting regime timing. In the US, porting follows FCC rules with NPAC coordination and uses a different set of rejection reason codes. EU markets each have their own national porting body and timing rules under the European Electronic Communications Code. Building porting orchestration for a single market is straightforward. Building it for multiple markets requires the porting orchestration module to be market-aware -- each market gets its own clearing house integration, message format adapter, timing rule set, and rejection code mapping, all hanging off the same core porting workflow. We scope the number of markets and their regulatory requirements during discovery and build the orchestration layer to handle each market's rules correctly rather than approximating a single generic flow.
Cost depends on the scope of provisioning integrations, the number of plan types, the porting markets covered, and the BSS systems the platform needs to integrate with. A core subscriber management system covering SIM provisioning for a single host MNO, KYC via one identity provider, standard postpaid and prepaid plan management, single-market number porting, and billing system integration typically delivers in 14-16 weeks. A more complete platform adding eSIM provisioning, multi-market porting, pooled business plans, multi-BSS integration, and regulatory reporting typically runs 18-22 weeks. We give you a fixed cost before development starts, scoped against your actual provisioning environment and plan portfolio rather than a generic estimate. If you tell us your host MNO, the provisioning APIs they expose, your plan catalogue structure, and the porting markets you operate in, we can scope the right build for your situation.
Talk to us about your subscriber management project.
Tell us your current subscriber base size, the provisioning systems you connect to, and where manual steps in onboarding or plan changes create the most support load. We will scope the right platform.
