TRV-2026-0553Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-0553 version: 1 kind: certified reason: Certified into the record timestamp: 2026-07-24T06:05:47.270539Z status: published lens: p_space sector: labor headline: ‘Customers prefer AI chatbots,’ says British Gas owner as 1,300 call centre jobs axed dek: The owner of British Gas has claimed that most households would rather speak with an AI chatbot than deal with the company’s staff as it prepares to cut 1,300 jobs from its call centres. Centrica, the supplier’s FTSE 100 owner, plans to cut 800 jobs as the company carries out a “targeted deployment of AI tools”, on top of the 500 cuts it confirmed last month. The plan to reduce the supplier’s customer service teams in Glasgow, Edinburgh, Cardiff, Leicester, Stockport and Leeds by 14% is expected to take place ov… gain_title: (none) problem_title: Centrica will eliminate 1,300 British Gas call centre jobs across six UK cities as it carries out targeted deployment of AI tools and chatbots. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: Centrica will eliminate 1,300 British Gas call centre jobs across six UK cities as it carries out targeted deployment of AI tools and chatbots. problem_evidence: cut 1,300 jobs from its call centres | plans to cut 800 jobs as the company carries out a 'targeted deployment of AI tools' quick_read: On 23 July 2026, The Guardian reported that Centrica, owner of British Gas, will cut 1,300 call centre jobs, including 800 new cuts linked to a 'targeted deployment of AI tools' across six UK cities over two years. CEO Chris O'Shea said over 90% of customers now use digital channels first and calls have fallen 20%, while unions warned hundreds of human jobs would go to chatbots. The case matters because it links AI customer-service automation directly to large-scale displacement of frontline workers, even as retail profits rise. What remains uncertain is whether AI is the primary cause, as O'Shea attributes the cuts mainly to changing customer behaviour and says the firm expects to grow jobs around its digital interface. limitation: CEO disputes that AI is the primary driver of cuts, attributing reductions mainly to changing customer behaviour, leaving causal link between AI deployment and job losses contested. tag: Evidence-backed problem key_points: Centrica plans to cut 800 additional call centre jobs through 'targeted deployment of AI tools', on top of 500 cuts confirmed last month, totaling 1,300 roles. | Reductions represent 14% of customer service teams in Glasgow, Edinburgh, Cardiff, Leicester, Stockport and Leeds over two years via unfilled resignations and redundancies. | CEO Chris O'Shea said over 90% of customers use digital channels first and calls fell 20%, while unions said investment would give 'hundreds of human jobs' to chatbots. | Retail division profits rose to 346m in first half from 338m a year earlier even as domestic customers fell to 7.45 million. rundown: Centrica said the 14% reduction across Glasgow, Edinburgh, Cardiff, Leicester, Stockport and Leeds will occur over two years, with some posts left vacant after resignations and the remainder through redundancies, following 500 cuts confirmed last month. The company reported retail profits of 346m in the first six months, up from 338m a year earlier, while British Gas domestic customers fell to 7.45 million from 7.5 million, and it faces up to 112m in compensation for force-fitted prepayment meters. sources: - journalism | The Guardian | https://www.theguardian.com/business/2026/jul/23/customers-prefer-ai-chatbots-says-chris-oshea-british-gas-centrica-boss | 2026-07-23 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 19db26a006fbefcdc953a9d726cd4d68cbdebff48ac305d0abc4924b90a581ec
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0553 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace