v2.0

GoRules Version 2 is here - redesigned, now with managed cloud.GoRules Version 2 is here!

Watch the launch videoWatch
gorules
Book a demoGet started

MVNO Partner Enablement

Automated rules engine that determines service access, network resources, and pricing tiers for mobile virtual network operators based on partnership metrics.

Solution

This MVNO partner management solution streamlines telecom wholesale relationships by dynamically applying business rules to virtual operators. The system evaluates each partner's profile - including type, tenure, and subscriber base - to automatically determine appropriate service access levels, from basic to full service tiers.

Network resource allocation is precisely tailored to each MVNO's service level, with specific provisions for data capacity, voice minutes, SMS volumes, and API capabilities. The solution also implements a tiered pricing structure that accounts for both service level and market scale, determining revenue sharing percentages and granular usage rates for data and voice services. This creates a scalable framework that grows with MVNOs while ensuring profitable, sustainable partnerships for the host carrier.

How it works

The decision system evaluates MVNO partners through three interconnected rule components:

  1. Partner Service Access: Evaluates the MVNO's type (premium, standard, startup), age, and subscriber count to determine appropriate service access level and bandwidth priority.

  2. Network Resource Allocation: Based on the assigned service level, allocates specific network resources including data capacity (GB), voice minutes, SMS count, and appropriate API access level.

  3. Partner Pricing: Combines service level and subscriber count to establish pricing tier, revenue sharing percentage, and unit costs for data and voice services.

The system maintains full data transparency throughout the decision process, ensuring both host carriers and MVNOs understand service provisioning and cost structures.

Where teams use it

  • Telecom wholesale partnership management
  • MVNO onboarding and service provisioning
  • Dynamic resource allocation for virtual operators
  • Revenue share and pricing tier automation
  • Scalable service level management
  • Telecom partner lifecycle management

Inside the decision model

MVNO Partner Enablement ships as a JDM decision graph with 4 nodes, 3 decision tables and 13 rules. Download it, load it into GoRules, and run it as-is on Zen Engine.

Decision graph4 nodes · read-only
input requesttable partnerServiceAccesstable networkResourceAllocationtable partnerPricing
01

Request

input

A single partner object carries everything the rules need: type, ageInMonths, and subscriberCount determine service access and pricing, while id, name, region, and businessModel travel through as account metadata.

Sample requestJSON 
{
  "partner": {
    "id": "mvno-123",
    "name": "TechMobile",
    "type": "premium",
    "ageInMonths": 36,
    "subscriberCount": 120000,
    "region": "Northeast",
    "businessModel": "business-focused"
  }
}
02

Partner Service Access

table

Access levels come from crossing partner.type with tenure and scale under a first hit policy. A 'premium' MVNO older than 24 months with more than 100000 subscribers earns 'full' serviceAccessLevel and 'high' bandwidthPriority; a premium partner with only > 50000 subscribers drops to 'enhanced'. 'standard' partners need > 12 months and > 25000 subscribers for the 'standard' level, otherwise they share the 'basic'/'low' row with every 'startup'.

Graduating wholesale access on tenure and subscriber count is normal host-carrier practice: a virtual operator only earns priority on shared radio capacity once its traffic is predictable and its business proven, and startups begin at basic access because overcommitting bandwidth to an unproven brand risks the host's own retail quality. The thresholds themselves are commercial checkpoints, not industry constants.

Decision tablefirst hit policy
Partner Typepartner.typePartner Age (months)partner.ageInMonthsSubscriber Countpartner.subscriberCountService Access Levelconfig.serviceAccessLevelBandwidth Priorityconfig.bandwidthPriority
'premium'> 24> 100000'full''high'
'premium'-> 50000'enhanced''medium'
'standard'> 12> 25000'standard''medium'
'standard'--'basic''low'
'startup'--'basic''low'
03

Network Resource Allocation

table

Quota packages follow mechanically from config.serviceAccessLevel: 'full' unlocks 5000 GB of data, 1000000 voice minutes, 2000000 SMS, and 'advanced' API access; 'enhanced' halves that to 2500 GB and 500000 minutes; 'standard' gets 1000 GB with 'intermediate' APIs, and 'basic' bottoms out at 500 GB, 100000 minutes, and 'basic' API access.

Keeping the resource grid keyed on the access level alone, rather than re-testing partner attributes, means the earlier table is the single place where eligibility is decided and this one stays a pure capacity catalog. The roughly 2x steps between rows give the host carrier a clean upgrade path to sell, and tiered API access mirrors how wholesale platforms gate provisioning and reporting endpoints by contract level.

Decision tablefirst hit policy
Service Access Levelconfig.serviceAccessLevelData Allocation (GB)resources.dataAllocationGBVoice Minutesresources.voiceMinutesSMS Countresources.smsCountAPI Access Levelresources.apiAccessLevel
'full'500010000002000000'advanced'
'enhanced'25005000001000000'intermediate'
'standard'1000250000500000'intermediate'
'basic'500100000200000'basic'
04

Partner Pricing

table

Wholesale rates improve with scale: 'full' access with > 100000 subscribers lands in 'tier1' with a 0.85 revenueShareFactor and the lowest unit costs, 0.004 per MB and 0.002 per minute. 'enhanced' with > 50000 gets 'tier2' at 0.88, 'standard' with > 10000 gets 'tier3' at 0.9, and everything else defaults to 'tier4', where the MVNO keeps 0.95 of revenue but pays the highest rates, 0.008 and 0.004.

The inverse relationship in this card, bigger partners keep less of their revenue but buy capacity cheaper per unit, is a deliberate structure: at tier1 volume the host monetizes through share of a large base, while tier4 pricing lets small entrants keep margin on thin revenue at the cost of steeper unit rates. Volume-banded data and voice pricing is the standard shape of MVNO wholesale agreements, though these particular rates are business choices.

Decision tablefirst hit policy
Service Levelconfig.serviceAccessLevelSubscriber Countpartner.subscriberCountPricing Tierpricing.tierRevenue Sharepricing.revenueShareFactorData Cost Per MBpricing.dataRatePerMBVoice Cost Per Minpricing.voiceRatePerMinute
'full'> 100000'tier1'0.850.0040.002
'enhanced'> 50000'tier2'0.880.0050.003
'standard'> 10000'tier3'0.90.0060.003
--'tier4'0.950.0080.004

Other Telco templates

View all templates
Telco

Dynamic Tariff Engine

Rule-based pricing system for telecommunication services that automatically applies discounts based on user profiles, time periods, and location types.

Telco

Regional Compliance Manager

Automated system that applies region-specific data privacy rules for telecommunications services across EU, US, UK, Canada, and Australia.

Telco

Customer Eligibility Engine

Intelligent system that analyzes customer data to determine service upgrades, loyalty rewards, and premium features based on usage patterns and account history.

Make this template
your own.

Load MVNO Partner Enablement into GoRules, adjust the rules to your policy, and ship it behind your own API.

Get started Book a demo