More time for complex support cases
For IT service providers and MSPs with their own service desk in Germany, Austria, and Switzerland: I build AI agents that triage tickets, prepare server diagnostics, and write support reports, so your team can spend less time on routine work.
Changes to customer systems require technician approval. Every action is logged.
Tue–Thu, 10:00–16:00 Berlin time · 30 minutes · Google Meet
Pick a free time on this page and answer five short questions. The invitation with the Google Meet link arrives by email.
Routine tickets cost technician time. And margin.
Your service desk is at capacity, yet experienced technicians spend much of their time on recurring tickets, diagnostic preparation, and documentation. Under fixed-price managed-service contracts, every extra minute eats into your margin.
My agent for server diagnostics and support reports won the techbold challenge at START Hack Vienna 2026 and the ElevenLabs special award for best use of voice. The hackathon project is not evidence of customer savings. View the project and source code →
From the first check to implementation
Free Ticket Time Check
In 30 minutes, you get an initial estimate of the technician time spent on recurring tickets and possible ticket types to automate.
- Calculate using your ticket volumes and handling times
- Discuss recurring tasks and required approvals
- Decide whether a detailed analysis is worth pursuing
Paid workshop
In a paid workshop, we analyse the selected workflows in detail. We define system integrations, tasks, and permissions.
- Choose the ticket types the agent will handle
- Record required approvals and prohibited actions
- Agree on baseline values and measurements
Fixed-price implementation
I build the agent for the agreed ticket types. For two weeks in shadow operation, it only makes suggestions. It then goes into operation with the agreed approval stages.
- Require technician approval for changes to customer systems
- Log every action
- Measure minutes per ticket, first-contact resolution rate, and escalations
Operation and expansion
After launch, I can operate and expand the agents I built.
- Continue tracking the agreed measurements
- Review changes based on the tickets the agent has handled
- Agree on further tasks and approvals before expanding
What the agent handles
The agent triages tickets, prepares server diagnostics, and writes support reports. We choose the ticket types it will handle during the workshop.
The agent only changes customer systems after technician approval. We agree on tasks and limits before it goes into use. The agent uses its own service account with minimal permissions.
Every action is logged. Your team can review what the agent executed.
Before launch, your team reviews suggestions on real tickets. Technicians continue to decide which changes the agent may carry out.
We measure minutes per ticket, first-contact resolution rate, and escalations. Real tickets show whether the agent reduces your team's workload.
For the initial estimate
Rough figures are enough. We look at recurring ticket types individually: volume multiplied by handling time gives the technician time tied up in that work. Team size and contract type provide context. Time spent is not the same as achievable savings.
Recurring tickets per month
How often does the selected ticket type occur in a typical month?
Technician count
How many technicians handle these tickets?
Minutes per routine ticket
How much working time does a typical routine ticket take?
Fixed-price contracts
What share of your contracts are billed at a fixed price?
Book the free check
Tue–Thu, 10:00–16:00 Berlin time · 30 minutes · Google Meet
You get an initial time estimate and possible ticket types to automate. You decide separately whether to continue with a detailed analysis in the paid workshop.
Free check · 30 minutes · Google Meet
Pick a time
Choose a free time and answer five short questions so I can prepare. Google sends the invitation with the Meet link to your email address.
Booked.
The invitation with the Google Meet link is on its way to .
If it does not arrive within a few minutes, check your spam folder or email oskar@freye.tech.