Government

AI Attribute Classification for Government Services

Citizen requests classified on your infrastructure. GDPR-aligned.

  • Department routing
  • On-prem GPU
  • GDPR-aligned
  • No data export
Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO

ROI estimate

What you can save

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

Show the full calculation

What manual routing costs you every month

Four hidden costs — easy to miss, expensive when they stack up.

L1 triage labor

2–4 h/day per L1

Agents read and sort before specialist work starts.

Misrouting & bounce

2× handle time

Wrong Department → tickets ping-pong between teams.

Customer wait time

SLA risk

Hours before the right team sees the ticket.

Repetitive cognitive load

Minutes per ticket

Reading threads, copying fields, re-prioritizing.

Before / after in real life

Concrete situations — not just spreadsheet math.

Lisa

Customer

Without OTAI

Hours waiting for a reply

A password reset lands in the general inbox — Lisa waits most of the day.

4+ hours
With OTAI

Answer in minutes via chatbot

The public chatbot resolves common requests instantly — no ticket needed.

~2 min

Marco

L1 agent

Without OTAI

Sorts every ticket by hand

Sorts 80+ tickets/day by hand — specialist teams still wait hours.

45 min avg. to right team
With OTAI

Routing on arrival

Classification sets Department and priority before Marco even opens the ticket.

Instant

Sandra

Specialist

Without OTAI

Reads long threads herself

Scrolls through 15 emails just to understand the current status.

8–12 min/ticket
With OTAI

Summary on the ticket

Problem, status, and next steps are written back on the ticket.

~30 sec
Pack: Free Cloud Trial

Too low volume

Many routing targets, minimal tickets — Full On-Prem is not yet worth it.

5 tickets/day · 30 Departments

Manual routing€450
With OTAI (total)≈ €200
OTAI subscription (range)€0 (trial)
Remaining handling cost€200

Estimated monthly savings

≈ −€250

per month (net of subscription range)

Agent time saved
≈ 6 h/month
Value of that time
≈ €130 worth

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

    ≈ €180
  • Priority & other attributes

    Correct priority cuts sorting effort.

    Faster first handling / shorter cycle

    ≈ €40
  • Ticket summaries

    Saves agent reading time, with minor impact on overall cycle time.

    Agent time (not cycle time)

    ≈ €30
  • Answer drafts

    Soon

    Minimal effect at low ticket volumes.

    Not shipped yet — illustrative only

    —
  • Customer chatbot

    Premium · Soon

    Premium 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.

Pack: Entry

Small team

A lean support team handling a steady daily ticket stream.

50 tickets/day · 3 Departments

Manual routing€4,800
With OTAI (total)≈ €1,800–€2,100
OTAI subscription (range)≈ €500–€800
Remaining handling cost€1,300

Estimated monthly savings

≈ €2,700–€3,000

per month (net of subscription range)

Agent time saved
≈ 40 h/month
Value of that time
≈ €900 worth

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

    ≈ €2,200
  • Priority & other attributes

    Proper fields reduce mis-prioritization and re-sorting.

    Faster first handling / shorter cycle

    ≈ €400
  • Ticket summaries

    Cuts reading time per ticket for agents.

    Agent time (not cycle time)

    ≈ €350
  • Answer drafts

    Soon

    Review a draft (~30–90s) instead of typing — useful on ~25% of tickets.

    Not shipped yet — illustrative only

    ≈ €250
  • Customer chatbot

    Premium · Soon

    Premium 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.

Pack: Standard

Mid-size

Growing helpdesk routing across multiple specialized teams.

200 tickets/day · 10 Departments

Manual routing€18,500
With OTAI (total)≈ €5,200–€5,900
OTAI subscription (range)≈ €800–€1,500
Remaining handling cost€4,400

Estimated monthly savings

≈ €12,600–€13,300

per month (net of subscription range)

Agent time saved
≈ 160 h/month
Value of that time
≈ €3,500 worth

Where the savings come from

  • Department classification

    Straight to the right team without manual triage — dominant savings lever.

    Faster first handling / shorter cycle

    ≈ €9,500
  • Priority & other attributes

    Proper priority from intake shortens time to meaningful work.

    Faster first handling / shorter cycle

    ≈ €1,800
  • Ticket summaries

    Saves agent reading time across all tickets.

    Agent time (not cycle time)

    ≈ €1,200
  • Answer drafts

    Soon

    Less typing on routine queries (coming soon).

    Not shipped yet — illustrative only

    ≈ €900
  • Customer chatbot

    Premium · Soon

    Premium: Deflects ticket creation. Not included in Standard.

    Not shipped yet — illustrative only

    —

Resolved up to a day faster — Department classification drives most savings.

Pack: Premium

High volume

Heavy ticket load across many targets with complex initial routing.

750 tickets/day · 40 Departments

Manual routing€72,000
With OTAI (total)≈ €13,500–€15,000+
OTAI subscription (range)≈ €1,500–€3,000+
Remaining handling cost€12,000

Estimated monthly savings

≈ €57,000–€58,500

per month (net of subscription range)

Agent time saved
≈ 620 h/month
Value of that time
≈ €14,000 worth

