BRUTAL MARKETING

CUSTOMER SERVICE CHATBOT: HOW TO IMPLEMENT IT WITH A CRM

2026
BRUTAL MARKETING

Customer Service Chatbot: How to Implement It with a CRM

2026

Customer Service Chatbots: How to Implement One Without Failing — A Practical Guide

A customer messages you on WhatsApp at 9:40 p.m. The bot replies in two seconds with a menu of eight buttons, and none of them match the question. The customer closes the chat and writes to a competitor. Your rep sees the message in the morning — if at all.

At Brutal Marketing, we see this in audits more often than we see a bot that actually works
Serhii Ponomarenko. Customer Service Chatbot: How to Implement It with a CRM I Brutal Marketing blog
Serhii
Ponomarenko
The technology isn't the problem: you can build a rule-based bot in an evening, and an AI agent answers almost like a person. Bots fail because companies launch them without analyzing real requests, without a handoff to a human and without a CRM connection. The result is one more channel where leads disappear.

Below: where a bot beats a person and where it hurts, how to pick the bot type and channel under the new WhatsApp, Viber and EU rules, and a seven-step launch plan. Owners get criteria for whether a bot is worth it; sales managers get scenarios, metrics and a checklist.

Why most chatbots fail — and it's not the technology

In most companies, a bot appears not because the process needs it, but because "our competitors have one." Our audits keep finding the same three causes.

Teams build the bot around a menu, not real requests

The team guesses what customers will ask and builds buttons for those guesses. Real questions turn out to be different. In our experience, 5–7 recurring questions cover 60–70% of inbound requests. To find them, export two to three months of conversations and count.

There's no way out to a human

The customer gets stuck in a "choose an option" loop and leaves. In a Gartner survey of 5,728 customers, 64% said they would prefer companies didn't use AI for customer service at all. Their top concern: it gets harder to reach a person. And 53% would consider switching to a competitor over it.

Customers don't hate bots. They hate dead ends.

The bot lives apart from the CRM

The bot collected a name, a phone number and a budget, but the data stayed in the chat. The rep asks again, the customer gets annoyed, and the manager can't see how many leads the bot brought in or how many bought. The bot becomes one more place where leads never convert into sales.

A chatbot doesn't replace your sales team, and it isn't a gimmick. It's the first stage of your funnel — design it like the rest: from data, with stage criteria and an owner at every step.
Tasks a chatbot handles better than a person | Customer Service Chatbot: How to Implement It with a CRM – Brutal Marketing

Tasks a chatbot handles better than a person

A bot wins where the task repeats, has a clear structure and needs speed. Here are the five tasks we hand to bots most often.

An instant first response, 24/7

Speed sells. Research published in Harvard Business Review found that companies that contacted a lead within an hour were nearly 7 times more likely to reach a decision-maker than those that responded even an hour later. A bot picks up the customer in seconds and holds the conversation until a rep is free. More in our guide to lead management.

Lead qualification

Three or four questions: the need, the volume or budget, the timeline, the city. Instead of a bare "hi," the rep gets a completed deal card. The bot routes irrelevant requests to a separate branch.

Recurring questions

Opening hours, delivery, payment, order status, returns. These are the same 5–7 questions that eat up your reps' time. Hand them to the bot, and your team sells instead of sending the same message for the twentieth time.

Follow-ups on unfinished requests

An abandoned booking, cart or quote. The bot reminds the customer in an hour, a day or a week — with no task cluttering the rep's calendar. More scenarios are in our overview of customer communication automation in a CRM.

Post-deal feedback

One question on a 1–10 scale, a day after delivery. The score lands in the customer record, and a low one creates a task for the manager. More in our piece on how to improve customer satisfaction with a CRM.

Where a chatbot will fail every time

When the customer expects judgment, empathy or flexibility, a bot won't just fail to help — it will do damage.

The five-step rule

If a scenario doesn't fit into roughly five steps with clear answers, it's too early to hand it to a bot. Simplify the process first — or leave it with a person.

What about AI agents?

