An operations director handling 800 queries a month by email and phone has a very specific question: does a customer service chatbot help me or complicate my life? The answer is not automatically “yes”. It depends on the type of query, the volume, the preferred channel of your customers and whether your organisation is prepared to maintain the tool. In this article we break down the decision with practical criteria so you can assess whether it suits you and, if so, how to approach it.
What a modern chatbot does (and does not do)
Customer service chatbots have evolved enormously since the decision-tree systems that replied with canned messages. Current systems combine natural language processing (NLP) with the company's knowledge base to answer questions in free language, escalate to a human agent when they detect the query requires it, and log every interaction in the CRM.
What they do well:
- Resolving frequently asked questions immediately, without waiting: opening hours, order status, return conditions, required documentation.
- Qualifying the customer before passing them to an agent: finding out whether it is a billing issue, a technical incident report or a commercial information request.
- Handling queries outside business hours or during demand peaks without increasing headcount.
- Collecting structured data (order number, delivery address, product type) before a human intervenes, reducing average resolution time.
What they do not do well (yet):
- Managing complex complaints that require empathy and negotiation.
- Resolving situations where internal policy allows discretionary exceptions.
- Serving customers who explicitly prefer the phone and become frustrated by automated responses.
- Maintaining their usefulness if the company does not feed them with up-to-date information.
Market figures for 2025–2026
According to Salesforce's State of Service 2025 report, the majority of European consumers say they have interacted with a chatbot in the past year, but a significant proportion were not satisfied when the query required a real resolution. The gap between “having used a chatbot” and “having solved the problem” is the figure that should concern a company most before deploying one.
Meanwhile, Gartner forecast at the end of 2024 that by 2027, 40% of customer service problems will be resolved through consumer AI tools such as ChatGPT or device-integrated assistants — showing the growing pressure on corporate channels to deliver comparable resolution quality. In parallel, Gartner predicts that by 2029 AI agents will autonomously resolve 80% of common customer service issues without human intervention. The difference in resolution capability between decision-tree chatbots and AI agents is substantial.
In Spain, the ONTSI 2025 study on SME digitalisation notes that 22% of companies with between 10 and 250 employees already use some form of virtual assistant in customer service, compared with 11% in 2022. Growth is real, but more than three-quarters of mid-sized businesses have still not deployed one.
Variables that determine whether it is worth it
Before signing any contract with a provider, it is worth evaluating four levers:
1. Volume and type of queries
If your team handles fewer than 200 queries a month and most are complex or require access to very specific internal systems, the return on investment from a chatbot may be marginal. The usual inflection point is companies with more than 500 recurring interactions a month and a high percentage of repetitive questions. If 60% of calls or emails are variations of “when does my order arrive?” or “what documentation do I need for…?”, a well-trained chatbot can free up that 60% of the team's workload.
2. Your customers' preferred channel
A web chatbot works differently from a WhatsApp Business assistant, and both differ from a voice agent on the phone. Analyse where queries currently arrive. If 80% arrive by phone and your customers are over 55, the web or WhatsApp channel may not be the first to automate. Text chatbots on the web work particularly well in sectors with digital-native customers: e-commerce, SaaS, financial services and online education.
3. Availability of structured knowledge
The chatbot needs a knowledge base to answer queries. If your company has not documented its policies, prices, catalogues and procedures in an accessible and up-to-date way, the chatbot project will begin with a documentation phase that multiplies the time and cost. The chatbot does not create knowledge: it consumes it. A company without organised documentation must invest in that first.
4. Integration with existing systems
A chatbot that only answers generic questions has a low ceiling. Value increases when it can check the real status of an order in the ERP, verify a contract balance in the CRM or open a ticket in the support tool. That integration requires connectors or APIs and, depending on the architecture of your systems, can be straightforward or very costly. It must be evaluated before committing.
Comparison table: chatbot vs. human agent vs. hybrid
| Criterion | Human agent only | Chatbot only | Hybrid model |
|---|---|---|---|
| Hours of availability | Business hours | 24/7 | 24/7 (bot) + business hours (human) |
| Resolution capacity for simple queries | High, but with waiting | High and immediate | High and immediate |
| Handling of complex situations | Optimal | Limited | Optimal (escalates to human) |
| Cost per interaction at scale | Grows with volume | Low and stable | Low for the automatable portion |
| Personalisation and empathy | High | Medium-low | High in the human portion |
| Implementation time | Immediate (already exists) | 4–12 weeks | 6–14 weeks |
| Customer satisfaction (CSAT) | High if resources allow | Variable depending on training | High if routing is correct |
The practical conclusion drawn from any serious analysis is that the hybrid model consistently outperforms the extremes. The chatbot does not replace the human team: it filters and frees it to focus on what truly requires judgement.
Which types of company benefit most
Based on Summum IA's experience deploying conversational solutions in SMEs and mid-sized companies since 2007, the sectors where return appears fastest are:
- E-commerce and retail: the volume of order-status, returns and sizing queries justifies automation once a certain monthly turnover is exceeded.
- Financial services and insurance: balance queries, coverage, renewals and documentation are highly repetitive and easy to structure.
- Private clinics and health centres: appointments, pre-operative documentation, confirmations and reminders. The chatbot reduces phone congestion at peak hours.
- Service companies with maintenance contracts: opening job reports, confirming visits and queries about the status of interventions.
- Education and training: enrolments, deadlines, programme content, platform access and initial technical support.
By contrast, sectors where conversational automation encounters more friction are those working with unique, high-value queries (complex legal advice, architecture, bespoke engineering) or with customers who explicitly value human contact as part of the service.
How to measure whether your chatbot is working
A chatbot deployed without monitoring metrics is a cost, not an investment. The variables to track from the first month are:
- Containment rate: the percentage of conversations the chatbot resolves completely without escalating to an agent. A well-trained chatbot in a well-structured environment typically achieves 60–75% containment for FAQ-type queries.
- CSAT by channel: customer satisfaction after an interaction with the bot, separated from satisfaction with the human agent. If the bot's CSAT is systematically lower, the training or flow design needs reviewing.
- Time to first response: the chatbot should reduce this to zero in the channel where it operates.
- Conversation abandonment rate: if the user drops the conversation before receiving a reply, it signals that the flow is not well designed.
- Cost per resolution: divide the total cost of the tool (licence, maintenance, adjustment hours) by the number of cases resolved. Compare this with the equivalent cost of a human agent.
If you want to understand how to design and implement a customer service chatbot with business criteria, not just technological ones, at Summum IA we cover the complete project: from defining use cases to integration with your CRM and training the team that will manage it.
Considerations on the AI Act and GDPR for customer service chatbots
The European Artificial Intelligence Act (AI Act, Regulation EU 2024/1689) entered into force on 1 August 2024, but its application is staggered. The transparency obligations under Article 50 — which apply directly to chatbots and conversational assistants — became mandatory from 2 August 2026. AI systems that interact with people on behalf of a company must inform the user that they are talking to an automated system. This is not merely an ethical recommendation; it is a legal requirement carrying penalties of up to €15 million or 3% of global turnover.
In parallel, the GDPR requires the chatbot to inform users how the personal data they provide during the conversation (name, order number, contact details) is processed, that a legal basis for that processing exists, and that data is not retained longer than necessary. If the chatbot is integrated with the CRM, the company must ensure data flows with adequate safeguards.
For regulated sectors such as healthcare, banking or insurance, there are additional compliance layers worth reviewing before launching the bot publicly. At Summum IA we coordinate these aspects with our colleagues in AI Act technical compliance to ensure the chatbot meets regulatory requirements from day one.
Five signs your company is ready for a chatbot
- You have identified at least 20–30 frequently asked questions that your support team answers repeatedly.
- Your query volume exceeds 500 monthly interactions and the team faces demand peaks that are difficult to absorb.
- Your customers already use digital channels (web, WhatsApp, email) as their primary means of contact.
- You have (or can produce) a documented knowledge base: catalogue, prices, policies, procedures.
- You have an internal owner who can supervise and update the bot on an ongoing basis.
If you meet three or more of these conditions, the probability that a well-implemented chatbot will generate positive return in the first year is high. If you meet fewer than two, the most sensible step is to start by documenting and structuring your service processes before adding technology on top.
Frequently asked questions
How long does it take to deploy a customer service chatbot?
It depends on the complexity of the use cases and the integrations required. A FAQ chatbot without integration with external systems can be operational in four to six weeks. If it needs to connect to the ERP, CRM or ticketing platforms, the typical timeframe is eight to fourteen weeks. The first two or three months of operation always include training adjustments based on real conversations.
Does the chatbot replace customer service agents?
Not in most cases. The real goal is to free the team from lower-value queries so it can focus on more complex, urgent or commercially relevant ones. Companies that deploy a chatbot without realigning human team functions do not obtain the full benefit: the bot absorbs load, but the value materialises when that freed time is redirected to higher-impact tasks.
What happens if the chatbot cannot answer a question?
A well-designed chatbot has a clear escalation path: when it cannot find the answer or detects the query exceeds its capability, it transfers the conversation to a human agent with the context gathered up to that point. The customer does not have to repeat what they already said. That clean handoff is critical to prevent the experience from deteriorating. Configuring the escalation conditions correctly is one of the most important parts of the project.
Is it mandatory to inform the user they are talking to a bot?
Yes, under Article 50 of the AI Act, which became mandatory from 2 August 2026. Conversational AI systems must identify themselves as automated systems at the start of the interaction. Concealing that the interlocutor is a bot is an infringement of European regulation, as well as poor practice that can damage customer trust when discovered. The disclosure does not have to be cold or off-putting: it can be presented with your brand name and a defined personality, as long as its automated nature is clear.