---
title: "Customer service with a visible route to a person"
description: "Escalation as a visible right rather than a hidden exception: how to automate customer service without hiding the people."
source_name: "Gen8"
source_url: "https://gen8.app/en/kennis/klantenservice-met-menselijke-route/"
site_home: "https://gen8.app/"
source_description: "Managed AI service for SMEs. We set up, connect and manage; you stay in control."
locale: "en"
authors:
  - name: "Tijs Berens"
    url: "https://gen8.app/en/kennis/author/tijs-berens/"
copyright: "© 2026 Gen8 VOF · Dutch Chamber of Commerce 92978789 · Delft"
published_at: "2026-09-09T00:00:00.000Z"
modified_at: "2026-10-21T20:13:24.130Z"
---

# Customer service with a visible route to a person

Most complaints about automated customer service concern the feeling of being trapped rather than the answer. That is a design choice, and you can make it differently.

By Tijs Berens · September 9, 2026 · Email

## What really irritates people

A wrong answer from a system is annoying but forgivable; people give wrong answers too. What stays with people is something else: the feeling that there is no way out. Rephrasing the same question three times, no button to reach a person anywhere, and the uneasy suspicion that the route to an employee was deliberately tucked away to cut costs.

That suspicion is often correct. That is precisely why keeping the human route visible is not a courtesy but the core of the design.

## Four design rules

### 1. The way out is always there, from the first message

Not only after three failed attempts, not hidden in a footer. The option to speak to a person is visible from the start, with an honest indication of when that is possible. Curiously, fewer people use that route when it is clearly visible: knowing it exists removes the tension.

### 2. Uncertainty is an outcome, not an error

A workflow must be able to say “I do not know,” and that must lead somewhere. If the model cannot answer the question confidently from the sources, the conversation goes to a person — with the context, so the customer does not have to start over. That last part is half the job.

### 3. Sources alongside the answer

An answer about a delivery time, warranty period or condition refers to where it is stated. That gives the customer something to check and gives you a signal: if the source is outdated, that becomes visible instead of the model confidently repeating something obsolete.

### 4. Outgoing messages with approval, initially

The workflow may read and prepare replies. Sending is a separate decision. Start with human approval for everything going out, and change that only when the log shows which types of questions are consistently answered correctly. Not the other way around.

## What is never automatic

- An emotionally charged complaint. The model sees the words, not the fact that this customer already called last week.
- Anything creating an obligation: a goodwill arrangement, a credit, a commitment about a deadline.
- A question about which the customer explicitly says they want to speak to a person. That is not an objection to overcome.

## What to measure

Do not only measure the share of questions handled without a person — that figure rises by itself if you hide the way out, and then means nothing. Also measure how often a customer contacts you again after the automatic answer, and how many transferred conversations an employee could resolve without further questions. Together, those two show whether automation works or only postpones the work.

## What to do with this

Take the last fifty customer questions and divide them into three piles: factually answerable from a source, judgment required, and emotion or obligation. Only the first pile is an automation candidate — and the size of the third tells you how much you really gain. The working approach is under [handling customer questions with escalation](<https://gen8.app/en/mogelijkheden/klantvraag-afhandelen/>), with a practical setup in the case [inbox triage at a service agency](<https://gen8.app/en/cases/inbox-triage-servicebureau/>).

## Frequently asked questions

Should I disclose that an AI is answering?

Yes, and not just because it is courteous: customers phrase their questions differently when they know who is reading. Hidden automation is also almost always recognized, and then the conversation becomes about that rather than the question.

What should I do if the knowledge base is outdated?

That is the first problem to solve, not the second. A workflow showing sources alongside its answer makes outdated information visible; without that reference, the model repeats old information just as easily as current information.

## Want to apply this to your own process?

Bring one process to a conversation. We assess suitability, risk and the cost of the first step.

[Book an introduction](<https://gen8.app/en/contact/>)

- Reply within one business day
- No obligation