How Commonwealth Bank's voice bot cuts were reversed.

The short version.

In June 2025 Commonwealth Bank of Australia (CBA) put a voice bot on the inbound phone line of its Customer Service Direct business. On 29 July it confirmed that 45 roles in that business were affected, and told the Finance Sector Union the bot had cut calls by 2,000 a week.²³²⁴ The union said call volumes were rising, that staff were being offered overtime and that team leaders were taking calls, and it took the dispute to the Fair Work Commission.¹¹

On 21 August, 23 days after the roles became public, CBA said its assessment "did not adequately consider all relevant business considerations and this error meant the roles were not redundant". It apologised and offered each person the choice to stay, move to another role or leave.²⁶ At the annual general meeting in October the Chair told shareholders: "We made a mistake."³¹

No tribunal ruled on the case, and nobody outside the bank has seen the call data. Its value is as a clear example of a common failure: a headcount decision taken on an early, unpublished reading of what an AI system had done, before the effect had settled and before the people doing the work were asked.

The call centre before the bot.

Customer Service Direct, also called direct banking, is the CBA business that answers customers' calls. In June 2024 the union reported that 158 roles there would be made redundant and the people moved into broader roles.⁸ In September 2024 CBA began trialling Hey CommBank, a text-based AI chat tool. At the time it had more than 2,400 call-centre staff handling about 50,000 customer contacts a day.³³

AI was a stated priority at board level. In March 2025 CBA expanded its partnership with Anthropic and invested in the company, and in August 2025, while the voice bot dispute was running, it announced a strategic partnership with OpenAI.¹² The voice bot itself went live in June 2025. It answered calls on the inbound customer enquiries line, worked out what the caller needed and passed the call to a specialist.²³⁹ No public source names the vendor or the technology behind it.

What CBA announced.

The cuts became public on 29 July 2025. CBA confirmed 45 roles in Customer Service Direct were affected by the voice bot. A spokesperson said: "By automating simple queries, our teams can focus on more complex customer queries that need empathy and experience."²³²⁴ The figure CBA gave the union, 2,000 fewer calls a week, was offered in a briefing. It does not appear in any CBA document that could be found.²⁴¹¹

The union's own count was 90 roles. Its total included the 45 call-centre roles and a group of customer messaging roles that it said were moving to CBA India.⁹¹⁰ Its national secretary, Julia Angrisano, said: "Just when we think CBA can't sink any lower, they start cutting jobs because of AI on top of sneakily offshoring work to India."⁹ The two issues ran together in the coverage from then on, and they need to be kept apart to read the case.

What the union put to CBA.

On 7 August the union said it was disputing the cuts at the Fair Work Commission. Its case on the voice bot was practical. Call volumes were going up. Staff in the team had been offered overtime, and team leaders had been taken off their own work to answer calls. It said CBA had not backed the 2,000-calls figure with data and had refused to provide its work health and safety risk assessments or the criteria it used to choose the roles.¹¹

None of these claims has been tested by a tribunal, and CBA did not publish data to rebut them. What CBA did say, two weeks later, was that its assessment had been wrong.

What CBA admitted.

CBA's full statement read:²⁶

"CBA's initial assessment that the 45 roles in our Customer Service Direct business were not required did not adequately consider all relevant business considerations and this error meant the roles were not redundant. We have apologised to the employees concerned and acknowledge we should have been more thorough in our assessment of the roles required. We are currently supporting affected employees and have provided them with choice regarding continuing in their current roles, pursuing redeployment within CBA or to proceed with leaving the organisation. We are also reviewing our internal processes to improve our approach going forward."

According to the union, management told it the bank "didn't properly consider that an increase in calls would continue over a number of months".¹² That is the union's account; CBA's own statement does not mention call volumes. A hearing had been listed for 25 August. The reversal came first, so the Commission never ruled.¹²¹³

The union called it "a massive win for workers", and added: "The damage is already done for the 45 workers who endured weeks of unnecessary stress, not knowing if they would be able to pay bills or support their families."²⁸²⁹³⁰ How many of the 45 stayed, moved or left has not been published.

