What are the risks of using Agentic AI in customer service, and how do you manage them in compliance with the AI Act?

Agentic AI poses specific risks in customer service related to autonomous decision-making, a lack of transparency, and potential violations of customer rights. The EU AI Act requires organizations that use Agentic AI in customer interactions to systematically manage these risks, ensure human oversight, and, in certain cases, maintain comprehensive compliance documentation. In this article, we answer the most frequently asked questions about Agentic AI in customer service and explain exactly what the AI Act requires of your organization.

What specific risks does Agentic AI pose in customer service?

Agentic AI in customer service carries risks that go beyond those of traditional chatbots or automated menu systems. Because Agentic AI makes decisions independently, takes action, and can act on its own without employee intervention, this increases the likelihood of errors that directly impact customers.

The main risks are:

  • Autonomous decisions without context: An AI agent handling a complaint or processing a request may sometimes miss the nuances that a human would pick up on, such as when dealing with a vulnerable customer or in an emotionally charged situation.
  • Lack of transparency: Customers do not always know that they are communicating with an AI system, which undermines trust and raises legal concerns.
  • Profiling and Discrimination: If Agentic AI analyzes customer behavior to determine priority or treatment, there is a risk that certain groups will be systematically disadvantaged.
  • Data Quality and Error Propagation: An autonomous agent that acts based on outdated or incorrect information may make false promises or mislead customers.
  • Loss of human oversight: The more tasks Agentic AI performs autonomously, the greater the likelihood that employees will lose track of what is being communicated on behalf of the organization.

These risks are not hypothetical. In sectors such as government, healthcare, and housing authorities—where customer contact has a direct impact on people—they carry even greater weight.

How does the AI Act classify agentic AI in customer service?

The AI Act defines four risk levels: unacceptable risk (prohibited), high risk (strictly regulated), limited risk (minimal transparency requirements), and minimal risk (unregulated). Agentic AI in customer service generally falls into the limited- or high-risk category, depending on what the system actually does.

Low-risk applications, such as an AI chatbot that answers questions or provides information, are subject to transparency requirements. The customer must be aware that he or she is communicating with an AI system. That sounds simple, but in practice, organizations often fail to implement this.

A high-risk classification is imminent as soon as Agentic AI:

  • Performing profiling of individual customers (always considered high risk under the AI Act);
  • Makes decisions regarding access to essential services, such as whether or not to transfer a call to emergency services or to assess a customer request with financial implications;
  • Is used in sectors covered by Annex III of the AI Act, including government and public services.

Prohibited practices also apply in full to customer service. Agentic AI may not use manipulative techniques that influence behavior without the customer’s awareness, nor may it exploit vulnerable groups based on age, disability, or socioeconomic status. These prohibitions have been in effect since February 2, 2025.

What requirements apply to high-risk AI systems used in customer interactions?

If your Agentic AI system is classified as high-risk, extensive obligations will apply starting August 2, 2026. Organizations acting as deployers—that is, those that deploy a third-party AI system—also bear a share of this responsibility.

The core obligations for high-risk AI are:

  • Risk Management System: An ongoing process that identifies, evaluates, and manages risks throughout the entire life cycle of the system.
  • Data quality requirements: Training and operational data must be relevant, representative, and as free of errors as possible.
  • Technical documentation: A comprehensive description of the system, its capabilities, limitations, and test results.
  • Logging and Traceability: The system must automatically maintain logs so that the decisions it has made can be reconstructed later.
  • Transparency for users: Customers and employees must understand how the system works and what decisions it makes.
  • Human oversight: There must be mechanisms in place that allow people to monitor, correct, and, if necessary, shut down the system.
  • Fundamental Rights Impact Assessment: For certain applications, a formal assessment of the impact on fundamental rights is required.

As a deployer, you are also required to provide adequate training to employees who work with the AI system and to report serious incidents to the competent authority.

How do you ensure human oversight of autonomous AI agents?