AI agents push this boundary further: they understand free-form questions and answer from a knowledge base instead of a button tree. But a language model can confidently "promise" a discount or a deadline that no policy of yours contains. Anything involving money and company commitments stays with people.

How to choose a chatbot type: rule-based, NLP or AI agent

Choose the type for the task, not for the trend. Each of the three approaches fails in its own way.

What changed with AI agents

AI agents now come built into CRMs. The Kommo AI agent, for example, answers from uploaded documents, qualifies leads with your questions and hands off to a person by your rules or when the customer asks. It's a paid add-on available on all plans.

Gartner predicts that by 2029, agentic AI will autonomously resolve 80% of common customer service issues. Customer trust lags behind: in another Gartner survey, 54% of customers trusted a human more than AI for product recommendations, and only 32% trusted AI more.

Our recommendation: go hybrid

Scripts run structured flows where predictability matters: qualification, bookings, payments. The AI agent handles open questions from the knowledge base. Strict handoff rules sit on top of both. And remember: an AI agent is never smarter than your knowledge base. If prices and terms live in your reps' heads, the agent will invent them.

Where to launch your chatbot: WhatsApp, Instagram, Messenger, Telegram, Viber or website chat

The channel sets the rules of the game: what a message costs, when the bot may write first and which bots the platform allows at all.

How to choose your first channel

Don't launch everywhere at once. Start where most of your requests came from over the last three months. As a rule of thumb, WhatsApp leads in most of Europe, Latin America and India. Telegram and Viber dominate in Ukraine and much of Eastern Europe. Visual niches live on Instagram, and B2B usually wins with website chat.

Add the next channel once the first one runs smoothly — always into a single CRM inbox. See our pieces on multichannel customer experience in a CRM and customer service quality across communication channels.

Chatbot–CRM integration: why nothing works without it

A bot without a CRM is an auto-responder with buttons: polite, but it passes nothing down the funnel. In our projects, the conversion rate from bot conversation to qualified lead runs 25–35% higher with CRM integration than without it. The rep picks up where the bot left off and doesn't re-ask what the customer already said.

Five things the integration must do

  1. Create a contact and a deal — automatically, with a duplicate check by phone number or messenger handle.
  2. Pass the context. Qualification answers go into deal fields; the full chat history goes into the activity feed.
  3. Assign a task with a deadline — for example, 15 minutes during business hours. If the rep doesn't react, the system alerts the manager.
  4. Move the deal through stages. The bot has the data — the deal moves to "Qualified." The customer went silent — the deal enters a follow-up sequence.
  5. Record the source: channel, ad campaign, UTM tags. Without it, you can't tell how much money the bot brought in — the job of end-to-end sales analytics.

Which CRM to choose for your bot

If you sell mostly through messengers, look at Kommo CRM: a built-in Salesbot builder, an AI agent and chats from every channel in one deal card. For B2B with long deal cycles, Pipedrive works well; its LeadBooster add-on includes a chatbot, live chat and web forms. Online stores need a bot that sees orders, payments and shipping — here's how to choose an e-commerce CRM.

For the bigger picture, read about CRM for customer service and CRM as a customer management system.

How to implement a chatbot: 7 steps without the usual mistakes

We follow this sequence in every project. The technical work takes less than half the time; the rest goes into analysis, scenarios and testing.
  1. Analyze real requests. Export two to three months of conversations, sort them into categories and count the share of each. If the top 7 questions cover less than half of all requests, a fixed-script bot won't do much — consider an AI agent.
  2. Set one goal and one primary metric: qualification, FAQ answers or bookings. A bot "for everything" does nothing well.
  3. Write the scenarios and handoff points. Five steps at most per scenario, with a way out to a person at every step. Build the logic on the same principles as your sales playbook.
  4. Start with one channel — the one where most of your requests already come in.
  5. Integrate with the CRM: fields, stages, tasks and source.
  6. Test the edge cases — not just the "happy path" (see the list below).
  7. Soft-launch for two weeks. Turn the bot on only after hours or for part of your traffic. Read 10–20 conversations a day, fix the scenarios, then scale.