The episode reached the annual general meeting on 15 October 2025. A former employee asked from the floor what CBA now did to protect staff from having their roles displaced by AI and by offshoring. The Chair, Paul O'Malley, answered: "We made a mistake. We didn't adequately consider all the relevant business considerations."³¹ The shareholders' association recorded that the CEO, Matt Comyn, also apologised and that processes had since been put in place.²² Neither prepared address mentioned the case.³⁴

Why "not redundant" matters.

Under section 389 of the Fair Work Act, a dismissal is a genuine redundancy only if the employer "no longer requires the person's job to be performed by anyone because of changes in the operational requirements" of the business, and has met its obligations to consult. It is not a genuine redundancy if it would have been reasonable to redeploy the person.¹⁶

CBA's statement, that the error "meant the roles were not redundant", reads directly onto the first part of that test. If calls were still rising, the jobs were still needed, whatever the bot was doing. That reading is mine; CBA did not refer to the Act. It explains why a technology claim that could not be shown in data became a legal weakness so quickly, and why the bank chose to concede rather than defend the decision at a hearing.

The offshoring complaint followed a separate track. In October 2025 the union said a review directed by the Commission had found two Australian roles had gone offshore, and that CBA had withdrawn 30 job advertisements in India.¹⁴ CBA had rejected the union's offshoring claims in July: "We refute their claims."⁴⁰ That review concerned offshoring, though it is often reported as part of the voice bot case.

What CBA did next.

CBA appointed a Chief AI Officer in November 2025.⁵ In February 2026 it launched a $90 million, three-year Future Workforce Program. Its release noted that organisations had traditionally made changes and then engaged with workers after the fact, and said the bank had worked with unions to design the programme.⁶ About 300 roles were cut the same day. A spokesperson said AI "is changing how some tasks are performed but it is not the driver of these role changes".¹⁵³⁴

In May 2026 Comyn wrote that "an employer of our scale has a responsibility to avoid false reassurance and give people the best possible chance to adapt", and that "pretending every role can be preserved would not be fair either".³⁵ In July CBA proposed 276 further cuts, which it attributed to "workflow automation, organisational realignments, streamlining".³⁶ The same month Bloomberg reported that hundreds of contractor chat roles at an outsourcer in Johannesburg had gone as AI took over CBA's messaging channel.³⁸³⁹

The cuts continued through the year. In April the union said 119 more roles would go, 43 of them at Bankwest and six linked to automation.⁴² In September it said more than 172 technology roles in New South Wales would go, and put CBA's job cuts for 2026 at more than 1,000. CBA did not cite AI. A spokesperson said "customer needs, technology and how we work continue to evolve", and that more than 500 people whose roles were cut this year had moved into other roles in the bank.⁴³ The union's 1,000 is its own count; CBA has not published a total.

CBA's own figures show Australian staff roughly level from June 2024 to June 2026 and CBA India up by about 1,300 over the same period.⁷ Headcount moves for many reasons, and these numbers cannot show what AI did to jobs. They do show why the union treated automation and offshoring as one story.

The rules around the decision.

The Senate committee on adopting AI had recommended in November 2024 that AI affecting "the rights of people at work" be treated as high-risk, that work health and safety law be applied to its risks, and that workers be "thoroughly consulted".¹⁷ On 29 July 2025, the day the CBA cuts became public, the ACTU called for enforceable AI implementation agreements between employers and workers.¹⁹ The National AI Plan of December 2025 committed, in the ACTU's account, to meaningful consultation with workers.²⁰ In July 2026 the Prime Minister promised AI legislation "early next year", which lawyers expect to touch workplace change.²¹³⁷ By late August, Baker McKenzie read the announced plan as mandatory standards for large data centres and AI training. Workplace adoption and skills were left to consultation with employers, workers and unions, with no legislative timetable.⁴¹ As of October 2026 there is no AI-specific workplace law in Australia; the genuine redundancy test and the duty to consult in the Fair Work Act remain the binding rules.¹⁶

For a bank there is a further layer. APRA's operational risk standard, CPS 230, took effect on 1 July 2025, a few weeks after the bot went live.¹⁸ Nothing links it to this case. It does require banks to manage the operational risk of changes to critical operations and of material service providers, which is where a customer contact channel run partly by bots and partly by outsourcers now sits. That application is my reading.