You can ensure human oversight at Agentic AI by intentionally building in intervention points, defining clear escalation paths, and actively involving employees in monitoring AI behavior. The AI Act explicitly requires this for high-risk systems, but it is also a best practice for lower-risk applications.

In practice, this means the following:

  • Define the limits of autonomy: Determine which actions the Agentic AI is permitted to perform independently and in which situations a human must always be involved, such as complaints about service, financial decisions, or emotionally charged conversations.
  • Build in escalation mechanisms: Ensure that the AI agent can detect on its own when a situation is beyond its scope and seamlessly hand it off to a staff member, including the full conversation history.
  • Actively monitor for anomalies: Use dashboards and logging to see if the AI agent is behaving as expected. Unexpected patterns, such as a sudden spike in escalations or low customer satisfaction scores, are early warning signs of problems.
  • Train employees in AI literacy: The AI Act requires organizations to promote AI literacy starting February 2, 2025. Employees must understand how the AI agent works, what its limitations are, and how they can intervene.

Human oversight is not an afterthought, but a structural component of a responsible Agentic AI system. An AI agent that operates completely autonomously without any form of human oversight does not meet the requirements of the AI Act.

What are the consequences of non-compliance with the AI Act?

Non-compliance with the AI Act can result in substantial fines, reputational damage, and the shutdown of AI systems. The fine structure is tiered and will take full effect on August 2, 2025.

The three stages of penance are:

  • Violation of prohibited practices (Article 5): Up to 35 million euros or 7% of global annual revenue, whichever is greater.
  • Non-compliance with other obligations: Up to 15 million euros or 3% of global annual revenue.
  • Inaccurate or misleading information provided to authorities: Up to 7.5 million euros or 1% of global annual revenue.

For medium-sized organizations, the lower of the percentage or the fixed amount applies, which somewhat limits the financial impact. But even aside from fines, the consequences of non-compliance are very real: regulators can order AI systems to be shut down, customers can take legal action, and reputational damage in sectors such as government and healthcare is difficult to repair. In January 2026, Finland became the first member state to grant formal enforcement powers to its national authority, a sign that enforcement is becoming a reality.

What steps are you taking to implement Agentic AI in compliance with the AI Act?

In accordance with the AI Act, you implement Agentic AI in customer service by starting with a clear risk classification, followed by establishing the required governance, documentation, and oversight mechanisms. A structured approach prevents you from having to fix later on what went wrong during the initial setup.

Follow these steps:

  1. Map out its usage: What exactly does Agentic AI do? What decisions does it make? What data does it use? This forms the basis for risk classification.
  2. Determine the risk category: Does the system fall under “limited risk” or “high risk”? Does it perform profiling? Does it impact access to essential services? Document your reasoning.
  3. Prepare technical documentation: Describe the system, how it works, its limitations, test results, and the measures you have taken to manage risks.
  4. Set up logging: Ensure that the system automatically tracks which decisions it makes, when, based on what input, and with what result.
  5. Define human oversight: Specify who is responsible for monitoring, how the escalation process works, and how to shut down the system if necessary.
  6. Train your employees: Foster AI literacy throughout the organization. Employees who work with the AI agent need to understand how the system works and what their role is.
  7. Establish transparent communication: Always inform customers that they are communicating with an AI system, especially in low-risk applications.
  8. Schedule periodic reviews: The AI Act requires ongoing risk management. Schedule regular times to review the system and update the documentation.

How Pegamento Helps Implement Responsible Agentic AI in Customer Service

We at Pegamento understand that the combination of Agentic AI and regulations such as the AI Act raises many questions. Especially for organizations already struggling with fragmented systems, staff shortages, and increasing customer volumes, it’s tempting to postpone addressing these risks. But that’s exactly where things go wrong.