What to check before launch

  • The customer sends a voice note, photo or file instead of tapping a button
  • The customer types "human!", "operator" or "agent"
  • Two unrecognized replies in a row hand the chat to a person
  • A complaint or a sharp tone opens a high-priority task
  • A returning customer doesn't create a duplicate in the CRM
  • After hours, the bot honestly says when a rep will reply
  • A customer who returns a week later doesn't restart from scratch
  • For an AI agent: 50–100 real questions from past chats, each answer checked against your policies

What to measure after launch: the metrics that actually matter

Conversation counts and "reach" tell you nothing about revenue: a bot can run a thousand chats a month and close nothing. These are the metrics we put on client dashboards in the very first week.
These thresholds are benchmarks from our projects, not an industry standard. Record your own baseline before launch.

Where to see the numbers

Once you connect the bot to your CRM and tag sources and stages, most of these metrics already sit in its reports. See our guide to working with Kommo CRM analytics. An owner needs three numbers on one screen; a sales manager needs a breakdown by step and by rep. Both levels fit into sales team dashboards.

Chatbots by industry: what works in practice

Everywhere, the bot takes the routine and people make the decisions. The routine differs by industry.

Online stores: a bot without order data is useless

The top question in e-commerce is "Where's my order?" A bot can answer it only if it sees order statuses and tracking numbers in the CRM; otherwise it just forwards the customer to a rep. More in CRM for online stores and closed-loop sales.

B2B: the bot doesn't sell, it screens

Nobody buys B2B in a five-minute chat. The bot filters out poor fits and brings good ones to a call with a rep, deal card already filled in. See our guide to building a B2B messaging strategy; for solar companies, CRM for solar business.

Six implementation mistakes — and how to avoid them

We see all six regularly, from small businesses to companies with 20-person sales teams.

1. No way out to a human

The customer can't reach a rep and leaves frustrated. The fix: a "Talk to a person" button at every step and an automatic handoff after two unrecognized replies.

2. Scenarios that run too long

Ten questions before the bot names a price — and the customer leaves at question four. Keep only the questions whose answers change the rep's next action.

3. A bot pretending to be human

A name like "Emma," a stock photo and a fake "typing…" indicator. Customers see through it within three messages and stop trusting everything you say next.

It's now a legal risk too. Article 50 of the EU AI Act, already in force, requires you to tell people they are interacting with AI unless it's obvious from the context. Fines reach €15 million or 3% of worldwide annual turnover. In the US, California's bot disclosure law bans using an undisclosed bot to mislead people about its artificial identity to drive a sale. The fix: an honest "I'm a virtual assistant, and I can connect you with a person anytime" in the first message.

4. Launching without testing

Two employees who know the right answers tested the bot, but real customers write differently. Run the pre-launch checklist on people who have never seen the bot.

5. "Launch it and forget it"

Prices, products and delivery terms change, but the bot keeps answering with old data. Assign an owner who reviews 20 conversations and the metrics every week.

6. An AI agent with no guardrails

Someone gives the agent the website and says "answer customers." A week later, it promises next-day delivery to places you ship to in a week. Give the agent a verified knowledge base, a list of forbidden topics (prices outside the price list, discounts, legal questions) and a mandatory handoff whenever the knowledge base has no answer.

Conversational marketing and chatbots: the link most teams miss

Most companies treat a bot as a support tool. It's also an entry point into sales and the core of conversational marketing: the customer gets an answer in a conversation instead of filling in a form and waiting for a call. A bot runs these conversations with hundreds of customers at once, with no extra hires.

Where the bot works for marketing


All of this works on one condition: marketing, the bot and the sales team see the same customer record. Otherwise, the bot offers a first-purchase discount to someone who placed their third order yesterday.

When a chatbot pays off — and when it doesn't

A chatbot pays off where you have a steady flow of similar requests and a process to plug it into.

