Insights and Strategies

Following on from our Genesys Playbook, we are now providing a NICE CXone version: The HRO Engine: NICE CXone Deployment Playbook. 1. The Core Architecture Pipeline The framework replaces manual sample polling with a continuous, server-less ingestion and evaluation pipeline: Ingestion: NICE CXone captures 100% of inbound and outbound interactions, including web messaging JSON recordings, while executing automated entity masking. Event Routing: Amazon EventBridge Router

The customer experience (CX) landscape in Australia and New Zealand (ANZ) is undergoing a major structural transformation. For years, the default corporate playbook was offshore outsourcing to developing markets. Today, that pendulum has swung decisively backward. Major domestic brands, including Telstra, Optus, Origin Energy and Westpac, have re-shored their core voice queues to reclaim operational control through onshore, captive in-house networks. With captive in-house o

In our modern contact centres, the standard approach to risk management is fundamentally flawed. Relying on manual human evaluations that sample a mere 2% of customer interactions creates a dangerous "85% Trap," where zero-tolerance regulatory and compliance errors are masked behind high, blended soft-skill scores. To transition customer operations into High-Reliability Organisations (HROs), systems capable of operating with zero-defect safety under intense volatility, we mus

In my previous article, we cut through the vendor marketing hype to define what true Agentic AI looks like in the contact centre. We established that moving from rigid decision trees to dynamic reasoning engines requires a robust 3 to 6 month runway built on clean data, standardised standard operating procedures (SOPs), and strict API execution guardrails. However, as organisations begin mapping out this operational runway, a much larger macro shift is unfolding. Recent data

For contact centre leaders, a consistent 85% aggregate score on monthly quality scorecards has traditionally been accepted as a marker of steady performance. In high-stakes environments however, this reliance on aggregate metrics represents a structural vulnerability. Traditional quality assurance frameworks rely on retrospective manual evaluation methodologies, typically sampling a statistically insignificant 2% of the total interaction population. This creates an operationa

The contact centre industry is currently navigating a massive wave of vendor re-branding. Walk through any enterprise technology expo or read any software press release and you will find the word "Agentic" attached to almost every legacy IVR system and basic chatbot on the market. For operations leaders focused on genuine efficiency and customer experience, this marketing noise makes it incredibly difficult to separate actual innovation from clever packaging. To successfully

How smaller, agile operations can eliminate guesswork and scale performance without six-figure software contracts. In the small to medium contact centre space (sub-150 seats), workforce management (WFM) is frequently a game of survival. While massive enterprise operations deploy dedicated data science teams and hyper-expensive software suites to balance their staffing, mid-market centres are forced to make a brutal choice: rely on basic, rigid spreadsheets, or manage schedule

If you are currently reviewing an upcoming customer experience (CX) or business process outsourcing (BPO) vendor renewal, you are likely being buried under an avalanche of a new corporate buzzword: Agentic AI. Every major platform and BPO provider is pitching a vision of the immediate future where autonomous, self-thinking AI "agents" dynamically navigate your legacy systems, make executive decisions on the fly, and resolve complex tier-1 customer issues entirely without huma

The contact centre industry is currently flooded with a commodity asset: the "prompt pack." Search any digital storefront or business forum, and you will find endless lists of generic text templates promising to magically optimise your operations. They offer vague, open-ended instructions designed to make AI "creative." But here is the hard truth that every operational leader eventually realises: Generic prompts fail in high-volume, regulated environments. When you ask a stan

Let’s be honest, for a long time, managing a contact centre was treated as a game of pure headcount. The operational playbook was simple: hire thousands of agents in low-cost regions, route voice calls to them, and manage the overhead. But as we navigate 2026, that manual playbook is officially obsolete. The customer experience (CX) sector has reached a massive technological and operational fork in the road. On one side, legacy service providers are managing millions of custo

Contact centre performance has always been measured through a small set of familiar metrics. These have been foundational for decades and have continued to remain the bedrock on how centres are managed, especially in moments of contact centre stress. At the centre of that model is one of the most common measures in service operations: Average Handling Time (AHT). AHT made sense in a world where the main challenge was volume. If people were handling more calls, faster handlin

Why the HRO Engine is the New Standard for Operational Resilience For more than 30 years, contact centre quality was measured through a small set of familiar metrics. At the centre of that model was the most common standard in the industry: The 85% Passing Grade. The 85% model made sense in a world of manual sampling and limited visibility. If a supervisor listened to three calls a month and the agent ticked most of the boxes, the operation was considered "safe." But the lega

AI governance is often discussed as if it lives in a separate world from the day-to-day operation of a business. In practice, it does not. Governance shows up in the moment a customer issue is handled, a recommendation is accepted, a decision is overridden, or an exception is escalated. That is why so many AI programs struggle not because the technology is weak, but because the role design around it is unclear. If people do not know what AI can do, what humans remain accounta

Most traditional position descriptions are built around tasks. They describe what a person does, what system they use, and what process they follow. That made sense in a world where humans handled most work manually and technology played a supporting role. AI changes that. In an AI-enabled operating model, routine tasks are increasingly handled by automation, copilots, chatbots and workflow tools. That means the human role is no longer defined primarily by task completion. It

For years, position descriptions were treated as administrative documents. They outlined: responsibilities, tasks, reporting lines, and required experience. In many organisations, they changed very little over time because the nature of work itself changed slowly. That is no longer the case. As AI becomes embedded into customer operations, contact centres and enterprise workflows, organisations are discovering that many existing position descriptions were designed for work th

In complex operations, there is an unspoken rule: if you aren't actively building a strong foundation, the system will slowly slide into chaos. In a high-volume contact centre, this breakdown doesn't happen overnight. It shows up in small, frustrating ways—a second of lag on an agent's desktop, a slight delay in multi-channel routing, or a growing gap between what your technology promises and what your team can actually deliver. For over 26 years, I have held senior leadershi