How Much Support Does an AI Assistant Really Handle?

„Our AI assistant resolves 80 percent of all enquiries on its own.” Sentences like this appear on many vendor pages, and they sound tempting. Yet anyone introducing a chat assistant to relieve their support should know the figure that is really achievable in the first year, rather than being guided by a marketing slide. The truth sits between two poles: a well-built assistant takes noticeable work off a team, but rarely at the push of a button and almost never at the level promised in the first conversation. High automation rates in first-level support usually only emerge after months of care. Fresh deployments start on well-structured topics with a more modest rate and only climb higher over time. For explanation-heavy services, only 10 to 15 percent of contacts are realistically automatable in the first year (project experience) before the curve rises. This article shows how much an AI assistant really handles, why the big promises mislead and how a hybrid setup with a knowledge base and handover raises deflection step by step.

Enlarge graphic

Labels in the illustration

• Higher values only after care
• start
• grows
• grows
• higher
• Month 1
• Month 3
• Month 6
• Month 12
• One contact, two paths
• resolved
• handed over
• Care
• raises the rate
• month by month
• not at the push of a button
• 10-15 %
• Realistic in the
• first year
• (project experience)
• $0.09
• vs $14
• Cost per contact
• self-service vs human
• (Gartner)
• Honest targets, measured weekly - the rate grows with knowledge base and handover

How Much Support Does an AI Assistant Really Handle?

What „Handling Support” Really Means

Before arguing about percentages, it is worth looking at the terms. „Handling support” can mean three things, and the figures behind them differ greatly. The deflection or automation rate measures the share of conversations that end without a human. The resolution rate measures only the cases where the concern was actually settled. And the handover rate shows how often the assistant deliberately passes on to a staff member. These three metrics are readily mixed up in marketing: counting every chat without a human as resolved, including the one where the customer gives up in frustration, produces good-looking numbers. Some vendors even pass off plain tier-1 automation as deflection, which lifts the figure further. Measurement only becomes honest when resolved enquiries, deliberate handovers and drop-offs are reported separately.

Why the 80 Percent Promises Mislead

The big numbers on vendor pages are rarely made up, but they mostly come from ideal conditions. They apply to a single, extremely well-structured use case, such as the shipping status in an online shop with a connected inventory system, measured after months of fine-tuning and often without subtracting the frustration drop-offs. Applied to a freshly introduced assistant with mixed concerns, a very different picture emerges. Across the board, the automation rates actually achieved are usually lower than on vendor pages, and even high-performing systems mostly reach the advertised peak values only on narrowly defined, highly structured topics and after substantial investment in the knowledge base. McKinsey puts the potential more cautiously: generative AI could deliver productivity gains in customer care worth 30 to 45 percent (McKinsey) of current function costs and further reduce the volume of human-serviced contacts by up to 50 percent (McKinsey), depending on the existing level of automation. That is a lot, but it is not an instant eighty percent solution.

For expectations this means: the interesting question is not whether an assistant manages 80 percent, but which share of your specific enquiries is suited to an automated answer at all. Part of the contacts is pure routine and can be caught well, another is personal, legal or technically delicate and belongs with a human. 62 percent (Bitkom) of online buyers want to turn to a quickly reachable, human contact in case of a problem, while a chatbot is wanted by only 36 percent (Bitkom). Anyone who ignores this and optimises for a high rate at any cost saves in the wrong place. How you can convince skeptical customers of an assistant anyway, without cutting the human connection, is shown in the linked article.

What Is Realistic in the First Year

More reliable than any advertising figure is a sober look at the typical course. Freshly introduced assistants start, depending on topic structure, with a more modest deflection than vendors advertise and only raise it noticeably over months of care - provided the topics are clear and the knowledge base is maintained. For explanation-heavy B2B services with individual concerns, the start is much flatter: here only 10 to 15 percent of contacts are often sensibly automatable in the first year (project experience), because many questions require context, contract data or an expert assessment. This range is not a flaw but the honest starting position - and exactly the reason an assistant must measure and grow from the outset.

The ranges in the table are experience values (project experience) and shift with industry, audience and care effort. The reading matters: a mixed enquiry situation almost never adds up to a high starting value, because the demanding cases pull the easily automatable ones down. Anyone who knows their realistic starting point can work deliberately on the topics that offer the greatest leverage, instead of chasing a blanket target figure.

