Kraken Autonomous Agents combines Sierra\u2019s conversational AI with the Kraken utility platform\u2019s customer, billing, meter, tariff, and workflow context. For shortlisted utilities, the decision rests on whether that generative AI service can be contracted, configured, governed, phased, stabilized, and measured without weakening customer protection or obscuring responsibility.<\/p>\n
Autonomous agents<\/a> are making their way into every contact center, even the more complicated ones, thanks to companies like Kraken. On June 11th, 2026, Kraken announced the launch of its Autonomous Agent platforms, specifically targeting utilities companies.<\/p>\n Currently, Kraken\u2019s utility platform supports more than 90 million accounts in over 15 countries. In April, its Saudi Energy joint venture reserved licensing rights covering another 11.5 million accounts. The Autonomous Agents offer is still new, but Kraken and Sierra have already announced a four-week launch at an unnamed utility covering 1.3 million accounts<\/a>.<\/p>\n That four-week claim makes the decision-to-deployment question unusually important. Buyers need to know what was live, which actions were enabled, how exceptions reached people, what stabilization was required, and which results survived after launch. Without those answers, speed is evidence of a release, not proof of a completed CX transformation.<\/p>\n TL;DR: What Should Buyers Know Before Deploying Kraken Autonomous Agents?<\/p>\n Kraken\u2019s scale is real and growing: 90 million+ accounts across 15+ countries, plus a Saudi Energy JV (April 2026) reserving rights to another 11.5 million. How Should Utilities Evaluate a New Customer Platform? The Kraken utility platform is the operating foundation, while Kraken Agentic Customer Service is the AI portfolio<\/a> built on top of that foundation. Within the portfolio, Human Assist supports employees, and Kraken Autonomous Agents handle customer-facing journeys. Open Kraken provides a separate route for approved third-party AI agents and applications.<\/p>\n Kraken Customer is the AI-powered system<\/a> sitting at the center of the utility platform. It brings together the customer account, tariff, meter history, bills, payments, contact history, and service record. Kraken also offers separate products for field operations, networks, generation, and energy flexibility.<\/p>\n Kraken layer Kraken utility platform Kraken Customer Agentic Customer Service Human Assist Autonomous Agents Open Kraken Autonomous Agents<\/a> is the feature launched in collaboration with Sierra on June 11, 2026. Sierra provides the conversational layer, while Kraken supplies utility-specific context and access to approved actions. That combination can move service beyond drafting and summarization, but only across journeys the utility has configured, governed, and tested.<\/p>\n Assaf Biderman, Kraken\u2019s Chief AI Officer, said in the June 11 launch announcement: \u201cEnergy is too important, too complex and too urgent for generic AI.\u201d<\/p>\n Autonomous Agents only earn their place if Kraken\u2019s context produces a better answer and the utility\u2019s controls stop the agent from stepping beyond its authority.<\/p>\n Key Takeaways<\/p>\n The Kraken utility platform provides the operating foundation, with Kraken Customer supplying the customer data and workflow context. How Should Utilities Evaluate Kraken Autonomous Agents?<\/p>\n Utilities should test Kraken Autonomous Agents on the journeys customers and employees already find painful, using their own data, rules, teams, and exceptions. A worthwhile proof of concept checks whether identity, account history, billing logic, permissions, escalation, and audit records hold together when the customer switches channels or explains the problem badly.<\/p>\n Start with a disputed bill, failed payment, missing meter reading, complaint, vulnerability flag, or complex account change. Then have operations build the journey, alter a rule near the billing date, and show what happens when the agent lacks permission or receives conflicting information.<\/p>\n Buyers also need a hard line between software they can deploy and features they\u2019ve seen on a roadmap. Product Studio is available. Kraken\u2019s Bill Editor remains in development, while its wider AI access layer is still described as forthcoming. Those distinctions affect the utility platform implementation plan, contract value, and expected launch date.<\/p>\n The best evaluation asks whether customer journey management<\/a> still works when the neat path breaks. That\u2019s the moment a utility CX transformation either starts to look credible or begins collecting expensive footnotes.<\/p>\n Key Takeaways<\/p>\n Test the proof of concept against real, uncomfortable journeys: a collections change close to a billing date with an open complaint attached. Learn more about the complexity of customer journey management here<\/a>.<\/p>\n What Must Utilities Agree Before Signing for Kraken Autonomous Agents?<\/p>\n Before signing, utilities should define the first journeys, channels, customer cohorts, data fields, permitted actions, approval thresholds, and evidence required to expand autonomy. The contract must separate configuration, shadow testing, first live use, stabilization, and scaled rollout, while assigning responsibility across Kraken, Sierra, the utility, integrators, and relevant subprocessors.<\/p>\n Use separate contractual milestones for configuration complete, shadow mode passed, first customer live, stable operations, expanded action rights, and scaled rollout. One broad \u201cgo-live\u201d date lets each supplier claim success at a different point. Any Kraken Customer migration, payment change, or other platform work should remain a named dependency rather than disappearing inside the Autonomous Agents milestone.<\/p>\n Supplier boundaries still matter. Kraken\u2019s April 16, 2026<\/a> subprocessor list names cloud, monitoring, communications, AI, and support providers, including Sierra for conversational AI. The contract should specify applicable providers, processing locations, retention, optional services, audit access, incident response, service levels, and notice requirements when that chain changes.<\/p>\n Put these five answers in writing before giving a signature:<\/p>\n Which journeys, channels, languages, actions, and customer cohorts are included in the first release? Deploying Kraken Autonomous Agents needs senior owners across customer operations, billing, metering, data, payments, security, privacy, compliance, workforce, and technology. It also needs verified identities, current account context, approved knowledge, vulnerability and complaint flags, tested exception paths, and employees who can take over immediately when the agent reaches its authority limit.<\/p>\n Kraken\u2019s configurable tools can reduce some development work, but they cannot decide tariff logic, debt policy, vulnerability treatment, complaint handling, or who owns a broken journey. Each journey needs one accountable business owner and named configuration owners for thresholds, permissions, approval routes, and customer communications.<\/p>\n A utility can launch a bounded agent faster when Kraken Customer is already stable. Where the AI project depends on a wider platform migration, resource needs rise sharply. Capita\u2019s March 2026<\/a> case study says it mobilized 77 people in one week and added another 100 FTE during an unnamed Kraken migration, exposing the support burden that can sit beneath an apparently simple AI release.<\/p>\n Training should begin while journeys are designed. Employees need practice with identity failures, disputed bills, payment changes, complaints, approvals, reversals, and human handoffs, not a late tour of the interface. A project that waits days for every policy answer will burn through even an apparently short launch schedule.<\/p>\n Key Takeaways<\/p>\n Dedicated journey, data, policy, security, and operations owners are implementation requirements, not optional governance. Why Are Utility Customer Migrations Completed In Phases?<\/p>\n Deploying autonomous agents into a utility contact center in phases makes sense because customer journeys and account actions carry different levels of risk. Read-only answers and low-impact service requests can move first, while disputed balances, vulnerable customers, bespoke tariffs, multi-site accounts, payment changes, complaints, and debt arrangements require deeper testing, human approval, and stronger evidence.<\/p>\n Just because Kraken and Sierra shared information about a four-week launch doesn\u2019t mean every utilities company should expect the same timeline. In a January 31, 2026 Times profile<\/a>, Kraken CEO Amir Orad said a new platform client can take up to two years to switch after dozens of workshops, executive meetings, and site visits. A fast agent release is plausible only when the required Kraken Customer context and operating decisions already exist.<\/p>\n Independent, named evidence exists for at least one large migration. When Energy Queensland completed the Ergon Energy Retail migration to Kraken, Ayesha Razzaq, Executive General Manager Retail at EQL, said in Octopus Energy\u2019s official migration announcement that the transformation was completed \u201cahead of schedule,\u201d calling it \u201ca credit to the technology, the deployment method, quality of the people and our partnership with Kraken.\u201d<\/p>\n Each agent wave still needs to prove that identities match, account data is fresh, answers come from approved sources, actions follow policy, human handoffs work, and mistakes can be reversed. Billing and reconciliation remain hard stops for anything that can alter a balance, payment, tariff, or debt position.<\/p>\n Use a clear autonomy ladder: employee drafting, read-only customer answers, recommended actions, approval-based actions, low-risk autonomous actions, and only then higher-impact journeys. Expand one variable at a time, whether that\u2019s the journey, channel, cohort, language, or permission, so failures have somewhere obvious to point.<\/p>\n Key Takeaways<\/p>\n Treat the four-week launch as proof that one tightly defined release can work, not permission to scale every journey, channel, cohort, and action right. What Controls Are Required Before and During Kraken Autonomous Agents Stabilization?<\/p>\n
\nThe Sierra partnership shows real deployment speed: Autonomous Agents went into production at an unnamed major utility within four weeks, covering 1.3 million accounts.
\nPhased migration is non-negotiable, not optional: timelines range from Ergon Energy\u2019s 185 business days (750,000 accounts) to Origin Energy\u2019s 2.5 years (4.2 million accounts).
\nThe gap: most published results (Origin\u2019s $170M cost-to-serve cut, Ergon\u2019s 90% Happiness Index rise) come from Kraken\u2019s own case studies, with baseline and staffing details not always disclosed.<\/p>\n
\nWhat Should Be Agreed Before a Utility Platform Contract Is Signed?
\nWhat Resources Are Required for a Utility Platform Implementation?
\nWhy Are Utility Customer Migrations Completed in Phases?
\nWhat Happens During Utility Platform Stabilization?
\nWhat Must Be in Place Before AI Agents Can Act on Customer Accounts?
\nHow Should Utilities Measure Platform Implementation Success?
\nFAQs
\nHow Do the Kraken Utility Platform, Agentic Customer Service, and Autonomous Agents Fit Together?<\/p>\n
\nRole
\nWhy it matters<\/p>\n
\nWider utility operating environment
\nConnects customer operations with billing, field work, networks, generation, and flexibility.<\/p>\n
\nCore customer platform
\nSupplies the account data, workflow context, and approved actions AI tools need.<\/p>\n
\nUmbrella AI portfolio
\nIncludes Human Assist and Autonomous Agents.<\/p>\n
\nEmployee-facing AI tools
\nSupports drafting, summaries, knowledge retrieval, and complaint handling.<\/p>\n
\nCustomer-facing agents built with Sierra
\nThe specific product evaluated in this article.<\/p>\n
\nThird-party AI access through MCP gateways
\nLets approved external agents and applications connect to Kraken capabilities.<\/p>\n
\nKraken Agentic Customer Service is the wider AI portfolio; Human Assist and Autonomous Agents serve different users and shouldn\u2019t be treated as the same product.
\nAutonomous Agents is the customer-facing product under review, while Open Kraken is a separate extensibility route for third-party AI.<\/p>\n
\nBill Editor and the wider AI access layer are still in development or forthcoming, not currently deployable, confirm what\u2019s actually live before pricing them in.<\/p>\n
\nWho approves action rights, policy changes, models, prompts, and new cohorts?
\nWho investigates, reverses, records, and reports an incorrect action?
\nWhat evidence must be met before human approval is reduced?
\nCan the utility export conversation history, evaluations, audit records, and journey logic on exit?
\nWhat Teams and Data Are Required to Deploy Kraken Autonomous Agents?<\/p>\n
\nCapita\u2019s recent case study shows why buyers should budget for stabilization capacity rather than assuming configuration tools remove operational labor.<\/p>\n
\nProgress through an autonomy ladder, with account accuracy, action-risk evidence, escalation, and reversibility determining the next wave.<\/p>\n