← All case studies AI costs and FinOps

The contact centre assistant

Designing AI for cost, on purpose

Illustrative scenario, drawn from episode 5.

The situation

A contact centre assistant helps agents answer customer emails. It works, and the bill grows with every success.

The version that surprises the finance director

  • Every email goes to the most powerful model.
  • The full customer history and the entire returns policy are attached every time.
  • The assistant drafts, checks its own draft and redrafts, three or four times.
  • Nothing is cached, even though most emails ask the same ten questions.
  • The cost lands in one central IT budget, so the contact centre never sees it.

The redesign

  • A small model sorts each email by type.
  • Common types are answered from a cache of approved responses.
  • Only genuinely unusual emails go to the powerful model, with just the relevant paragraphs of policy.
  • One draft and one check, then it hands over to the human.
  • The contact centre owns the budget, measured as cost per email resolved.

The lesson

Same capability. Same quality, proven on the evaluation set. A fraction of the calls. None of it needed a new vendor or a new contract. It needed someone to design for cost from the beginning.

Let's talk

Speaking, collaborations, sponsorship or a conversation about your architecture and AI plans.

Get in touch