Large public transport group

AI customer experience audit: 45,000 calls analysed

A full audit of a shared contact centre: 2,000 hours of conversation analysed to find the root causes of dissatisfaction and the scope for automation.

Client
Large public transport group
Secteur
Public transport
Période
2025 - 2026
Technologies
GeminiBigQuerySupabaseCloud RunPython

45,000

conversations analysed, that is 100% of the flow over two quarters

23% of the call flow assessed as automatable

A prioritised roadmap, from quick wins to structural work

The shared contact centre of a large public transport group handles requests from several hundred thousand beneficiaries: human resources questions, payroll, staff benefits, administrative situations. First contact resolution had plateaued, and nobody could say precisely why.

Rather than audit a sample, the analysis covered the entire flow over two quarters, which came to forty-five thousand conversations and around two thousand hours of audio.

The method

The recordings are first renamed by technical identifier and anonymised before any processing, then transcribed automatically. Each call is then classified against a strict framework: two-level reason, segment, resolution status, satisfaction, repeat contact, friction point. No free text, only categories that can be compared and added up.

A composite model combining severity and volume then ranks the fifteen largest problem groups, with automatic detection of satisfaction anomalies and excess repeat contacts. For each area, systematic sampling of summaries and targeted reading of transcripts make it possible to reconstruct the real customer journey, with every conclusion carrying an explicit confidence level.

The conclusions

The analysis overturned the initial diagnosis. The problem was not the quality of the advisers but a set of systemic causes: case statuses the customer cannot see, fragmented portals, fragile authentication. Five root causes account for most of the volume.

The audit delivered a prioritised roadmap separating quick wins from structural work, an assessment that twenty-three per cent of the flow could be automated, and, just as important, a list of sensitive flows explicitly ruled out of any automation. It also produced a glossary of the language customers actually use, built from their own words and directly usable to equip a future self-service channel.

For reasons of confidentiality, the end client is not named. The figures quoted are those of the engagement.

Next step

Where would you start?

Ten days to map where your teams lose time, put a figure on each lever and name the first system to build. If AI is not the right answer, I will tell you so.

Diagnostic

Étape 1

10 days

€9,500 excl. VAT · fixed fee, one area of the business

  • A map of where the time actually goes in the area audited
  • Each lever costed in hours freed, ranked by effort and by gain
  • The data note: what leaves your systems, and where it is processed
  • A three-month plan, naming the first system to build