Skip to content

Hansen CCB Release 2026: What It Is, Who It’s For, and What’s New

Insights Hansen CCB Release 2026: What It Is, Who It’s For, and What’s New
Hansen News
Written By

Hansen News

Every year Hansen issues a new release for its Hansen CCB and we’ve just gone live with our latest upgrade. Here’s all you need to know about Hansen CCB and it’s new enhancements.

What is Hansen CCB?

Hansen CCB is a unified digital BSS customer care and billing (CCB) platform built for telecommunications and media companies. It brings product management, customer management, sales and fulfilment, revenue management, resource and provisioning management, and partner management together in a single solution.

Instead of running separate tools for billing, customer service, product catalogs, and partner settlement, operators run all of it on one platform with one data model. That means a change made in one place – a new pricing plan, a customer address update, a partner commission rule – is reflected everywhere else automatically.

Hansen CCB is configuration-driven, so operators can launch new products, pricing models, and offers without waiting on custom development. This is what lets communications and media businesses move at the speed of their market rather than the speed of their IT backlog, taking only days, not weeks to launch new offers.

Who is Hansen CCB For?

Hansen CCB is built for communications and media operators of all shapes, including:

  • Pay TV and legacy broadcast operators moving into multi-service offerings like OTT and broadband, while cutting operational cost and complexity
  • Broadband and fibre providers that need flexible pricing, bundling, and lifecycle management for product-based offerings
  • Mobile and MVNO operators running prepaid, postpaid, or hybrid charging models, including partner and network integrations
  • Multi-service operators delivering converged video, broadband, voice, and mobile offerings from a single customer and billing framework

Whether the goal is cutting costs on existing services or launching entirely new revenue streams, Hansen CCB is designed to scale with the business rather than get replaced by it.

Why Operators Choose Hansen CCB

  • Increase revenue. Flexible product modelling and bundling support recurring, usage-based, and event-driven charging models, so pricing strategy isn’t limited by the system underneath it.
  • Reduce operational cost. One platform replaces multiple billing and customer systems, cutting the overhead of maintaining and integrating disconnected tools.
  • Accelerate time-to-market. Products, pricing, and offers are introduced and changed through configuration, not custom code, so commercial teams aren’t stuck waiting on development cycles.
  • Improve customer experience. A unified view of customer, product, and billing data means every interaction – CSR, self-service, or AI-powered – has the full picture.
  • Scale without complexity. Multiple brands, countries, currencies, and business models (B2B, B2B2C, MVNO, wholesale, reseller) run on the same platform without duplicating systems or logic.
  • AI-enabled engagement. HansenCCB integrates with Hansen’s AI-powered Virtual Agent, which draws on the platform’s unified customer, product, and billing data to support live CSR interactions, handle direct customer contact, and power self-service – including outage-related queries.

What’s New in Hansen CCB 2026

The Hansen CCB release focuses on four areas: broadband capability, cloud optimization, core tech stack upgrades, and faster time to value.

Broadband Accelerator

Hansen CCB rounds out broadband support with a dedicated set of enhancements:

  • Fixed broadband endpoint support – network components like NIDs and ONTs can now be identified as endpoint devices linked to the address itself (not the customer), which matters for Fibre to the Home deployments where devices belong to the location, not the account.
  • Homes Passed status tracking – a standard field (Connected, Ready to Connect, Unable to Connect, Pending Future Connection) now governs which products and offers are available at a given address, tied directly into the existing SAL (Service Availability List) check process.
  • Improved Customer Move flow – a new Manage Customer Move process replaces the old Service Address Change, handling agreement impacts, service availability checks, reversals, prorating, and scheduled future moves in one flow.
  • Invoice Designer & Bill Presentment – a new reporting engine (built on FastReport) generates on-demand and bulk invoice PDFs, with a visual drag-and-drop template designer, TM Forum–aligned JSON export, and API access to retrieve invoice PDFs directly.
  • Sample Selfcare & Onboarding – sample self-service and customer onboarding flows built on the Flutter framework, giving implementation teams a working starting point.
Cloud Optimisation
  • Containerised CCB modules (ASM, BSM, ISM, WSM) with Kubernetes support, deployable on AWS EKS with Terraform-managed infrastructure and Argo CD for configuration and state.
  • Improved queue depth metric management – PostgreSQL and Kafka environments now publish queue depth metrics to the operational database, matching existing Oracle behaviour.
Tech Stack Upgrades
  • Kafka 4.0 (KRaft mode, no separate Zookeeper cluster required) and Confluent 7.5
  • Redis 7.4 and Valkey 9.0.0
  • Windows Server 2025 support (Windows Server 2019 support has ended)
  • Dynatrace observability support
  • Broader security improvements, including business-unit-restricted username visibility across notes, contacts, and associates
Improve Time to Value
  • A new data migration framework built on AWS Glue, with standard target data formats for uploading and testing migrated data – a Hansen-supported process where the customer owns source data extraction.

The Bottom Line

This Hansen CCB release is about giving operators more control with less overhead: better broadband and fiber support, a modern invoice generation engine, a cloud-native deployment path, an updated technology foundation, and a faster path to getting live. For teams evaluating a Customer Care and Billing platform for broadband, mobile, or converged services, this release is a meaningful step toward simpler, faster, more flexible operations.

 

Frequently Asked Questions

Hansen CCB is a Customer Care and Billing platform used by telecommunications and media operators to manage products, customers, billing, and partner relationships from a single system, covering everything from product catalog and pricing to invoicing, payments, and customer support.

Pay TV and broadcast operators, broadband and fiber providers, mobile and MVNO operators, and multi-service (converged) operators use Hansen CCB to run billing and customer operations across one or multiple service lines.

Yes. Hansen CCB supports cloud (SaaS), on-premises, and hybrid deployment models. The 2026 release adds containerised modules with Kubernetes support for deployment on AWS EKS.

Hansen CCB is configuration-driven, meaning products, pricing, and offers can be created and changed through configuration rather than custom software development, reducing dependency on IT teams for commercial changes.

The 2026 release adds broadband endpoint and Homes Passed status support, a new Customer Move flow, a new Invoice Designer with on-demand PDF generation, Kubernetes-based cloud deployment, upgrades to Kafka, Redis, and Windows Server, and a new AWS Glue–based data migration framework.

Yes. Hansen CCB integrates with Hansen’s Virtual Agent, which uses the platform’s unified customer, product, and billing data to support customer service representatives, handle direct customer interactions, and power self-service channels.

Yes. Hansen CCB supports multi-company, multi-tenant, multi-country, and multi-currency operations, along with B2B, B2B2C, MVNO, distributor, and reseller business models within a single deployment.

What does “modernise with precision” mean for Tier-1 telecom operators?

“Modernise with precision” describes a low-risk, targeted approach to BSS/OSS modernisation where operators upgrade only the parts of their digital stack that create the greatest impact. Instead of embarking on high-risk, multi-year full-stack replacements, Tier-1 telcos selectively introduce cloud-native BSS/OSS, API-driven telecom architecture, AI-ready data layers, and TMF-compliant BSS components. 

This modular strategy reduces cost and disruption, allowing operators to strengthen areas such as product agility, order orchestration, customer experience, and operational efficiency while maintaining stability in core environments. It aligns directly with TM Forum’s Open Digital Architecture (ODA), which encourages a composable, interoperable, future-proof approach to telco transformation.  

Why is time-to-market so important for telecom monetisation today?

Telecom monetisation increasingly depends on the ability to respond quickly to new commercial opportunities – from enterprise IoT solutions and digital services to 5G monetisation, wholesale partnerships, and B2B vertical offerings. In this environment, operators that can design, package, and activate new services in days rather than months gain a clear revenue advantage. 

Legacy catalogues, rigid product hierarchies, and tightly coupled BSS architectures make rapid innovation difficult. Modern operators therefore prioritise catalog-driven architecture, agile/composable BSS, and cloud-native BSS capabilities to give business teams control over offer creation without relying on long IT delivery cycles. Faster launch cycles = faster monetisation. 

What is slowing down product launch cycles for many telcos?

The primary obstacles are deeply entrenched in legacy architecture: hard-coded product models, outdated catalogues, nonstandard integrations, and heavy IT dependencies. These constraints slow down even minor product changes, creating friction between commercial teams and IT. 

Modern telcos are replacing these bottlenecks with TMF-compliant BSS, cloud-native catalogues, API-driven BSS integrated via TMF Open APIs, and low/no-code configuration tools. These solutions allow product owners to create and test offers independently, ensuring the Digital BSS backbone supports true agility. 

How can telecom operators reduce order fallout and manual intervention?

Order fallout typically stems from fragmented systems, inconsistent data models, and brittle custom integrations across BSS/OSS chains. When orchestration spans numerous legacy systems, even small discrepancies can cause orders to fail. 

Operators can dramatically reduce fallout rates by adopting zero-touch service orchestration, modern order management modernisation, end-to-end automation, and a unified data model across their Digital OSS and Digital BSS layers. Cloud-native telecom systems and order orchestration for telecom remove reliance on manual rework, minimise delays, and improve service accuracy – all essential to delivering predictable customer experiences. 

Why is accuracy so important for B2B and wholesale customer experience?

For enterprise and wholesale customers, trust is built on precision. A single misquote, incorrect configuration, or missed activation can lead to delays, SLA breaches, revenue disputes, and strained relationships. These segments rely on highly controlled, predictable fulfilment processes – particularly as operators expand into 5G edge services, network slicing, managed security, and outcome-based contracts. 

Improving accuracy requires strengthening the underlying architecture – through modern CPQ for telecom, clean data models, cloud-native BSS/OSS, and robust API-driven telecom architecture. When quoting, ordering, provisioning, and billing are accurate, customer satisfaction increases naturally. 

How does cloud, AI, and API-driven architecture support telecom modernisation?

Cloud-native platforms provide the scalability, flexibility, and deployment speed needed to support modern telecom services. AI introduces intelligence into operations, enabling predictive analytics, anomaly detection, and proactive assurance. APIs – especially TMF Open APIs – ensure new components integrate cleanly with legacy systems. 

Together, AI-powered BSS/OSS, cloud-native architecture, and API-driven integration create a digital foundation that supports continuous innovation, reduces technical debt, and enables operators to deliver new services more efficiently. This trio is central to future-proofing the telco stack. 

What is TM Forum’s Open Digital Architecture (ODA) and why does it matter?

TM Forum’s Open Digital Architecture (ODA) is an industry-standard framework designed to help telcos simplify, modularise, and modernise their BSS/OSS environments. ODA promotes interoperability, composability, and openness so operators can integrate new capabilities without heavy customisation or vendor lock-in. 

For Tier-1 operators, ODA serves as a blueprint for transitioning from monolithic legacy stacks to cloud-native, API-driven, modular BSS/OSS infrastructure. By adopting ODA-aligned solutions, operators speed up integration, lower deployment risk, and reduce long-term operational cost. 

How is Hansen involved in TM Forum and ODA?

Hansen aligns its architecture directly to TM Forum’s ODA principles and has contributed to the development of one of TM Forum’s recognised industry standards. This reinforces a commitment not just to following best practices, but to shaping them. 

Hansen’s portfolio of cloud-native, AI-powered, API-driven Digital BSS/OSS modules is built on TMF Open APIs and composable design principles. This ensures seamless interoperability in multivendor environments and helps operators modernise safely and incrementally. 

Can operators modernise their BSS/OSS without a full-stack replacement?

