How will the AI Act affect customer service departments?

The AI Act has direct implications for customer service departments that use AI tools for customer interactions, automation, or decision-making. Depending on how you use AI, you’ll be subject to either light transparency requirements or stricter requirements for high-risk systems. In this article, we answer the most frequently asked questions about what the AI Act means for customer service and how to properly prepare your organization.

Which AI applications in customer service are covered by the AI Act?

Most AI applications in customer service fall under the “limited risk” or “minimal risk” categories under the AI Act. Examples include chatbots, virtual assistants, and automated email processing. These systems are largely unregulated, but they must comply with transparency requirements whenever they communicate with people.

In practical terms, this means that a chatbot or voice-based AI assistant must always clearly inform users that they are communicating with an AI system and not with a human. This will take effect on February 2, 2025, as the transparency requirements are already in force.

However, there are situations in which customer service AI does fall into the high-risk category. This is the case when the system:

  • Profiling individual customers to make decisions about access to essential services, such as credit or insurance
  • Automatically determines whether someone is eligible for a service or product based on personal characteristics
  • Used for emergency calls or urgent services where errors have direct consequences for safety
  • Emotion recognition applied in the workplace, for example, to monitor employees

AI systems that perform only routine tasks, such as forwarding messages or retrieving information from a knowledge base, generally fall outside the high-risk definition. However, as soon as a system makes independent decisions that directly affect customers, the classification changes.

What are the requirements for high-risk AI in customer interactions?

If an AI system used in your customer service is classified as high-risk, significantly stricter requirements apply. The most stringent requirements fall on the system provider, but as the deployer—the organization that implements the system—you also have clear responsibilities.

Requirements for Providers of High-Risk AI

Companies that develop and market high-risk AI systems must, among other things:

  • Establish a continuous risk management system throughout the system’s entire lifecycle
  • Maintain technical documentation in accordance with the requirements of Annex IV of the AI Act
  • Enable automatic event logging
  • Systematically incorporate human oversight into the system’s design
  • Apply for CE marking and a declaration of conformity
  • Registering the system in the European AI database

Requirements for Deployers in Customer Service

If your customer service department deploys a high-risk AI system from a third-party vendor, you are the deployer. Your obligations are more limited, but they are not without responsibility:

  • Use the system as specified by the provider
  • Assign human supervision to qualified and trained employees
  • Retain logs for at least six months
  • Informing employees about the use of the AI system before it is put into use (Article 26(7))
  • Conduct a data protection impact assessment (DPIA) where applicable

In addition, under Article 86, customers have the right to request an explanation of decisions made about them by a high-risk AI system. So make sure you are able to provide that explanation.

When must a customer service department comply with the AI Act?

The AI Act will be implemented in phases. For customer service departments, three dates are most relevant. The prohibited practices and the AI literacy requirement will take effect on February 2, 2025. The requirements for high-risk systems will become fully enforceable on August 2, 2026.

Here is the specific timeline:

  1. Effective February 2, 2025: Prohibited AI applications are no longer allowed. Examples include manipulative techniques, emotion recognition in the workplace, and social scoring. The AI literacy requirement is also in effect, which means that employees must have a basic understanding of AI.
  2. Effective August 2, 2025: Requirements for providers of General Purpose AI (GPAI) models are in effect. Fines may already be imposed.
  3. Effective August 2, 2026: Most requirements for high-risk Annex III systems will become enforceable. This is the date by which customer service organizations that use high-risk AI must be fully compliant.

So don’t wait until 2026 to get started. Setting up an AI registry, assessing your systems, and training employees takes time. Organizations that are already taking action now will be in a much stronger position down the road.

How does the AI Act differ from the GDPR for customer service teams?

The AI Act and the GDPR complement each other but address different risks. The GDPR protects personal data and regulates how it is processed. The AI Act regulates AI systems themselves, regardless of whether they process personal data. For customer service teams, this means you must apply both frameworks in parallel.

