You set the task and the trigger. Your agent does the rest, following your guidelines.
Payment reminders Trigger: Every Monday, 7:00 Done · 11 drafted Next run: Mon 7:00 
Minutes of the site call Trigger: After each Outlook meeting Done · sent to 6 Next run: Thu 10:30 
Weekly pipeline report Trigger: Every Friday, 16:00 Done · 12 deals Next run: Fri 16:00 
Sort new tickets Trigger: When a ticket arrives Running Next run: On new ticket Writing reports, collecting status updates and following up on open cases: these tasks are part of every day. Done by hand every time, they leave less time for customers, projects and decisions.
Choose which task your agent takes on and how often it runs. The workflow starts at the planned time. You can check the results and decide which actions need approval.
Payment remindersEvery Monday, 7:00done · 11
Minutes of the site callAfter each Outlook meetingsent to 6Weekly pipeline reportEvery Friday, 16:00next FriA workflow starts at a set time, when something changes in a connected system, or on request in the chat.
You see which information the agent used and what came out. If a run fails, the person in charge is told why.
An agent that uses your company knowledge and respects the access rights you already have.
Checks your systems, answers with the source and returns a finished draft.
Each team decides which tasks its agent takes on and what a good result looks like.
Every answer quotes its source, down to the page.
Describe how you talk once. eokit keeps to it from then on.
Dictate on site and get clean text in your company's tone.
500+ recurring tasks covered · permissions come from the source system
A change in a connected system can trigger a workflow. The agent processes the information and delivers the result where your team needs it.
Stephan Hostert CEO, Steffen Holzbau S.A. „When it comes to AI solutions, we could not be working with a better team than aigentcy, and we can not wait to have them work on a number of other valuable opportunities."
For companies that use AI responsibly
eokit is designed to be natively GDPR-compliant. It runs in the EU or inside your own network, and prompts are checked for personal data before they can go to an external model. We provide a data processing agreement and a list of subprocessors.
Trust centerWhere you choose to run eokit: in your own data centre, in our EU cloud in Germany or Luxembourg, or in your own cloud account. It is not copied to other regions.
Hosting optionsYes. You describe once how your company writes, and drafts follow that tone. You can also add your logo and colours.
Exactly the people who can open the document today. eokit uses the permissions from your directory and file systems, so people get answers only from documents they are allowed to open.
Your documents stay where they are, because eokit does not move them. We remove our components and can hand over your activity logs.
A digital team member with one job. It knows which systems to read, which steps to follow and what to hand back, for example a report or a draft.
Yes. Someone who knows the task describes it in plain words, eokit sets up the agent, and you check it before it runs.
The one you choose: a self-hosted model, a model from an EU provider or a large commercial model. Each department can use a different one. Access rights stay the same.
Reading and drafting happen automatically. Sending, booking or changing a record needs a person's approval, unless you decide otherwise. Every step is logged.
Workflows take on recurring tasks with a clear result, for example writing weekly reports, preparing reminders, summarizing meetings or comparing quotes. Your team decides how the agent works and what a good result looks like.
A workflow starts on a schedule, when something changes in a connected system, or when someone asks in the chat. You choose the trigger that fits the task.
Yes. You can run workflows outside working hours, for example for large monthly reports. Actions that need approval still wait for the person in charge.
The person in charge is told about the error and its cause. The log shows which steps ran and where the run stopped.
Every run is logged. You see which information the agent used and what came out. Your team checks whether the result meets its guidelines. You decide which actions also need approval.
eokit has connectors for SharePoint, Google Drive, Outlook and Gmail. Other tools connect through MCP servers. Which triggers and actions are available depends on the connector and on existing access rights.
eokit is designed to be natively GDPR-compliant. It runs in the EU or inside your own network, and prompts are checked for personal data before they can go to an external model. We provide a data processing agreement and a list of subprocessors.
Where you choose to run eokit: in your own data centre, in our EU cloud in Germany or Luxembourg, or in your own cloud account. It is not copied to other regions.
Yes. You describe once how your company writes, and drafts follow that tone. You can also add your logo and colours.
Exactly the people who can open the document today. eokit uses the permissions from your directory and file systems, so people get answers only from documents they are allowed to open.
Your documents stay where they are, because eokit does not move them. We remove our components and can hand over your activity logs.
A digital team member with one job. It knows which systems to read, which steps to follow and what to hand back, for example a report or a draft.
Yes. Someone who knows the task describes it in plain words, eokit sets up the agent, and you check it before it runs.
The one you choose: a self-hosted model, a model from an EU provider or a large commercial model. Each department can use a different one. Access rights stay the same.
Reading and drafting happen automatically. Sending, booking or changing a record needs a person's approval, unless you decide otherwise. Every step is logged.
Workflows take on recurring tasks with a clear result, for example writing weekly reports, preparing reminders, summarizing meetings or comparing quotes. Your team decides how the agent works and what a good result looks like.
A workflow starts on a schedule, when something changes in a connected system, or when someone asks in the chat. You choose the trigger that fits the task.
Yes. You can run workflows outside working hours, for example for large monthly reports. Actions that need approval still wait for the person in charge.
The person in charge is told about the error and its cause. The log shows which steps ran and where the run stopped.
Every run is logged. You see which information the agent used and what came out. Your team checks whether the result meets its guidelines. You decide which actions also need approval.
eokit has connectors for SharePoint, Google Drive, Outlook and Gmail. Other tools connect through MCP servers. Which triggers and actions are available depends on the connector and on existing access rights.
Bring your own systems, keep your own rules.
Write a few lines, and we will get back to you.
Welcome, I'm eo
I live inside eokit and help your team find, write and act. Tap me anytime to get around.