Yes – and in fact, most Tier-1 operators now prefer incremental transformation. Full-stack replacement is high risk, slow, and expensive. By contrast, modular modernisation allows operators to introduce new BSS/OSS capabilities – catalogues, orchestration layers, charging engines, customer management, monetisation components – without destabilising the existing ecosystem. 

This approach reduces risk, accelerates value, and aligns with ODA’s principles of composability and openness. Operators can modernise at their own pace while still maintaining service continuity. 

How does modular modernisation reduce risk?

Modular transformation focuses on improving specific parts of the architecture – such as product agility, order accuracy, unified data, or 5G monetisation – without changing everything at once. Each module is integrated, tested, and scaled independently, which reduces disruption and improves predictability. 

It also allows operators to retire legacy systems gradually, reducing technical debt over time while still realising near-term efficiency and revenue gains. This is why agile/composable BSS is now the preferred model for Tier-1 telecom transformation. 

What operational improvements can telcos expect from a unified data model?

A unified, AI-ready data model brings real-time visibility across commercial and operational processes, enabling faster decision-making and more reliable service execution. It also allows operators to detect issues earlier, automate root cause analysis, and reduce order fallout. 

This consistent data foundation is essential for AI-powered BSS/OSS, predictive assurance, next-best-action recommendations, and advanced analytics. It ultimately improves operational efficiency, accuracy, and customer experience – three core pillars of modern telecom performance. 

Why is Customer Experience (CX) tightly linked to operational excellence? 

Most customer experience problems – delays, incorrect orders, billing errors, missed SLAs – originate from inefficiencies within the internal BSS/OSS engine. When operators modernise their Digital BSS/OSS processes, eliminate manual workarounds, and ensure accurate orchestration and service activation, the customer experience improves naturally. 

This is particularly true for enterprise and wholesale customers, where CX is defined by precision, predictability, and contract performance. Improving CX requires improving the processes beneath it. 

How do Hansen’s solutions fit into a Tier-1 telco transformation strategy?

Hansen provides cloud-native, API-driven, TMF-compliant, AI-powered Digital BSS/OSS modules that integrate smoothly into hybrid and legacy environments. Operators can use them to strengthen catalog agility, automate order flows, unify data, enhance monetisation, or improve service reliability – without needing to replace their entire BSS/OSS stack. 

This flexibility supports transformation at the operator’s own pace, aligned to business priorities, regulatory requirements, and commercial objectives. 

What benefits can operators expect from a layered or hybrid modernisation approach?

A layered or hybrid approach allows operators to combine existing systems with cloud-native components, enabling transformation without disruption. Key benefits include: 

  • Faster time-to-market for new offers 
  • Improved order accuracy and reduced fallout 
  • Lower cost-to-serve through automation 
  • Stronger customer experience 
  • Gradual reduction of technical debt 
  • Alignment with ODA and modular architecture principles 

This approach balances stability with innovation – ideal for Tier-1 operators. 

How do industry standards such as ODA accelerate telecom digital transformation?

Industry standards like TM Forum ODA and TMF Open APIs reduce integration complexity, promote interoperability, and give operators a trusted blueprint for modernisation. They ensure that new BSS/OSS components can plug into existing environments without custom engineering. 

By reducing dependence on bespoke integrations and enabling modular deployment, standards significantly lower long-term cost and accelerate transformation across the business. They also future proof the architecture for new technologies, including AI, automation, and 5G service innovation. 

1. What does “modernise with precision” mean for Tier-1 telecom operators?

“Modernise with precision” describes a low-risk, targeted approach to BSS/OSS modernisation where operators upgrade only the parts of their digital stack that create the greatest impact. Instead of embarking on high-risk, multi-year full-stack replacements, Tier-1 telcos selectively introduce cloud-native BSS/OSS, API-driven telecom architecture, AI-ready data layers, and TMF-compliant BSS components.
This modular strategy reduces cost and disruption, allowing operators to strengthen areas such as product agility, order orchestration, customer experience, and operational efficiency while maintaining stability in core environments. It aligns directly with TM Forum’s Open Digital Architecture (ODA), which encourages a composable, interoperable, future-proof approach to telco transformation.