Our AI-driven intelligence was built from the ground up with human oversight as a guiding principle. What we offer:

  • Risk Classification as a Starting Point: We’ll help you determine which category your use of Agentic AI falls into and what that means in practical terms for your obligations.
  • Built-in escalation routes: Our Agentic AI assistants are designed to seamlessly hand off conversations to agents, including the full context of the conversation, so customers don’t have to repeat themselves.
  • Transparency by design: Customers always know when they are communicating with an AI agent, in accordance with the transparency requirements of the AI Act.
  • Logging and reporting: All interactions are logged and can be viewed via central dashboards, so you can always account for what the system has done.
  • Everything under one roof: From implementation to management and compliance support, you have a single point of contact instead of multiple vendors that aren’t coordinated.
  • Built on proven modules: No costly custom development, but a smart combination of proven building blocks that we tailor to your situation and industry.

We are ISO 27001 certified (information security), supplemented by ISO 9001 and ISO 26000, which means that compliance and quality are structurally embedded in our operations—not something you have to add as an afterthought. Would you like to know how your organization can use Agentic AI responsibly and in compliance with the AI Act? Contact us, and we’d be happy to work with you to find a solution.

Frequently Asked Questions

Does the AI Act apply even if we purchase an Agentic AI system from a third-party vendor rather than developing it ourselves?

Yes, even as a deployer—the party that deploys a third-party AI system—you have obligations under the AI Act. You are responsible for the proper use of the system, training employees, and reporting serious incidents. It is therefore essential to check with your supplier to see what technical documentation and declarations of conformity are available, and to specify in the contract who is responsible for what.

How do I know if my current Agentic AI system already complies with the transparency requirements of the AI Act?

At a minimum, verify that customers are clearly informed at all times that they are communicating with an AI system—this applies from the very first interaction and also to automated emails or chat messages. Also check whether the system offers customers the option to switch to a human agent. If this option is not actively enabled, it constitutes non-compliance with the transparency requirements that are already in effect.

What is the difference between an AI chatbot and Agentic AI, and does that matter for AI Act classification?

A traditional chatbot follows fixed scripts and provides predetermined responses, while Agentic AI makes independent decisions, performs actions within systems, and can take the initiative. This difference is crucial for the AI Act: the greater the autonomy and impact on the customer, the higher the likelihood of a high-risk classification. A chatbot that only provides information is generally classified as low risk, but an AI agent that processes customer requests, updates files, or assigns priorities can quickly be classified as high risk.

What should I do if my Agentic AI system makes a mistake that has harmed a customer?

Document the incident immediately and in full using the designated logging system, and use the audit trail to investigate which decision the system made and based on what input. For high-risk systems, you are required to report serious incidents to the competent national authority. Additionally, ensure a remediation process for the affected customer and evaluate whether adjustments to the system or the autonomy limits are necessary to prevent recurrence.

How often should I review my risk classification and documentation after the initial implementation?

The AI Act requires ongoing risk management, which means your documentation must remain up to date with every significant change to the system, the data used, or the context of use. As a practical guideline, many organizations conduct at least one formal evaluation per quarter, supplemented by ad hoc reviews in response to system changes, new use cases, or notable anomalies in the monitoring data. Schedule these review periods in your governance calendar so that compliance becomes a structured process rather than a one-time activity.

Are there any exceptions or relaxed requirements for small organizations or nonprofit institutions?

The AI Act provides some relief for small and medium-sized enterprises (SMEs) and startups, such as lower fixed fine amounts, with the lower of the percentage or the fixed maximum applying. For nonprofit organizations, there are no structural exceptions to the substantive obligations—the system’s risk category and the impact on customers determine the requirements, not the organization’s legal form. However, regulators may take an organization’s size and resources into account when enforcing the law.

How do I handle Agentic AI in customer service if my organization operates in multiple EU countries?

The AI Act is an EU regulation that applies directly in all member states, so the core obligations are the same everywhere. However, national regulators—such as the Finnish authority mentioned earlier—may have their own enforcement priorities and reporting procedures. Make sure you know which national authority has jurisdiction in each country where you operate, align your incident reporting procedures accordingly, and take into account any additional sector-specific legislation—such as in healthcare or financial services—which may vary by member state.

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!