Why it matters for AI.

The bot was described as a triage tool that passed calls to staff.²³ A system like that changes where work lands and how long it takes; it does not necessarily reduce it. Callers who have been through a bot may arrive at a person later, more frustrated and with harder problems. A few weeks of data after go-live can show fewer calls reaching staff and still miss what happens over the following months, which is what the union says management admitted.¹²

The second lesson is about evidence. CBA's case for the cuts rested on a single number given to the union in a briefing. When it was challenged, there was nothing published to defend it with, and the bank's own statement put the reversal down to an assessment that had not looked at everything it should have.²⁶ A board approving headcount changes on the strength of an AI deployment should expect to see the measurement, over a stated period, before the decision.

The third is about attribution. In July 2025 CBA tied the cuts directly to the voice bot. In February 2026 it said AI was not the driver of the next round.²³³⁴ Naming AI as the cause of job losses invites a particular kind of scrutiny, from unions, the press and shareholders, and the bank learned that in public. CBA has since reached for a different model: a funded workforce programme designed with unions, and a CEO who speaks openly about the jobs at stake.⁶³⁵

What is often misreported.

• It was a voice bot on the phone line. Several headlines called it a chatbot.²⁵²⁹
• The reversed roles were 45 call-centre roles. The union's figure of 90 included messaging roles that were not reinstated, as far as the record shows.⁹²⁶
• The 2,000 calls a week is what CBA told the union. It is not a published measurement.²⁴¹¹
• Staff were told their roles were redundant, then offered their jobs back three weeks later. Stories of a mass rehiring overstate it.²⁶
• No tribunal ruled on the voice bot. The Commission-directed review that found offshored roles belongs to the offshoring dispute.¹²¹⁴
• CBA said call volumes rose and its assessment missed it. No source shows the bot caused the rise.²⁶²⁷

What boards can take from it.

1. Measure for long enough before cutting. The roles were declared redundant within about two months of go-live. Set a measurement period that covers seasonal and follow-on demand, and make headcount decisions after it ends.
2. Publish the number you rely on, at least internally. The 2,000-calls claim was never shown, so it could not be defended. Any headcount case built on an AI system's effect should carry the data, the period and who checked it.
3. Count the work the bot hands back. A triage bot moves work to people as well as removing it. Track transfers, repeat calls, handling time and overtime alongside the calls the bot closes.
4. Test the redundancy separately from the business case. A role is redundant only if nobody needs to do the job. Ask HR and legal to test each role against that standard, and against redeployment, before any announcement.
5. Consult before the decision. The union says CBA would not share its data or how it chose the roles. Bring staff and their representatives into the measurement, so the evidence is agreed before it is used.
6. Explain automation and offshoring decisions separately. Announcing them together let each discredit the other. If both are happening, explain each on its own evidence.
7. Include outsourced and offshore roles in the same view. The later reports concerned contractors in another country. A board should see the whole channel's workforce, not only direct employees, when it reviews an AI rollout.
8. Make reversal possible. CBA could undo the decision because the people were still there. Sequence changes so that a wrong assessment can be corrected before anyone has left.

A board can test itself against these points with five questions. What did the system change, measured over what period, and who checked the number? Has each role been tested against the genuine redundancy standard and against redeployment? Were staff and their representatives shown the evidence before the decision? Does the review cover outsourced and offshore roles in the same channel? If the assessment proves wrong, can the decision still be undone?

To check a proposed AI deployment in a customer channel against these points, place it on the agent risk assessment matrix, and estimate the human review capacity it needs with the oversight ceiling calculator.

What to watch next.

• The 2026 AGM is scheduled for 14 October 2026 in Sydney. The Chair's notice says the board has monitored CBA's investment in priority AI use cases.⁴⁴
• The enterprise agreement is under negotiation. The union is pushing for changes to the redundancy process and a commitment to retrain local staff.⁴³
• AI legislation was promised for early 2027. The announced standards cover data centres and AI training; workplace rules are still at consultation.²¹⁴¹
• The 45 staff. CBA has not published how many stayed, moved or left, or the call data behind its assessment.²⁶

Full timeline.

Common questions about the case.