2. Why is time-to-market so important for telecom monetisation today?

Telecom monetisation increasingly depends on the ability to respond quickly to new commercial opportunities – from enterprise IoT solutions and digital services to 5G monetisation, wholesale partnerships, and B2B vertical offerings. In this environment, operators that can design, package, and activate new services in days rather than months gain a clear revenue advantage.
Legacy catalogues, rigid product hierarchies, and tightly coupled BSS architectures make rapid innovation difficult. Modern operators therefore prioritise catalog-driven architecture, agile/composable BSS, and cloud-native BSS capabilities to give business teams control over offer creation without relying on long IT delivery cycles. Faster launch cycles = faster monetisation.

 

3. What is slowing down product launch cycles for many telcos?

The primary obstacles are deeply entrenched in legacy architecture: hard-coded product models, outdated catalogues, nonstandard integrations, and heavy IT dependencies. These constraints slow down even minor product changes, creating friction between commercial teams and IT.
Modern telcos are replacing these bottlenecks with TMF-compliant BSS, cloud-native catalogues, API-driven BSS integrated via TMF Open APIs, and low/no-code configuration tools. These solutions allow product owners to create and test offers independently, ensuring the Digital BSS backbone supports true agility.

4. How can telecom operators reduce order fallout and manual intervention?

Order fallout typically stems from fragmented systems, inconsistent data models, and brittle custom integrations across BSS/OSS chains. When orchestration spans numerous legacy systems, even small discrepancies can cause orders to fail.
Operators can dramatically reduce fallout rates by adopting zero-touch service orchestration, modern order management modernisation, end-to-end automation, and a unified data model across their Digital OSS and Digital BSS layers. Cloud-native telecom systems and order orchestration for telecom remove reliance on manual rework, minimise delays, and improve service accuracy – all essential to delivering predictable customer experiences.

5. Why is accuracy so important for B2B and wholesale customer experience?

For enterprise and wholesale customers, trust is built on precision. A single misquote, incorrect configuration, or missed activation can lead to delays, SLA breaches, revenue disputes, and strained relationships. These segments rely on highly controlled, predictable fulfilment processes – particularly as operators expand into 5G edge services, network slicing, managed security, and outcome-based contracts.
Improving accuracy requires strengthening the underlying architecture – through modern CPQ for telecom, clean data models, cloud-native BSS/OSS, and robust API-driven telecom architecture. When quoting, ordering, provisioning, and billing are accurate, customer satisfaction increases naturally.

6. How does cloud, AI, and API-driven architecture support telecom modernisation?

Cloud-native platforms provide the scalability, flexibility, and deployment speed needed to support modern telecom services. AI introduces intelligence into operations, enabling predictive analytics, anomaly detection, and proactive assurance. APIs – especially TMF Open APIs – ensure new components integrate cleanly with legacy systems.
Together, AI-powered BSS/OSS, cloud-native architecture, and API-driven integration create a digital foundation that supports continuous innovation, reduces technical debt, and enables operators to deliver new services more efficiently. This trio is central to future-proofing the telco stack.

7. What is TM Forum’s Open Digital Architecture (ODA) and why does it matter?

TM Forum’s Open Digital Architecture (ODA) is an industry-standard framework designed to help telcos simplify, modularise, and modernise their BSS/OSS environments. ODA promotes interoperability, composability, and openness so operators can integrate new capabilities without heavy customisation or vendor lock-in.
For Tier-1 operators, ODA serves as a blueprint for transitioning from monolithic legacy stacks to cloud-native, API-driven, modular BSS/OSS infrastructure. By adopting ODA-aligned solutions, operators speed up integration, lower deployment risk, and reduce long-term operational cost.