A few specific differences:

  • Scope: The GDPR applies to all processing of personal data. The AI Act applies specifically to AI systems and their impact on people, even when no personal data is involved.
  • Risk Model: The GDPR is based on the principles of data minimization and purpose limitation. The AI Act uses risk levels to determine how strict the requirements are.
  • Transparency: Both laws require transparency, but the AI Act adds a specific requirement: users must know when they are interacting with an AI, even if no personal data is being processed.
  • Overlap in DPIA: For high-risk AI that also processes personal data, both an AI Act compliance assessment and a GDPR DPIA are required. These processes may overlap, and you can combine them effectively.

For the day-to-day operations of a customer service department, this means: the GDPR compliance measures you’ve already put in place are a good foundation, but they’re not enough. The AI Act requires additional documentation, risk assessments, and governance specifically related to your AI systems.

What do customer service representatives need to know about AI transparency?

Customer service representatives must understand that the AI Act establishes two types of transparency requirements: transparency toward customers and transparency within the organization. Both are relevant to day-to-day work practices.

When it comes to customers, any AI application that communicates directly with people must identify itself as AI. A chatbot that conducts conversations, a voicebot that handles incoming calls, or a system that sends automated emails must clearly indicate this. Employees who receive complaints about AI interactions must know how to handle them properly and where customers can exercise their rights.

The AI literacy requirement (Article 4) is already in effect. This means that organizations must train their employees in the basics of AI: what it is, how it works, and what its limitations are. Employees do not need to become technical experts, but they must:

  • Understanding which AI systems they use every day
  • Knowing When an AI Decision Requires Human Oversight
  • Being able to accurately inform customers about the use of AI in customer interactions
  • Recognizing signs that an AI system is producing inaccurate or biased results

Automation bias—the blind reliance on AI recommendations without critical thinking—is a specific risk that the AI Act aims to address. Employees must be trained to view AI as a tool and not as an infallible decision-maker.

How do you prepare a customer service department for the AI Act?

Preparing for the AI Act starts with a clear overview of all the AI systems you use. Without that inventory, you won’t know which obligations apply to you. A structured four-step approach will help you get started.

  1. Create an AI registry: Document all the AI systems you use, including their purpose, vendor, and the role your organization plays (deployer, provider, or something in between).
  2. Classify your systems: Determine the risk level for each system. Most customer service tools fall under the “limited” or “minimal” risk categories, but be sure to verify this explicitly for systems that make decisions about customers.
  3. Review contracts with suppliers: Ensure that suppliers of AI systems fulfill their obligations as providers. Request technical documentation, user manuals, and information on how human oversight is built into the system.
  4. Train your employees: Invest in AI literacy for everyone who works with AI systems. This is not only a legal requirement, but also a way to improve the quality of your customer interactions.

Organizations that use multiple providers for phone services, chat, WhatsApp, and email are at greater risk of compliance gaps. If systems do not communicate with one another and there is no central overview, it is also virtually impossible to properly implement AI Act requirements such as logging and human oversight.

How Pegamento Helps Ensure AI Act Compliance in Customer Service

As a customer service department, you want to use AI to better assist customers, not to get bogged down in compliance issues. We help organizations achieve both goals at the same time: smart AI implementation that also complies with the requirements of the AI Act.

Our Agentic AI for customer service goes beyond traditional automation. Whereas classic RPA bots follow instructions, our Agentic AI assistants take the initiative on their own: they think along with you, act proactively, and scale up when necessary. We don’t do this with expensive custom solutions, but with a smart combination of proven standard building blocks that we configure to fit your situation.

Here’s what we specifically offer to help you prepare for the AI Act:

  • Transparent AI systems that identify themselves to customers, in accordance with transparency requirements
  • Built-in human oversight, so employees can always take control
  • Logging and reporting on all customer contact channels from a single central platform
  • Support for classifying AI systems and preparing documentation
  • Everything under one roof: from implementation to management and support, without a complex supplier structure