Where the savings come from

  • Department classification

    Eliminates L1 bottlenecks with immediate team assignment.

    Faster first handling / shorter cycle

    ≈ €38,000
  • Priority & other attributes

    Proper priority shortens wait time before work begins.

    Faster first handling / shorter cycle

    ≈ €6,500
  • Ticket summaries

    Saves significant agent reading hours.

    Agent time (not cycle time)

    ≈ €4,000
  • Answer drafts

    Soon

    Review drafts instead of typing — applies to ~25% of tickets (coming soon).

    Not shipped yet — illustrative only

    ≈ €3,500
  • Customer chatbot

    Premium · Soon

    Premium: Deflects common requests so tickets are never created.

    Fewer tickets created

    ≈ €8,000

Direct team routing on intake plus Premium chatbot ticket deflection.

How a ticket reaches the right team

Without OTAIHours of waiting before work begins
  1. Ticket arrives
  2. L1Reads & triages manually
  3. Moved to a Department
  4. L2/L3Bounced if misrouted
  5. Right team starts
With OTAIInstant routing — no triage backlog
  1. Ticket arrives
  2. AIClassifies target + priority
  3. L1/L2/L3Assigned directly to the right team
  4. Team starts immediately

More ways OTAI saves cost

Department classification drives cycle-time savings. Other features save agent time or deflect tickets.

Ticket summaries

Summarizes long email threads instantly. Reduces agent reading time.

From Entry · available now

Typical savingLess read time per ticket
Coming soon

Answer drafts for agents

Review and send drafts instead of typing. Speeds up responses.

Depends on pack

Typical savingFaster replies, less typing
Coming soon

Customer chatbot

Answers common questions directly to deflect ticket creation.

Premium pack only

Typical savingFewer tickets created

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.

Features

Every feature in Government

Every feature, what it gives you, and how it looks.

Chatbot for citizens

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 Studio: public chatbot with the code to add it to a website

Department routing

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 Studio: department descriptions such as building office and residents office

Priority

OTAI sets the priority from deadlines and urgency in the request.

Your benefit: Urgent requests are seen first.

OTAI Studio: priority agent with its values

Service category

OTAI fills a field such as permits, registrations, or complaints.

Your benefit: You can count and report requests by service.

OTAI Studio: agent that fills a category field

Request summary

A short summary appears at the top of the request.

Your benefit: Staff see what a long request is about in seconds.

Ticket with the OTAI summary at the top

Reply drafts

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.

OTAI Studio: reply draft agent

Runs in your data center

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.

Quick Start

Government Service Templates

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.

Citizen Services

  • Request: “Need a copy of my residence certificate”
  • Writes department: Civil Registry
  • Sets Priority: 2 and service type: Certificate
  • Same pattern for permits, complaints, and information requests

Infrastructure

  • Request: “Streetlight out on Lindenstraße”
  • Writes department: Public Works
  • Sets Priority: 3 and category: Lighting
  • Same pattern for roads, utilities, and construction permits

Internal Administration

  • Request: “Need badge access to the archive wing”
  • Writes department: Facilities / IT
  • Sets Priority: 2 and type: Access request
  • Same pattern for facility, HR, and internal IT tickets
How it works

Go live with Government

Connect the helpdesk, describe your setup in Studio, classify tickets zero-shot, run Full On-Prem.

01

Connect Helpdesk

02

Describe Departments

03

Configure Studio

04

Run On-Prem

  1. 01

    Connect Helpdesk

    Connect Zammad, OTOBO, or Znuny with the matching OTAI connector.

  2. 02

    Describe Departments

    Use department names and categories from your setup — no citizen ticket export.

  3. 03

    Configure Studio

    Zero-shot classification for department, priority, and custom fields.

  4. 04

    Run On-Prem

    Runtime classifies new citizen requests locally and writes routing back.

On-Prem Classification

Classify Ticket Fields on Your Infrastructure

Full On-Prem AI runs inside your network to set queues, groups, priorities, and custom fields securely.

Full On-Prem Path

Your Infrastructure (On-Prem)
GPU required
OTAI Studio

On-prem configuration and control in your environment

Government

New tickets arrive for AI processing

OTAI Runtime + Connector

Local classification on your GPU — air-gap ready

Tickets Enriched by AI

Routing, priority, and custom fields updated automatically

No ticket data leaves your network. Everything runs on your infrastructure.

AI Capabilities

Fields AI Can Improve in Government

Department

Department Routing

Service Category

Service Classification

Priority

Priority Classification

Sub-Department

Sub-Routing

Requirements

Any supported ticketing system (Zammad, OTOBO, or Znuny)
Docker / Docker Compose for OTAI Runtime
2 CPU cores, 4 GB RAM minimum
GPU with 24 GB+ VRAM for Full On-Prem production
Start with the Free Cloud Trial if GPU hardware is not yet available
Pricing

Editions

Free Cloud Trial to evaluate. Full On-Prem quotes for enterprise and public sector.

Free Cloud Trial

One month · full features

Free
  • One month
  • Full features on a sample ticket system and OTAI Studio
  • Rate limit and a total usage cap
  • No GPU on your side
One month

Full On-Prem

On request · agent-based software

From ~€500 / month
  • Studio and Runtime on your infrastructure
  • Chatbot, classification, summaries, and AI workflows
  • Flexible agent licensing: Entry, Standard, or Premium
  • Includes updates, security patches, and support
  • Run on existing hardware or partner hardware
View Product
FAQ

Frequently Asked Questions

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:

  • Where OTAI Runtime runs
  • Who has admin access and how logs are retained
  • Department names, service descriptions, and routing rules as the classification input

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.

Ready to automate classification
for Government?

Automate ticket classification on-premise using your existing Department setup.

Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO