Last verified with: 10.8.6.0
Overview #
Entitlements define what usage, capacity, or service allowance a customer is included to consume as part of an offer.
In the platform, Entitlements are modeled primarily through buckets. That means the allowance is not just described conceptually. It is operationalized in billing with clear rules for what is included, how much remains, when it resets, whether unused amounts roll forward, how shared allowances work, and what happens when the customer exceeds the included amount.
This gives businesses a structured way to turn commercial promises into enforceable billing behavior.
What They Are #
At a business level, an Entitlement is the amount of usage or service value a customer is allowed to consume under an agreement before additional charging rules apply.
Examples include:
- included data,
- included minutes,
- included transactions,
- included messages,
- pooled usage across a group of services,
- or dynamically calculated allowances tied to another usage metric.
In simple terms, an Entitlement allows a business to say:
“This customer receives this amount of included value or usage, under these conditions, before overage or the next pricing rule applies.”
How They Work #
The platform uses buckets to create the entitlement structure.
From a business perspective, the model is straightforward:
- A bucket is configured to represent the included allowance.
- Base bucket settings define what kind of usage the Entitlement applies to, such as data, time, count, or other supported usage classes.
- The bucket is attached to a service or used as part of a shared plan.
- The bucket can be configured as one-time, recurring, or recurring with rollover.
- One or more tiers can be added to define how the Entitlement behaves as usage is consumed.
- Usage is applied against the bucket during rating and billing.
- The platform tracks remaining allowance, consumed allowance, and any transition into overage or next-tier behavior.
This turns included usage from a static catalog description into an active billing control structure.
Why Buckets Matter For Entitlements #
Buckets are what make Entitlements operational.
Without a bucket structure, an Entitlement is just a promise in a product definition. With buckets, that promise becomes measurable and enforceable.
Buckets make it possible to define:
- what usage qualifies for the allowance,
- how much is included,
- when the allowance starts and ends,
- whether it replenishes,
- whether unused amounts roll over,
- whether multiple users or services can share it,
- and how charging changes once the allowance is exhausted.
That is why buckets are such an important part of Entitlement design. They provide the control model behind the commercial offer.
Business Benefits #
Entitlements deliver value in several important ways:
- Clear included-value offers. Businesses can define exactly what is included in a service or package.
- Better control over overage behavior. Once the Entitlement is exhausted, the next pricing rule can be applied consistently.
- Support for multiple allowance models. Entitlements can be one-time, recurring, rolling, shared, or dynamically calculated.
- More flexible product design. Teams can build simple or sophisticated included-usage offers without custom billing workarounds.
- Better customer transparency. The customer can understand what is included, what has been consumed, and when additional charges begin.
- Stronger monetization of expansion. Businesses can create smooth transitions from included usage into higher tiers, flat charges, or overage pricing.
Entitlement Structures #
The platform supports several different ways to structure Entitlements.
Fixed Entitlements #
A fixed Entitlement provides a defined allowance that does not change unless the product configuration changes.
Examples:
- 100 GB included each month,
- 10,000 transactions included,
- 500 minutes included,
- or a one-time included implementation allowance.
Benefit:
- Clear and easy for customers to understand.
- Straightforward to price and manage.
- Well suited to standard package offers.
Recurring Entitlements #
A recurring Entitlement replenishes on a defined schedule, such as monthly or yearly.
Benefit:
- Supports subscription-style included usage.
- Keeps the allowance aligned to the recurring commercial period.
- Creates a predictable model for both billing and customer expectations.
Rollover Entitlements #
A recurring Entitlement can also be configured so unused value rolls into the next cycle.
Benefit:
- Creates a more customer-friendly experience.
- Differentiates premium offers from basic ones.
- Helps reduce waste perception for customers with variable consumption patterns.
Shared Entitlements #
Entitlements can also be pooled across multiple participating services, packages, devices, or users through shared-plan structures.
Benefit:
- Supports family, enterprise, or pooled commercial models.
- Lets multiple participants consume from one common allowance.
- Reduces the need to assign rigid usage limits to each individual line or service.
Dynamic Entitlements #
Some Entitlements are not fixed in advance, but are calculated from another usage metric.
Examples:
- bandwidth consumed determines included requests,
- one usage class creates free allocation in another,
- or account-level consumption drives a derived allowance for a related service.
Benefit:
- Supports modern usage-based product models.
- Aligns included value to actual customer scale or activity.
- Enables more sophisticated platform and infrastructure pricing strategies.
Tiering Options Within Entitlements #
One of the most important strengths of the bucket model is that Entitlements can include tier behavior.
That means the platform does not just decide whether the customer is inside or outside the allowance. It can also define how pricing changes as the customer moves through different levels of consumption.
Single-Tier Included Usage #
The simplest model is one included allowance with one overage rule after it is consumed.
Benefit:
- Easy to explain and implement.
- Works well for standard subscription offers.
- Creates a clean entry point into pay-as-you-grow pricing.
Multi-Tier Entitlements #
An Entitlement can include multiple tiers, each with its own threshold and behavior.
This allows the business to structure offers where different levels of consumption trigger different charging outcomes.
Benefit:
- Supports more granular pricing.
- Creates smoother expansion paths.
- Makes it possible to align commercial value with customer growth.
Flat Charges On Tier Entry #
A tier can apply a flat charge when the customer enters that tier.
Benefit:
- Supports step-based commercial models.
- Useful for threshold-driven charges or bundled increments.
- Gives the business more control over how usage progression is monetized.
Infinite Or Repeating Last Tier #
The last tier can be configured to continue repeating instead of forcing an immediate handoff to a separate overage model.
Benefit:
- Supports repeating entitlement blocks.
- Useful for packaged expansion models.
- Creates a predictable step-up structure beyond the initial allowance.
Overage After Entitlement Exhaustion #
When the included Entitlement is consumed, the platform can use an overage rate plan to continue billing usage beyond the allowance.
Benefit:
- Creates a clean transition from included to chargeable usage.
- Protects revenue once the customer exceeds the included amount.
- Supports scalable usage growth without changing the underlying service structure.
Telecom Examples #
Monthly Included Data Allowance #
A telecom provider may include a defined amount of monthly data in a service package, with overage pricing once the Entitlement is used.
Benefit:
- Creates a familiar included-usage plan.
- Lets the provider clearly separate included and overage consumption.
- Supports simple subscription plus usage models.
Shared Usage Plan Across Multiple Lines #
A provider may offer one common allowance that multiple lines, devices, or services consume together.
Benefit:
- Supports family and enterprise pooling scenarios.
- Makes the offer more flexible for the customer.
- Improves commercial efficiency compared with rigid per-line entitlements.
Tiered Messaging Or Airtime Bundle #
A telecom offer may include one level of usage, then step into additional tiers or repeating blocks as the customer consumes more.
Benefit:
- Supports more nuanced monetization than a simple allowance cutoff.
- Creates smoother scale-based pricing.
- Helps align cost recovery to real usage growth.
SaaS Examples #
Included Transaction Or API Call Allowance #
A SaaS provider may include a monthly quantity of transactions, API calls, or processed events in the subscription.
Benefit:
- Supports standard platform packaging.
- Makes entry-level offers more attractive.
- Provides a clean foundation for usage expansion pricing.
Shared Entitlement Across Teams Or Environments #
A software business may allow several users, environments, or connected services to consume from one pooled allowance.
Benefit:
- Supports enterprise account structures.
- Makes the commercial model more flexible.
- Reduces friction when usage shifts between teams or workloads.
Dynamic Entitlement Based On Another Usage Metric #
A SaaS or infrastructure provider may want one kind of usage to drive the amount of included value in another category.
Benefit:
- Supports cloud-style or platform-style commercial models.
- Creates a stronger connection between customer scale and included value.
- Enables sophisticated bundled pricing without manual adjustment.
Why Customers Value This Capability #
Entitlements are especially valuable for organizations that:
- include usage as part of a subscription or package,
- need flexible allowance structures,
- want shared or pooled included value,
- need more than a simple on/off overage model,
- or want to support dynamic included-value relationships between services.
In those environments, the challenge is not just defining how something is priced. The challenge is defining what the customer is allowed to consume before a different charging rule should apply.
That is where buckets add value. They give the business a practical way to create, track, and enforce Entitlements, while also supporting the tiering and expansion logic that modern usage-based offers require.