We are ISO 27001-certified for information security, supplemented by ISO 9001 and ISO 26000, which means that compliance and quality are systematically ensured at our company. Would you like to know how your customer service department is currently performing and what it takes to operate in compliance with the AI Act? Contact us, and we’d be happy to help you figure it out.

Frequently Asked Questions

What happens if my organization does not comply with the AI Act?

In the event of non-compliance with the AI Act, regulators can impose substantial fines. For violations of the most serious obligations, such as the use of prohibited AI practices, fines can reach up to 35 million euros or 7% of global annual revenue. For less serious violations, such as failing to comply with transparency obligations, the fines are lower but still significant: up to 15 million euros or 3% of revenue. In addition to financial penalties, you also risk reputational damage among customers who are becoming increasingly aware of their AI rights.

How do I know if an AI tool from a third-party provider is AI Act-compliant?

Explicitly ask your provider for technical documentation, a statement of compliance, and information on how human oversight is built into the system. For high-risk systems, providers are required to provide this documentation in accordance with Annex IV of the AI Act. Also verify whether the provider has registered the system in the European AI database and whether clear instructions for use are available. If a supplier is vague about this, that is a significant red flag to be critical about the partnership.

My organization uses a chatbot that sometimes uses human names. Is that allowed?

No, this violates the transparency requirements of the AI Act, which have been in effect since February 2, 2025. An AI system that communicates with people must always clearly indicate that it is an AI, even if it has a human name or personality. This applies to chatbots, voicebots, and automated email systems. Adjust your chatbot’s settings so that, at the start of every conversation, it explicitly states that the customer is communicating with an AI assistant.

How do I handle customers who ask for an explanation of an AI decision?

Under Article 86 of the AI Act, customers have the right to request an explanation of decisions made about them by a high-risk AI system, such as a rejection based on an automated assessment. Ensure that your customer service representatives know which AI systems make high-risk decisions and that they have access to the information needed to explain those decisions. Establish internal procedures for how this process will be handled and who is responsible for responding to such requests.

Does the AI literacy requirement also apply to employees who use AI only indirectly?

The AI literacy requirement (Article 4) applies to all employees who work with AI systems, even if only indirectly. Think of a team leader who reviews reports generated by AI, or an employee who processes customer files that have been pre-sorted by AI. The level of training does not have to be the same for everyone: employees who actively use AI on a daily basis need more in-depth knowledge than colleagues who only have indirect contact with it. Tailor the training program to the extent of AI use for each role.

What is an AI registry, and how do I start creating one?

An AI registry is an internal document in which you record all AI systems within your organization, including their purpose, vendor, risk level, and the role your organization plays. Start simple: make a list of all the tools you use for customer contact, automation, or decision-making, and note for each tool who the provider is and what the system actually does. Then, for each system, add the risk level based on the AI Act categories. This register is not only useful for compliance but also for internal governance and supplier management.

As a deployer, do I need to take any action if my AI supplier ceases operations or makes significant changes to the system?

Yes, as a deployer, you are responsible for ensuring the continuity and proper functioning of the AI system you deploy. If a supplier makes significant changes to the system, you must reassess whether the system still meets the AI Act requirements and whether the risk classification is still accurate. Ensure that contracts stipulate that suppliers inform you in a timely manner of any significant changes, updates, or the discontinuation of the system. This will help you avoid unexpected compliance gaps and allow you to take alternative measures in a timely manner.

More blogs

Download the white paper here

Deepen your knowledge with Pegamento’s white papers.

Joost Schaap-Account manager Pegamento

Joost Schaap

Senoir Account Manager

When a customer contacts an organization because they have a complaint, it is crucial that the employee of the organization begin by listening carefully. What does this complaint mean for the customer and also for their own organization? How can this complaint be resolved? After listening carefully the employee needs the right information so that a solution can be offered.

This piece was written by Joost Schaap, working as an Account Manager at Pegamento.

Tim Treurniet-AI developer Pegamento

Tim Treurniet

Designer of Intelligent Systems

Real childhood heroes I never had. But in retrospect, I believe figures like Willie Carrot or Dexter’s lab may have had an influence on me. I get energy from actually making innovative and useful products myself. Nothing like seeing the effect of a project that automates a boring task, or makes a complex process suddenly accessible.

A nice bridge to my photograph is the physical aspect of my work. By working with image recognition, I am often very directly connected to the physical world and my work is more than just programming. For example, our image recognition software ensures safety on bridges, tracks players on a soccer field or uses your own smartphone to accurately measure yourself. This combination between physical and digital provides variety and extra challenge. For me, these are the main reasons for my interest and enthusiasm in what I do!

This piece was written by Tim Treurniet, employed Designer of intelligent systems at Pegamento.

Vera van der Plas-UI-UX designer

Vera van der Plas

UI/UX Designer

As a UX/UI designer, I deal daily with transforming complex data into user-friendly visualizations. All of this topped off with a digital lick of paint which should attract the visitor’s attention to take action.

One of the interesting aspects of this field I find the effects that small tweaks, both textual and visual, can have on conversion. The psychological impact that a simple background color of a CTA button has on our behavior is huge. After all, that color can determine whether or not you are going to buy that product.

What we see and how our brains process and interpret this information fascinates me. The possibilities of subconsciously pointing potential customers in your chosen direction are endless. I hope to apply my expertise more often within our solutions in the future.

This piece was written by Vera van der Plas, working as a UX/UI Designer at Pegamento.

Fouad Rahaoui-Finance Pegamento

Fouad Rahaoui

Financial Controller

A Financial Controller within a company should not only be an expert in Finance. You must also have knowledge of the latest IT developments. Because these are also moving very quickly in the world of Finance.

At Pegamento, I can learn all about the latest IT developments. Like the latest development in the field of Machine learning and deep learning.

Through these application areas, as Financial Controller, I can further automate the financial business processes within Pegamento and implement improvements for the automatic processing of financial data.

This piece was written by Fouad Rahaoui, working as a Financial Controller at Pegamento.

Ernst Vegter-Business consultant Pegamento

Ernst Vegter

Business Consultant

Hospitality is one of my deepest motivations.
Not surprisingly, of course, customer service is a common thread in my career. Aspects of hospitality is being able to connect, to facilitate but mainly to make someone feel genuinely welcome. My intuition is my greatest asset to be able to put myself in the shoes of a guest. A customer is my guest.

Fed by various senses, an image forms around the client. I listen to what is being said, watch facial expressions, taste the underlying tone and get a feel for the challenge to be addressed. An image literally forms on my retina. I have to be able to see it. If I can see it, I can create it.

In this, the trick is to pursue simplicity, give the client a warm feeling that the problem is understood, receive good advice, facilitated and carefully guided to the solution. Trust, connect and unburden.

The feeling when a guest arrives at your hotel after a long tiring journey, can sit in front of the fireplace, be handed a good glass of wine and stare carefree at the fire. My guest knows it will be okay.

This piece was written by Ernst Vegter, working as a Business Consultant at Pegamento.

Gunisch-AI developer Pegamento

Gunish Alag

AI Developer

A picture is worth a thousand words, is an expression most of us have heard. We see a lot of things around us on a daily basis and subconciously have the ability to recognize and understand them. This ability of humans to me seems bizarre.

As a computer vision developer at Pegamento that is what I do, break down complex problems and turn them into solutions using images by meticulously extracting useful data.
With the world moving forward and new technologies emerging, complicated problems which were difficult to solve a decade earlier suddenly seem possible and viable. The future is full of new challenges and I look forward to them.

This story is written by Gunish, working as an AI developer at Pegamento.

