The 45 Jobs CBA Had to Give Back

In July 2025, Commonwealth Bank of Australia told 45 customer-service staff their roles were redundant, saying its new Hey CommBank voicebot had already cut call-centre volume enough that the work no longer existed. Six weeks later, on 21 August 2025, the bank reversed the decision and apologised.

The evidence beat the vendor claim. Finance Sector Union national secretary Julia Angrisano had spent those six weeks pulling the bank's actual call-volume figures instead of the ones CBA had published, and found the opposite of what the bank claimed: calls were rising, not falling, forcing team leaders off their desks and onto the phones to cover the gap. CBA told the Fair Work Commission its redundancy assessment had been flawed, and offered the 45 staff their old roles, a transfer, or an exit package.

Why the Reversal Was Not the End of the Story

The reversal changed the optics and the pace, not the trajectory. Eleven months after apologising for the 45 cuts, Commonwealth Bank had cut roughly 800 more roles across 2026, according to the Finance Sector Union's running count: about 300 in February, another 120 in April (43 of them at its Bankwest subsidiary), 176 technology and engineering roles in July, and hundreds of contractor chat-support jobs at its outsourced Johannesburg call centre that same month.

None of these later rounds triggered the same public reckoning as August 2025. Each was smaller, spread across different business units and geographies, and none repeated the specific, checkable claim - 'the voicebot cut calls by X a week' - that the union had been able to disprove with the bank's own data. A single testable claim is fragile in a way a dozen smaller, vaguer ones are not.

The Tell: How CBA Talked About Automation Changed

Watch the attribution, not just the headcount. In 2025, Commonwealth Bank was happy to say AI was cutting call volume - that claim was the entire justification for the 45 roles. By April 2026, when the bank cut a further 120 roles, it said only 6 of them were impacted by automation; the other 114, including 43 at Bankwest, were attributed to other causes.

Yes, but the pattern around the label tells a different story. In the same stretch, CBA's own general manager of self-service experiences, Rachel Round, said Hey CommBank was resolving close to 9 in 10 of the bank's more than 2 million monthly customer conversations without a human agent - and hundreds of contractor roles at its offshore vendor Nutun in Johannesburg were cut that same month as AI absorbed their chat volume. A company that stops calling its cuts automation while its automation rate keeps climbing has not stopped automating - it has stopped saying so.

The Number the Union Says CBA Has Not Explained

Profit growth undercuts the standard justification. Commonwealth Bank reported half-year cash profit of 5.44 billion Australian dollars for the six months to December 2025, up 6 percent on the year before - a result posted three weeks before the bank announced the 300-role February round. The Finance Sector Union has since lodged a formal dispute with the Fair Work Commission, arguing CBA has shown no financial justification for a year that added up to roughly 800 cut roles.

A bank does not need a revenue crisis to keep cutting once a large, repeatable automation platform is in place. The 9-in-10 resolution rate is the machine that keeps generating redundancy candidates regardless of quarterly results - that is the mechanism owners should watch, not the profit line the union is contesting.

The Owner's Checklist: Verify the Volume, Not the Resolution Rate

The bottom line: a resolution-rate stat is not a volume-reduction stat, and only one of them justifies a headcount cut. '9 in 10 conversations resolved' tells you what share of a workload an AI system absorbed, not whether the underlying workload shrank - exactly the distinction the Finance Sector Union used to unwind CBA's 2025 cuts, and exactly the distinction a vendor's dashboard will never surface on its own.

Before approving a headcount decision built on any AI vendor's productivity claim, pull the raw volume trend the claim is meant to explain - total calls, tickets, or conversations over the same period - not the tool's internal resolution share. In the EU and UK, that data request is also the paper trail works councils and employee-consultation bodies increasingly expect before a redundancy tied to automation goes ahead. If a public reversal follows a bad call like CBA's in August 2025, track the next two quarterly disclosures across every channel the company uses to cut headcount, including offshore vendors and contractors, which sit outside the scrutiny that forced the first reversal.