Our thinking

From chatbots to agents in customer service

On this page
  1. 01From scripts to agents
  2. 02What an agent can do that a chatbot couldn't
  3. 03Where it pays off
  4. 04Doing it well
  5. 05Our view

A few years ago, a customer service bot answered questions from a script. Today the same chat window can check an order, arrange a replacement and book a callback, and know when to pass the conversation to a person. The chatbot has become an agent.

From scripts to agents

Rule-based bots follow a fixed script: reliable for simple questions, stuck on anything else. Language models changed that. Modern agents understand what a customer means, not just the words they type, and can act on it in the tools behind the conversation: the order history, the CRM, the booking calendar.

What an agent can do that a chatbot couldn't

  • Look things up: order status, account details and delivery dates, from your own records.
  • Take action: rebook, refund within set limits, update an address.
  • Remember context across messages and channels, so customers don't repeat themselves.
  • Hand over to a person, with the full story, when a request needs judgment.
AI-powered assistants now handle a growing share of routine customer interactions. Photo: Konstantin Evdokimov on Unsplash
AI-powered assistants now handle a growing share of routine customer interactions. Photo: Konstantin Evdokimov on Unsplash

Where it pays off

  • Availability: support that doesn't stop at the end of a shift.
  • Scale: many conversations at once, at the same quality.
  • Languages: support across markets without hiring for every language.
  • Insight: every conversation becomes a signal for what to fix.

Doing it well

The difference between a helpful agent and a frustrating one is rarely the model. It's the setup:

  • Start with the top requests, the handful of questions that make up most of the volume.
  • Ground every answer in your own data and policies, with a source the team can check.
  • Set limits: what it may do alone, what needs approval, and what it must never touch.
  • Make handover easy: one step to reach a person, with nothing lost.
  • Review real conversations every week, not just at launch.

Our view

We build agents as part of a company's data and customer experience, not as a widget on top. What an agent learns in a conversation should feed back into the business, and what it does should be logged and reversible. Used that way, agents don't replace a support team. They give it time for the conversations that need a person.

Tell us what you want to build.

A 30-minute call with our CTO to explore what we could build or automate for your business.