Back to all posts
AI ChatbotsCustomer ServiceAI Agents

AI Chatbots for Customer Service: What They Actually Do

AI chatbots handle 80% of support questions without a human. Here is how they work, what they can and cannot do, and when they make sense for your business.

Dirk Wierenga
Dirk Wierenga
10 min read

If your last experience with a chatbot was a frustrating decision tree that kept asking you to "rephrase your question," forget everything you know. The chatbots being built today are fundamentally different technology. They understand language, they pull information from your knowledge base, and they handle the vast majority of customer questions without a human touching anything.

Here is what modern AI chatbots actually do, where they fall short, and how to know if they make sense for your business.

The Old Chatbots vs. The New Ones

The chatbots from 2018-2022 were rule-based. Someone wrote a decision tree: if the customer says X, respond with Y. If they say Z, respond with W. The moment a customer phrased something differently than expected, the bot broke. These bots were essentially interactive FAQ pages with extra steps.

Modern AI chatbots are built on large language models. They do not follow scripts. They understand what you mean even when you phrase it in unexpected ways. Ask "when do you close?" or "what are your opening hours?" or "are you guys open on Sunday?" and the bot understands these are all the same question.

The difference is not incremental. It is a category change. Rule-based bots handled maybe 20-30% of inquiries successfully. LLM-based bots handle 70-85% of inquiries without human intervention, depending on complexity.

Chatbots vs. AI Agents

These terms get used interchangeably, but they are different things.

A chatbot answers questions. It takes your input, searches its knowledge base, and gives you a response. It is reactive. You ask, it answers.

An AI agent takes actions. It can look up your order status in the database, reschedule your appointment in the calendar system, process a return in the e-commerce platform, or update your account information in the CRM. It does not just tell you what to do. It does it.

Most modern implementations are a hybrid. The bot handles conversational understanding and simple questions. When the conversation requires an action (booking, cancellation, data lookup), it triggers agent capabilities that connect to your backend systems.

The practical difference for your business: a chatbot reduces support tickets. An AI agent reduces support tickets AND handles transactions that previously required a human in the loop.

What AI Chatbots Handle Well

Not all support questions are created equal. Here is where AI chatbots genuinely shine.

FAQ and Product Information

This is the bread and butter. "What is your return policy?" "Do you ship to Belgium?" "How does pricing work?" "What sizes do you have?" These questions make up 40-60% of most support volumes. A well-configured chatbot answers them instantly, accurately, 24 hours a day.

The key is the knowledge base. You feed the bot your product documentation, FAQ pages, policy documents, and any other reference material. The bot searches this knowledge base for every question. Good knowledge base, good answers. Incomplete knowledge base, incomplete answers.

Order and Account Status

"Where is my package?" is the single most common support question for e-commerce companies. An AI agent connected to your order management system gives an instant answer: your order shipped on April 5, the tracking number is XYZ, estimated delivery is April 9. No human needed.

Same goes for account questions: subscription status, billing dates, usage limits, plan details. If the data exists in a system, the bot can retrieve it.

Appointment Booking and Scheduling

"I need to book an appointment for next Tuesday." The bot checks your calendar system, shows available slots, confirms the booking, and sends a confirmation email. This workflow used to require a phone call or email exchange. Now it takes 30 seconds in a chat window.

For service businesses (dental offices, consulting firms, repair companies), automated scheduling alone can justify the entire chatbot investment.

Lead Qualification

Before routing a prospect to your sales team, the chatbot can ask qualifying questions: What is your company size? What product are you interested in? What is your timeline? What is your budget range? By the time the conversation reaches a human, the rep already knows who they are talking to and whether the lead is worth pursuing.

We have seen chatbot-qualified leads convert at 2-3x the rate of unqualified form submissions. The bot filters out the tire-kickers before they consume sales time.

Multi-Language Support

A single AI chatbot handles conversations in dozens of languages without separate configurations. A Dutch company with German, French, and English customers does not need four separate support setups. The bot detects the language and responds accordingly.

This is not translation. The bot understands and responds natively in each language, including cultural nuances in phrasing and formality levels.

What AI Chatbots Do Not Handle Well

Being honest about limitations saves you from expensive disappointments.

Complex Complaints

"I have been a customer for 8 years, my last three orders were wrong, I spoke to someone last week who promised a resolution, and nothing happened." This requires empathy, context across multiple interactions, judgment about what compensation is appropriate, and possibly escalation authority. AI is not there yet.

The right approach: the bot recognizes complaint patterns and hands off to a human immediately, along with a summary of what the customer said. Fast escalation is better than a bot trying to handle something it cannot.

Emotionally Charged Situations

