DEV Community

Barry Batsbak
Barry Batsbak

Posted on

What we learned hiring an AI colleague for customer support

Most small and mid-sized companies in the Netherlands do not need another dashboard. They need a colleague.

We build AI colleagues: one agent per role, working inside the tools a team already uses. This is what we learned after running these agents for more than 40 Dutch SMEs, and what we would tell anyone starting with one.

Start with one process, not with a platform

The failure mode is a company-wide AI programme. The working mode is one process with a clear owner:

  • pick a process that runs every day
  • make sure it has a measurable output
  • give one person ownership

Customer support triage is the most common first choice. It has volume, a clear output and an obvious owner.

The agent needs three things

  1. Context. Product documentation, price list, internal procedures, tone of voice.
  2. Tools. Mailbox, helpdesk, CRM. Read first, write later.
  3. Escalation. A rule for when a human takes over, and a log of every handover.

Human control is not optional

An agent that answers 80 percent of questions is useful. An agent that answers 100 percent and is wrong 5 percent of the time is a liability. We keep a human owner who reviews the queue weekly, and we log every escalation.

What it returns

In our own deployments the pattern is consistent: the first response time drops from hours to minutes, the team stops answering the same ten questions, and the human owner spends the freed time on the cases that actually need judgement.

Doing it yourself

If you want to try this inside your own team, the practical route is:

  • write down the ten most common questions
  • document the answer for each one
  • decide the escalation rule
  • measure the first response time before you start

You can find the working templates and the process we use for this on Match-AI.

The short version: one process, three ingredients, one human owner.

Top comments (0)