Iris · Service Desk Assistant
IT · Custom implementation
Automate your IT service desk with AI
Resolves recurring IT tickets, gathers what a specialist needs and escalates the rest.
Connects toA forgotten password, no access to a folder, a printer that will not print, an account still open after someone has left. Much IT work is the same every week, and it interrupts the very people who need time for the difficult work.
An AI employee for IT handles what runs on fixed procedures, gathers what a specialist needs for the rest and keeps track of what is still open. By default, access to sensitive systems and admin rights stay with a person.
Iris · Service Desk Assistant
IT · Custom implementation
Resolves recurring IT tickets, gathers what a specialist needs and escalates the rest.
Connects toPeter · Access Manager
IT · Custom implementation
Handles accounts and permissions for joiners, movers and leavers, and flags access nobody needs any more.
Connects toMicrosoft 365AFASJasper · Outage Communicator
IT · Example application
Recognises when something is going wrong at scale, informs the organisation and keeps the status page up to date.
Connects toFemke · Licence Monitor
IT · Example application
Tracks which software is in use, what you pay for it and which licences nobody uses any more.
Connects toMicrosoft 365ExactDatabasesThese AI employees sit with another department, but touch the same work.
This is the starting point for each task. Exactly where the line sits for your team, we agree together during setup.
Runs automaticallyHandles recurring tickets according to your procedures and gathers what a specialist needs for the rest.
A person decidesComplex incidents and access to sensitive systems. A password reset only after verification.
Runs automaticallyLinks joiners and leavers to accounts and rights, and sets up standard access according to your role matrix.
A person decidesSensitive systems, admin rights and what happens to the accounts of people who have left.
Runs automaticallyRecognises the pattern in tickets, drafts an outage message and links new tickets to the outage.
A person decidesApproval to publish, especially when customers can read along.
Runs automaticallyCompares licences with actual use and invoices, and flags renewals in good time.
A person decidesCancelling and negotiating with suppliers.
You stay in control.
Not every decision should be made automatically. For each workflow, we set out:
The AI employees on this page work with these packages, among others. Is your system not listed? We can connect any system, even if there is no standard integration.
Handling recurring first-line tickets according to your procedures, managing accounts and rights for joiners, movers and leavers, preparing outage communication when many people report the same thing, and comparing licences with actual use. Solving complex incidents stays with your specialists.
Technically it can, but it is a security decision. By default we put a verification step in front of it and agree per action what it may do on its own. Standard access according to your role matrix can be automatic; sensitive systems and admin rights always go past a person.
Yes. Tickets stay in your service desk tool, accounts and rights run through Microsoft 365, and joiners and leavers come from your HR system, such as AFAS. That way the history stays where you already keep it.
It helps you demonstrate access management: you get a log of who was given which access, when and on what grounds. Certification is of course broader than that.
Then an AI employee gives outdated answers. That is why maintaining the knowledge base is part of the implementation: which articles are used, which never are, and who keeps them current.