The Hybrid Setup: Knowledge Base and Handover

The decisive lever for a rising automation rate is not a clever prompt, but the combination of two building blocks: a maintained knowledge base from which the assistant answers reliably, and a clean handover to humans that catches everything it should not take responsibility for. The knowledge base ties the answers to your own content and prevents the assistant from inventing freely; how this works in detail is shown by the article on preventing hallucinations with a knowledge base and retrieval. The handover, in turn, is not a failure but the built-in seatbelt: as soon as things become personal, legal or technical, the assistant is meant to pass on to your team with full conversation context. How this handover to staff succeeds smoothly is worth a topic of its own.

How Deflection Rises Step by Step

An automation rate is not a fixed value you set once, but a curve you nurture. The way up follows a recurring pattern that repeats over weeks and months and lifts the rate in clearly measurable steps. What matters is that each step comes from real conversations and not from an assumption about what customers supposedly ask.

• Start measurably: the assistant goes live with a clearly defined topic set, and every metric is captured from day one.
• Review conversations: the analysis of the chats shows which questions come up often and where the assistant still has to fit.
• Close the knowledge base: for every recurring gap a reliable piece of content is added, so the assistant answers the question itself in future.
• Sharpen handover rules: cases it can solve safely it takes on; delicate ones it passes to the team earlier and more cleanly.
• Check the effect: in the next period the rate rises measurably, and the next bottleneck becomes visible.

Does It Pay Off? The Cost per Contact

Whether automation is worthwhile is decided not by the highest rate, but by the cost per contact. Personal handling is expensive: in 2022, Gartner put a contact in assisted service at $14 (Gartner), while a contact in digital self-service channels cost $0.09 (Gartner). What an automated answer costs in your own operation depends on the operating model and is best assessed against your own cost per contact. In 2022, Gartner predicted that conversational AI in contact centres would cut agent labour costs by $80 billion (Gartner) by 2026. Even a modest deflection of 10 to 15 percent therefore shifts costs noticeably at high enquiry volume - the effect comes from volume times saving, not from the largest possible percentage on the slide.

It is important to calculate the benefit honestly. On top of the saving per automated contact come the faster response and the relief for the team, which concentrates on the demanding cases; against this stand introduction, care of the knowledge base and operation. How to weigh these sides seriously is set out by the article on cost, benefit and ROI of an assistant. And because a relieved first level also lowers the waiting times for the remaining personal enquiries, the automation works twice - a connection the article on relieving support around the clock explores in depth.

What an Assistant Deliberately Does Not Handle

As useful as automation is, it has clear limits, and a serious setup names them. An assistant is not meant to give legally binding information, make a goodwill decision or offer a remote diagnosis for a technical fault. It works with the content it is trained on and can be wrong; that is why a properly set-up assistant ties its answers to your sources and passes anything uncertain on, instead of inventing. Mood counts too: when a concern tips over, the assistant should recognise the frustration early and hand over to a human before the contact is lost. How to detect frustration in the chat and escalate in time is worth an article of its own. This restraint is not a weak point but the precondition for customers to trust the assistant at all.

A Few Steps to Measurable Automation

The path to an assistant that noticeably handles support begins not with a target figure but with an honest stocktake: which enquiries come in how often, which of them are routine, and where is the human indispensable? On this basis the assistant is trained on your content, given clear handover rules and embedded with a short snippet. After that it measures from day one. A fixed rate cannot be seriously assured, because how much can be automated depends on your topics, your audience and the care. What is reliable, by contrast, is the mechanism: measurable start, weekly review, closed knowledge gaps and a rate that grows. Which building blocks sit behind this is bundled in the scope of the support assistant; for an overview of packages see the pricing and packages, for examples the reference projects.

• Capture enquiries and sort them into routine, advice and delicate cases
• Build and maintain a knowledge base from FAQ, service pages and manuals
• Define clear handover rules for personal, legal and technical cases
• Measure deflection, resolution and handover separately, instead of celebrating one combined figure
• Refine weekly from the conversations and close recurring gaps
• Secure data protection and hosting in Germany contractually

Frequent questions