Fewer repeat tickets
A chatbot on your website answers simple questions at any hour, with the facts you enter in OTAI Studio.
A chatbot answers repeat questions on your website. New tickets get the right Group and priority. Agents see a summary at a glance. Everything runs on your own servers, with the AI model already set up.

Your host
Constanze Krishnaratne
CEO
Your agents keep working in Zammad. OTAI takes over the repetitive part.
A chatbot on your website answers simple questions at any hour, with the facts you enter in OTAI Studio.
New tickets get the right Group, priority, and tags when they arrive.
A short summary shows what a ticket is about without reading the whole thread.
OTAI runs on your own servers. Ticket text does not leave your network.
Example monthly savings for Zammad teams, net of the OTAI subscription. Open the full calculation to see how the numbers add up.
Small team · 50 tickets/day · 3 Groups
≈ €2,700–€3,000
estimated monthly savings
Mid-size · 200 tickets/day · 10 Groups
≈ €12,600–€13,300
estimated monthly savings
High volume · 750 tickets/day · 40 Groups
≈ €57,000–€58,500
estimated monthly savings
Four hidden costs — easy to miss, expensive when they stack up.
Agents read and sort before specialist work starts.
Wrong Group → tickets ping-pong between teams.
Hours before the right team sees the ticket.
Reading threads, copying fields, re-prioritizing.
Concrete situations — not just spreadsheet math.
Lisa
Customer
Hours waiting for a reply
A password reset lands in the general inbox — Lisa waits most of the day.
4+ hoursAnswer in minutes via chatbot
The public chatbot resolves common requests instantly — no ticket needed.
~2 minMarco
L1 agent
Sorts every ticket by hand
Sorts 80+ tickets/day by hand — specialist teams still wait hours.
45 min avg. to right teamRouting on arrival
Classification sets Group and priority before Marco even opens the ticket.
InstantSandra
Specialist
Reads long threads herself
Scrolls through 15 emails just to understand the current status.
8–12 min/ticketSummary on the ticket
Problem, status, and next steps are written back on the ticket.
~30 secMany routing targets, minimal tickets — Full On-Prem is not yet worth it.
5 tickets/day · 30 Groups
Estimated monthly savings
≈ −€250
per month (net of subscription range)
Where the savings come from
Group classification
Direct routing to the right team without L1 triage hops. Main lever for fast handling.
Faster first handling / shorter cycle
Priority & other attributes
Correct priority cuts sorting effort.
Faster first handling / shorter cycle
Ticket summaries
Saves agent reading time, with minor impact on overall cycle time.
Agent time (not cycle time)
Answer drafts
SoonMinimal effect at low ticket volumes.
Not shipped yet — illustrative only
Customer chatbot
Premium · SoonPremium pack — stops ticket creation. Needs higher volume.
Not shipped yet — illustrative only
Subscription costs outweigh savings at 5 tickets/day. The math flips at higher volume.
A lean support team handling a steady daily ticket stream.
50 tickets/day · 3 Groups
Estimated monthly savings
≈ €2,700–€3,000
per month (net of subscription range)
Where the savings come from
Group classification
No L1→L2 hopping: The right team starts on intake. Primary savings driver.
Faster first handling / shorter cycle
Priority & other attributes
Proper fields reduce mis-prioritization and re-sorting.
Faster first handling / shorter cycle
Ticket summaries
Cuts reading time per ticket for agents.
Agent time (not cycle time)
Answer drafts
SoonReview a draft (~30–90s) instead of typing — useful on ~25% of tickets.
Not shipped yet — illustrative only
Customer chatbot
Premium · SoonPremium pack only: Prevents simple requests from becoming tickets.
Not shipped yet — illustrative only
Tickets land with the right team hours earlier — SLAs are easily met.
Growing helpdesk routing across multiple specialized teams.
200 tickets/day · 10 Groups
Estimated monthly savings
≈ €12,600–€13,300
per month (net of subscription range)
Where the savings come from
Group classification
Straight to the right team without manual triage — dominant savings lever.
Faster first handling / shorter cycle
Priority & other attributes
Proper priority from intake shortens time to meaningful work.
Faster first handling / shorter cycle
Ticket summaries
Saves agent reading time across all tickets.
Agent time (not cycle time)
Answer drafts
SoonLess typing on routine queries (coming soon).
Not shipped yet — illustrative only
Customer chatbot
Premium · SoonPremium: Deflects ticket creation. Not included in Standard.
Not shipped yet — illustrative only
Resolved up to a day faster — Group classification drives most savings.
Heavy ticket load across many targets with complex initial routing.
750 tickets/day · 40 Groups
Estimated monthly savings
≈ €57,000–€58,500
per month (net of subscription range)
Where the savings come from
Group classification
Eliminates L1 bottlenecks with immediate team assignment.
Faster first handling / shorter cycle
Priority & other attributes
Proper priority shortens wait time before work begins.
Faster first handling / shorter cycle
Ticket summaries
Saves significant agent reading hours.
Agent time (not cycle time)
Answer drafts
SoonReview drafts instead of typing — applies to ~25% of tickets (coming soon).
Not shipped yet — illustrative only
Customer chatbot
Premium · SoonPremium: Deflects common requests so tickets are never created.
Fewer tickets created
Direct team routing on intake plus Premium chatbot ticket deflection.
Group classification drives cycle-time savings. Other features save agent time or deflect tickets.
Summarizes long email threads instantly. Reduces agent reading time.
From Entry · available now
Review and send drafts instead of typing. Speeds up responses.
Depends on pack
Answers common questions directly to deflect ticket creation.
Premium pack only
Illustrative examples for European support teams. Subscription figures are ranges (Full On-Prem from ~€500/month depending on agents + pack) — not a fixed price list. Manual costs cover triage, wait time, and misrouting. Chatbot and answer drafts are coming soon.
Every feature, what it gives you, and how it looks.
Zammad AI has no chatbot. Zammad Chat only connects a customer to your agents and sends no automatic answer. OTAI adds a chatbot to your website. It answers with the facts you enter in OTAI Studio.
Your benefit: Customers get an answer to simple questions at any hour, without waiting for an agent.
On-prem Zammad AI needs Ollama installed and a model downloaded and loaded. OTAI ships with the model already running on your GPU.
Your benefit: You start with on-prem AI right away. There is no separate model project.
One screen shows which AI agents run, on which tickets, and what they write back.
Your benefit: Your team changes the setup itself. No code and no config files.
OTAI reads each new ticket and sets the right Group. It uses your Group names and the descriptions you add in Studio. No ticket history is needed.
Your benefit: Tickets reach the right team without anyone sorting them by hand.
OTAI sets the priority from what the customer writes and adds matching tags.
Your benefit: Urgent tickets stand out at once, and tags stay consistent for reports.
OTAI fills your Zammad object attributes, such as department or product, with values from your list.
Your benefit: Triggers and reports work with clean values instead of empty fields.
OTAI writes a short summary of the ticket into a Zammad object attribute.
Your benefit: Agents see what a ticket is about without reading the whole thread.
Screenshots show OTAI Studio connected to Znuny. With Zammad you use the same Studio.
Zammad 7 brings its own AI features for agents. Here is where OTAI goes further.
Zammad AI: No chatbot. Zammad Chat connects a visitor to an agent and sends no automatic answer.
Open Ticket AI: A chatbot on your website answers simple questions on its own.
Zammad AI: You bring the model. On your own servers, you install Ollama and load a model yourself.
Open Ticket AI: The model comes with OTAI and is already running.
Zammad AI: With a hosted provider such as OpenAI, ticket text is sent to that provider.
Open Ticket AI: Ticket text stays on your servers.
Zammad AI: Each AI agent runs only when a trigger, macro, or scheduler job calls it.
Open Ticket AI: Switch it on in OTAI Studio, and it works on every new ticket.
Zammad AI: If you run the model yourself, you keep it running and up to date.
Open Ticket AI: Model updates and support are part of OTAI.
Sources: Zammad AI providers · Zammad AI agents · Zammad Chat
What a typical rollout looks like. We map your Groups in Studio; Runtime classifies new tickets and writes group, priority, and tags back to Zammad.
Connect the helpdesk, describe your setup in Studio, classify tickets zero-shot, run Full On-Prem.
01
The model is already running. You do not install Ollama or load a model.
02
Connect with an API token. Your groups come from Zammad.
03
Turn on the group, the priority, the chatbot, and summaries. No separate model step.
04
The same kind of GPU you would buy for Zammad. Results are written back into the ticket.
Full On-Prem AI runs inside your network to set queues, groups, priorities, and custom fields securely.
On-prem configuration and control in your environment
New tickets arrive for AI processing
Local classification on your GPU — air-gap ready
Routing, priority, and custom fields updated automatically
No ticket data leaves your network. Everything runs on your infrastructure.
Free Cloud Trial to evaluate. Full On-Prem quotes based on agents and tier.
One month · full features
On request · agent-based software
Questions about using OTAI with Zammad.
Zammad's own AI needs a provider. On-prem, that means you install Ollama and load a model. Zammad's install notes say a production model server is a complex stack, and the bundled Ollama add-on is for testing.
OTAI arrives with the model running. You connect Zammad and set your groups in OTAI Studio.
You still buy a GPU. Zammad on-prem needs one too. The difference is that you do not build the model server yourself.
OTAI also brings a chatbot for your website. Zammad AI has none: Zammad Chat connects a visitor to an agent and sends no automatic answer.
OTAI then sets the group, the priority, and other fields, and it writes a short ticket summary.
Deploy, configure, and run OTAI with Zammad.
Automate ticket classification on-premise using your existing Group setup.

Your host
Constanze Krishnaratne
CEO