8. How is Hansen involved in TM Forum and ODA?

Hansen aligns its architecture directly to TM Forum’s ODA principles and has contributed to the development of one of TM Forum’s recognised industry standards. This reinforces a commitment not just to following best practices, but to shaping them.
Hansen’s portfolio of cloud-native, AI-powered, API-driven Digital BSS/OSS modules is built on TMF Open APIs and composable design principles. This ensures seamless interoperability in multivendor environments and helps operators modernise safely and incrementally.

9. Can operators modernise their BSS/OSS without a full-stack replacement?

Yes – and in fact, most Tier-1 operators now prefer incremental transformation. Full-stack replacement is high risk, slow, and expensive. By contrast, modular modernisation allows operators to introduce new BSS/OSS capabilities – catalogues, orchestration layers, charging engines, customer management, monetisation components – without destabilising the existing ecosystem.
This approach reduces risk, accelerates value, and aligns with ODA’s principles of composability and openness. Operators can modernise at their own pace while still maintaining service continuity.

10. How does modular modernisation reduce risk?

Modular transformation focuses on improving specific parts of the architecture – such as product agility, order accuracy, unified data, or 5G monetisation – without changing everything at once. Each module is integrated, tested, and scaled independently, which reduces disruption and improves predictability.
It also allows operators to retire legacy systems gradually, reducing technical debt over time while still realising near-term efficiency and revenue gains. This is why agile/composable BSS is now the preferred model for Tier-1 telecom transformation.

11. What operational improvements can telcos expect from a unified data model?

A unified, AI-ready data model brings real-time visibility across commercial and operational processes, enabling faster decision-making and more reliable service execution. It also allows operators to detect issues earlier, automate root cause analysis, and reduce order fallout.
This consistent data foundation is essential for AI-powered BSS/OSS, predictive assurance, next-best-action recommendations, and advanced analytics. It ultimately improves operational efficiency, accuracy, and customer experience – three core pillars of modern telecom performance.

12. Why is Customer Experience (CX) tightly linked to operational excellence?

Most customer experience problems – delays, incorrect orders, billing errors, missed SLAs – originate from inefficiencies within the internal BSS/OSS engine. When operators modernise their Digital BSS/OSS processes, eliminate manual workarounds, and ensure accurate orchestration and service activation, the customer experience improves naturally.
This is particularly true for enterprise and wholesale customers, where CX is defined by precision, predictability, and contract performance. Improving CX requires improving the processes beneath it.

13. How do Hansen’s solutions fit into a Tier-1 telco transformation strategy?

Hansen provides cloud-native, API-driven, TMF-compliant, AI-powered Digital BSS/OSS modules that integrate smoothly into hybrid and legacy environments. Operators can use them to strengthen catalog agility, automate order flows, unify data, enhance monetisation, or improve service reliability – without needing to replace their entire BSS/OSS stack.
This flexibility supports transformation at the operator’s own pace, aligned to business priorities, regulatory requirements, and commercial objectives.

14. What benefits can operators expect from a layered or hybrid modernisation approach?

A layered or hybrid approach allows operators to combine existing systems with cloud-native components, enabling transformation without disruption. Key benefits include:
• Faster time-to-market for new offers
• Improved order accuracy and reduced fallout
• Lower cost-to-serve through automation
• Stronger customer experience
• Gradual reduction of technical debt
• Alignment with ODA and modular architecture principles
This approach balances stability with innovation – ideal for Tier-1 operators.

15. How do industry standards such as ODA accelerate telecom digital transformation?

Industry standards like TM Forum ODA and TMF Open APIs reduce integration complexity, promote interoperability, and give operators a trusted blueprint for modernisation. They ensure that new BSS/OSS components can plug into existing environments without custom engineering.
By reducing dependence on bespoke integrations and enabling modular deployment, standards significantly lower long-term cost and accelerate transformation across the business. They also future proof the architecture for new technologies, including AI, automation, and 5G service innovation.