Signs you need a bot

  • 100+ inbound requests a month across messengers and chats
  • Reps send the same replies several times a day
  • First response takes over 10–15 minutes during business hours
  • Evening and weekend requests wait until morning
  • You have a CRM or are ready to implement one
  • Someone will own the bot after launch

Four or more checks — the bot will pay for itself within the first months. Two or three — start with a simple rule-based bot for after-hours requests.

A sample calculation

A company gets 300 requests a month, and 60% of them are typical questions. That's 180 replies at 4 minutes each, or 12 hours of a rep's time every month. Another 75 leads (25%) arrive in the evening and wait until morning. The bot closes both gaps: it frees up a day and a half of a rep's work and catches evening leads while they're still warm.

When a bot won't help

A bot can't patch a missing sales process. If reps don't know what to do with a qualified lead, the bot just helps them lose leads faster. First systematize your lead management, then automate the start of the process.

It's also too early for a bot if you get fewer than 30–50 requests a month or every request differs from the last. In those cases, a response-time standard for reps and CRM reminders will do more. Not sure you need a CRM at all? Read why your business needs a CRM.
We at Brutal Marketing will select the best CRM program for you to use in your business. We will be happy to tell you about the program's capabilities and show you which settings will exactly help you achieve the desired financial results.

Frequently Asked Questions

Can a chatbot fully replace customer service reps?

No. A bot takes on typical questions, the first response and qualification; negotiations, complaints and complex deals stay with people. Reps spend the time they get back on conversations that bring in money.

Do I have to integrate the chatbot with a CRM?

If the bot serves sales, yes. Without a CRM, chat data never reaches the deal card, the rep gets no task, and you can't see how many deals the bot brought in. An FAQ-only bot can run on its own, but it won't move revenue.

At which funnel stage does a chatbot add the most value?

At first contact and qualification, where speed decides the outcome and tasks repeat the most. The second strong stage comes after the sale: order status, feedback, repeat-purchase reminders.

Do chatbots work in B2B?

Yes, as a screener. The bot collects company size, the task and the timeline, then books a call or a demo, so the rep comes to the conversation prepared.

How much does a customer service chatbot cost?

It depends on the channel. The Telegram Bot API is free. Viber charges €115 per bot per month. WhatsApp charges for template messages, while replies within the 24-hour service window are free. Add the CRM or bot-builder license, an AI add-on if you need one, and the work on scenarios — usually the largest cost.

Do I need to tell customers they're talking to a bot?

Yes. It's honest, it prevents disappointment, and for customers in the EU, Article 50 of the AI Act requires it. One sentence in the first message and a button to reach a person are enough.

How long does a launch take?

A rule-based bot with CRM integration takes 1–2 weeks; an AI agent takes 2–4 weeks, mostly for knowledge base prep. Add two weeks of soft launch to refine the scenarios on real conversations.

What are the main risks of implementing a chatbot?

Customers who can't reach a person, an AI agent that invents terms, and chat data that never reaches the CRM. You close all three at the design stage: handoff points, a verified knowledge base and integration before launch. Also mind personal data: link to your privacy policy and comply with GDPR if you serve EU customers.

Get an audit of the automation points in your sales team

We don't sell chatbots for the sake of chatbots. First, we map how your requests move today: where they come from, where they wait for a reply and where they get lost. Then we tell you honestly whether a bot will solve the problem — or whether you need to fix the process first.

What you get after the audit:
  • a map of your requests with the top questions and their share of total volume;
  • the scenarios to hand to a bot and those to keep with people;
  • a recommendation on the channel, bot type and CRM integration;
  • a launch plan with the metrics that will show you the result.

Leave a request on our CRM implementation page — we'll review your case and give you specific recommendations, not generic advice. See how this worked for other companies in our case studies.
customer service chatbot, chatbot for customer service, AI chatbot for customer support, chatbot CRM integration, WhatsApp chatbot for business, chatbot for small business | Brutal Marketing blog | Customer Service Chatbot: How to Implement It with a CRM
By submitting an application, you agree to the privacy policy
Join our community at Telegram and WhatsApp