Ewold Jansen-Service engineer Pegamento

Ewold Jansen

Service & Support Engineer

Hearing the wishes a customer has or the problems a customer is facing is important in order to then be able to help them properly. In both cases, I help find the right solution.

When the customer comes to us with a desire, they don’t know what all the options are. In this I advise them to make the right choices. When problems arise, listening to them is important. For example, a problem arises from a wrong action. By communicating well in this, many problems can be solved quickly by explaining it well. Through poor communication, a small problem can become very big.

This piece was written by Ewold Jansen, working as a Service & Support Engineer at Pegamento.

Andre Glasbergen-Scrum master Pegamento

Andre Glasbergen

Scrum Master

After completing my studies, I started working as a developer at a young Pegamento with a lot of ambition and enthusiasm. In the first years I learned all about process automation, now better known as RPA. I often had to rack my brains to convert the work instruction into a logical function, with not too many If-statements, so that the robot could perform the work.

I developed further and went to work as a consultant. Listening well to the customer and supporting in the pre-sales phase of projects. Executing projects and listening suited me very well. It was a small, but logical, step to now work as a Scrum Master and Project Manager. I have been supervising projects for a few years now. Such as RPA, Cloud applications and AI, according to the Human lead agile approach, We build this with a large team of specialists.

This piece was written by André Glasbergen, working as a Scrum Master at Pegamento.

Ensar Ari-IT engineer Pegamento

Ensar Ari

IT Engineer

Good communication between customer and organization is very important. As an organization, you naturally want to be easily accessible to your customers. Either via social media channels or via the old familiar telephone. Often organizations do not know exactly how they want their telephone line set up. That is why I like to help them think along and give them ideas. I believe there is a solution to every problem. But sometimes you just need someone who looks at the situation a little differently.

This piece was written by Ensar Ari, working as an IT Engineer at Pegamento.

Nini Heerings-Chief Happiness Officer Pegamento

Nini Heerings

Chief Happiness Officer

“You get to know someone better by playing for an hour than by talking for a year.”

This quote from Plato is totally hitting home for me. That’s why I like to connect people through play. Because while playing, you are totally on, all your senses at work.
In my great role as Chief Happiness Officer, I want to do that by connecting colleagues with each other and with the organization. In a creative and playful way that suits Pegamento.

When I’m not at work, I also enjoy connecting people. I do this by organizing The Playground, where adults play games you used to play in the schoolyard, gymnasium or neighborhood playground. The pure feeling of fun, total relaxation and no thoughts of anything but playing. That feeling is the goal.

This piece was written by Nini, working as Chief Happiness Officer at Pegamento.

Ger Koedam-Communication & Marketing Pegamento

Ger Koedam

Marketing & Communications

How can I help you? That’s pretty much the first question I ask when talking to people who are curious about our services. In such a conversation, the use of senses is very important. Because not everyone is the same. One person thinks in images, while for another words are important or how something feels. For me, sight and hearing are the most beautiful senses, because both eyes and ears absorb information and can convey or process emotions.

Why hearing? Because listening is essential in contact. And it’s the key to unlocking valuable insights.

I developed this skill early on. As a child, I enjoyed radio plays on the radio, bringing the stories to life in my head.

Pim Ritmijer-Software developer Pegamento

Pim Ritmeijer

Software Developer

Programming is more than just “code knocking. For me, listening to what the customer wants and visualizing that is an important part of software development.

Actively listening to a customer to understand the customer’s full story is crucial before building a solution. When you understand a customer’s story, you can think together about a solution that truly helps the customer.

Visualizing solutions is the next step for me. What will be the route we will climb to get to a solution? What challenges are we going to face to get to the top?

Like climbing, good preparation is valuable. Even though you can’t prepare for everything, preparation helps make the application fit the client’s needs as well as possible.

What a beautiful and fascinating profession programming is.

