Small team · 50 tickets/day · 3 Departments
≈ €2,700–€3,000
estimated monthly savings
Citizen requests classified on your infrastructure. GDPR-aligned.

Your host
Constanze Krishnaratne
CEO
Example monthly savings for Government teams, net of the OTAI subscription. Open the full calculation to see how the numbers add up.
Small team · 50 tickets/day · 3 Departments
≈ €2,700–€3,000
estimated monthly savings
Mid-size · 200 tickets/day · 10 Departments
≈ €12,600–€13,300
estimated monthly savings
High volume · 750 tickets/day · 40 Departments
≈ €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 Department → 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 Department 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 Departments
Estimated monthly savings
≈ −€250
per month (net of subscription range)
Where the savings come from
Department 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 Departments
Estimated monthly savings
≈ €2,700–€3,000
per month (net of subscription range)
Where the savings come from
Department 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 Departments
Estimated monthly savings
≈ €12,600–€13,300
per month (net of subscription range)
Where the savings come from
Department 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 — Department classification drives most savings.
Heavy ticket load across many targets with complex initial routing.
750 tickets/day · 40 Departments
Estimated monthly savings
≈ €57,000–€58,500
per month (net of subscription range)
Where the savings come from
Department 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.
Department 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.
Citizens ask on your website. The chatbot answers from your public FAQs and the facts you enter in OTAI Studio.
Your benefit: Common questions about opening hours, documents, and fees get answered without a phone call or email.
OTAI reads each request and sends it to the right department, such as the building office or the residents office. It uses your department names and descriptions.
Your benefit: Requests reach the right department without being forwarded several times.
OTAI sets the priority from deadlines and urgency in the request.
Your benefit: Urgent requests are seen first.
OTAI fills a field such as permits, registrations, or complaints.
Your benefit: You can count and report requests by service.
A short summary appears at the top of the request.
Your benefit: Staff see what a long request is about in seconds.
OTAI prepares a reply. A staff member reads it, edits it, and sends it.
Your benefit: Faster answers, and a person still checks every reply. OTAI sends nothing on its own.
Ticket system, OTAI, and the model run on your servers and your GPU. The model is already included.
Your benefit: Citizen data stays in your building. No external AI service is involved.
Screenshots show OTAI Studio with OTOBO and Znuny.
What a typical public-sector rollout looks like. We map departments in Studio; Runtime classifies citizen requests on-prem and writes routing back to the helpdesk.
Connect the helpdesk, describe your setup in Studio, classify tickets zero-shot, run Full On-Prem.
01
Connect Zammad, OTOBO, or Znuny with the matching OTAI connector.
02
Use department names and categories from your setup — no citizen ticket export.
03
Zero-shot classification for department, priority, and custom fields.
04
Runtime classifies new citizen requests locally and writes routing back.
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 for enterprise and public sector.
One month · full features
On request · agent-based software
Questions about using OTAI with Government.
Yes. OTAI is designed for Full On-Prem deployments where citizen ticket content is processed entirely inside your infrastructure. Classification uses your helpdesk setup — not historical citizen records exported to a vendor-hosted system.
What stays under your control:
OTAI does not require sending ticket bodies to a third-party SaaS for production routing. Procurement and DPO reviews typically focus on data location, subprocessors, and security measures — our on-prem architecture aligns with GDPR expectations for confidentiality and integrity of processing inside EU-hosted infrastructure.
Read the OTAI data privacy policy for the full legal overview.
Deploy, configure, and run OTAI with Government.
Automate ticket classification on-premise using your existing Department setup.

Your host
Constanze Krishnaratne
CEO