When someone is genuinely upset, they need to feel heard by a person. A bot that says "I understand your frustration" does not actually understand anything, and customers know it. Sentiment detection can identify when a conversation turns emotional and trigger a handoff, but the handoff itself needs to be seamless.

Situations Requiring Judgment

"Should I choose product A or product B for my specific situation?" If the answer depends on nuance, trade-offs, and understanding the customer's particular context, a bot will give a generic answer. Sales conversations, technical consultations, and strategic advice still need humans.

Anything Outside the Knowledge Base

An AI chatbot knows exactly what you teach it. If a customer asks about something not in the knowledge base, the bot either admits it does not know (good) or makes up an answer (very bad). This is called hallucination, and managing it is the single most important technical challenge in chatbot deployment.

The solution: configure the bot to only answer from verified sources and gracefully hand off when it is not confident. "I do not have specific information about that. Let me connect you with our team." That is a good outcome.

Deployment Options

Where your chatbot lives matters as much as what it knows.

Website Chat Widget

The most common deployment. A chat bubble in the corner of your website. Visitors click it, type a question, get an answer. Implementation takes hours, not weeks. The widget can be styled to match your brand, positioned on specific pages, and configured to proactively greet visitors after a set time.

WhatsApp and Messaging Apps

For many B2B and B2C companies, customers prefer messaging apps over website chat. A WhatsApp chatbot reaches customers where they already are. The bot handles the same questions and actions, just through a different channel. WhatsApp Business API makes this possible at scale.

In markets like the Netherlands and Germany, WhatsApp penetration is above 90%. Meeting customers on their preferred channel increases engagement significantly.

Voice Assistants

AI voice agents handle phone calls. The caller speaks naturally, the AI understands and responds with a natural-sounding voice. This is newer technology and not as mature as text-based chat, but it is improving fast. For companies that receive high volumes of phone inquiries (appointment bookings, order status, basic information), voice AI can deflect 40-60% of calls.

Internal Deployment

Not all chatbots are customer-facing. Internal chatbots help your own team find information faster. HR policies, IT troubleshooting, product specs, process documentation. Instead of searching through SharePoint or asking a colleague, employees ask the bot. Larger organizations see significant productivity gains from this approach.

The ROI Calculation

Let us put numbers on it.

Cost of Human Support

A full-time customer service agent costs EUR 35,000 to EUR 50,000 per year in the Netherlands (salary, benefits, workspace, tools). Each agent handles roughly 40-60 conversations per day. That is about EUR 3-5 per conversation.

Cost of AI Support

An AI chatbot handling the same volume costs EUR 500 to EUR 2,000 per month, depending on conversation volume and complexity. At 1,000 conversations per month, that is EUR 0.50-2.00 per conversation.

Realistic Scenario

A company receiving 2,000 support inquiries per month. Currently handled by 3 support agents. Deploy a chatbot that handles 70% of inquiries. That is 1,400 conversations automated. The remaining 600 go to humans, now needing 1.5 agents instead of 3.

Savings: roughly 1.5 FTE, which is EUR 52,500 to EUR 75,000 per year. Chatbot cost: EUR 12,000 to EUR 24,000 per year including setup and maintenance. Net savings: EUR 28,500 to EUR 63,000 per year.

Plus the chatbot works 24/7, responds in seconds, never has a bad day, and handles spikes without hiring temporary staff.

Beyond Cost Savings

The harder-to-measure benefits often matter more: faster response times (seconds vs. minutes or hours), consistent answers (no variation between agents), 24/7 availability (especially important for international customers), and data collection (every conversation generates insights about what customers ask and need).

When It Makes Sense for Your Business

A chatbot investment is justified when:

  • You handle more than 500 support conversations per month. Below that, the economics are thin.
  • Many questions are repetitive. If 40%+ of your inquiries are FAQ-type questions, a bot handles them easily.
  • Response time matters. If customers expect fast answers (e-commerce, SaaS, services), a bot delivers that consistently.
  • You operate across time zones or languages. A bot does not sleep and speaks every language.
  • You want to scale without proportionally scaling headcount. A bot handles 1,000 conversations as easily as 100.

It probably does not make sense if your support is already highly specialized (every conversation is unique and complex), your volume is low, or your customers strongly prefer human interaction for cultural or relationship reasons.

Getting It Right

The companies that get the most out of AI chatbots share a few things. They invest in the knowledge base. They set clear boundaries for what the bot handles versus what gets escalated. They measure deflection rate, customer satisfaction, and resolution accuracy. And they treat the chatbot as a living system that improves over time, not a one-time project you deploy and forget.

The technology is ready. The question is whether you implement it thoughtfully or just bolt on a chat widget and hope for the best. The difference between those two approaches is the difference between 30% deflection and 80% deflection. That gap is worth a lot of money.