This piece was written by Pim Ritmeijer, working as a Software Developer at Pegamento.

Denise Verhoef-Software developer Pegamento

Denise Verhoef

Software Developer

Hearing is something you do a lot of as a programmer but also thinking, for example, when you are tasked with putting together a customer need. If the customer wants a function for his application, it is important that as a programmer you think carefully about which functions are functional and which functions are not. In this way, you will put together the most functional application possible and the customer will have a good end product. Turning needs into code into functionality is something I find interesting.

I am currently doing an internship at Pegamento and studying Software Developer. I get a lot of information that you have to process and apply. The nice thing about this is that you can learn new things but also that you can experience how it works in real business. I started this training last year and knew nothing about programming beforehand. Now I can find my own way with programming and I enjoy working with it. That you can get from a blank page to a functional application through code is cool!

This piece was written by Denise Verhoef, working as a Software Developer intern at Pegamento.

Remco Pabst-Business consultant Pegamento

Remco Pabst

Computer Vision & AI Lead

Using innovative software technology for people or business to make “things” easier and smarter is really a driving force. That’s why the connection between the senses appeals to me the most. Our brains connect the senses just like a business process connects people, systems (data) and logic. They register and trigger an action, exactly how it should be in an optimal workflow. Very cool what is already possible today when we add a lot of computational power to that as well.

Hearing also means a lot. Not because I like to listen to Jazz, Soul, Deep House or Focus-like music every day AND have to be able to listen well to interpret a wish or pain point, but more because not everyone can have all the senses at their disposal. Think of him or her with a visual impairment. The fact that in close cooperation we were able to apply AI, TTS/STT technology (which is still in development) for this often underserved group of people in today’s digital world and to improve the interaction and experience with it gives me a lot of energy and meaning to what I try to do with technology; create value.

This piece was written by Remco, working as a Business Consultant at Pegamento.

Thomas de Wolf-Vision Engineer Pegamento

Thomas de Wolf

R&D Director

Once when I had to choose which study I was going to do, I had a hard time making that choice. I was interested in engineering, but what I most wanted to do was just work with a team toward a common goal.

To this day, that is still what I love doing most. The technology has become image recognition and the team the computer vision department of Pegamento. So it’s logical that in terms of sense, I end up with “seeing. By using our image recognition solutions to see things in the real world, our entire team solves relevant problems for our customers. And because of the variation in customers, the places where our solutions end up are never the same. For example, one moment I am in the control room of a bridge and the next day I am on a production line for sandwiches or between the fences of a TBS clinic.

This piece was written by Thomas de Wolf, working as a Computer Vision & AI Lead at Pegamento.

Rob Roode-Research Development

Rob Roode

Research & Development

Recognizing and automating patterns. Tasks we are constantly working on when implementing our robots at Pegamento. My 2 Drentsche Patrijshonden are hunting dogs and certainly not robots. The hunting instinct and intuition is basically in their genes. Continuing to offer new forms of training has taught them to recognize and act independently in hunting situations. Even “unsupervised,” even if I’m not around.

But when you try to teach a brain something, it also starts to see things you don’t expect. Dogs pick up on the slightest deviation in your voice or directions. To start recognizing that and correcting it again is perhaps the most complex challenge. But in our work, for the wonderful clients for whom we get to work, it often yields the most beautiful new insights!

This piece was written by Rob, founder of Pegamento and in charge of Marketing and R&D.

Serge Poppes-CEO Pegamento

Serge Poppes

CEO

Feeling. That’s the best thing Pegamento stands for. Feeling for technology in the broadest sense of the word. Not only feeling for the exciting stuff like AI, but also for the basics of communication.

The very best part of my job is selling, listening, translating and thinking about what really matters. We bring the digital transformation with a great team!
The diversity of our team, how sharp we are, but especially the wonderful things we get to make makes me feel extremely good. Hence, I intuitively chose the sense of “feeling.

Feeling gives life and differentiation!