Open Ticket AI

OTAI
Private AI
for your helpdesk
on your servers

100% Full On-Prem — private AI for your helpdesk on your infrastructure. Configure classification, summaries, and workflows in OTAI Studio — integrated directly into your ticket system.

Choosing queue, priority, or field classification in OTAI Studio

Stop hand-sorting tickets. Pick what to classify — queue, priority, type, or a field — and the same setup covers each one.

Core Capabilities

Full control over helpdesk AI on your own infrastructure. Configure chatbots, classification, ticket summaries, and reply drafts in OTAI Studio.

What is OTAI Studio?

Your control panel for helpdesk AI.

OTAI Studio extends your ticket system on your infrastructure alongside the runtime. No cloud required for production.

Change AI behavior in minutes without editing ticket system sysconfig files.

100% Full On-Prem

Studio, Runtime, and data remain on your infrastructure.

Built Into Your Helpdesk

Open Studio directly from OTOBO, Znuny, or Zammad without extra accounts.

Full Access Control

Control roles and permissions for agents and settings from one place.

Menu to start queue, priority, or field classification

One menu for every decision you want off the agent's plate.

  1. Open Agents and start a new classification.
  2. Choose queue routing — the same steps cover priority, type, service, and custom fields.
  3. Nothing runs until you turn it on. You review the setup first.
Capabilities

Control helpdesk AI without complex sysconfig.

OTAI Studio simplifies AI configuration, agent management, and runtime visibility.

Easy to Use

New agent → describe values → set trigger & fallback → save → activate. Same for every classification type.

Fast Setup

Queue routing in minutes. Customer chatbot: enable FAQ search, index your homepage, activate.

Helpdesk Sync

Sync queues, priorities, and categories from your ticket system — reuse existing notes as AI descriptions.

Access Control

Manage permissions for editing agents and system settings.

Evaluation Path

Test online, then deploy on-prem.

Evaluate the platform online before moving the setup to your infrastructure.

01

Contact Us

Share your ticket system and use case. We set up your trial.

02

Free Cloud Trial

One month on the Free Cloud Trial. Full features, with a rate limit and a total usage cap. Then OTAI runs on your GPU.

03

Full On-Prem

Deploy Studio and Runtime on your own infrastructure for production.

04

Support Included

We assist with deployment, updates, security patches, and hardware specs.

Pricing

Flexible Editions

Evaluate online with our Free Cloud Trial, then deploy Full On-Prem on your servers.

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
Contact Sales

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
Contact Sales
Return on investment

The cost of routing tickets without AI

Manual triage, misrouting, and wait time add up fast. See what changes when classification runs on every ticket.

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 Queue / group → 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 Queue / group 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

Example savings by team size

Two typical profiles — net of OTAI subscription range. More scenarios on the full ROI calculator page.

Pack: Entry

Small team

A lean support team handling a steady daily ticket stream.

50 tickets/day · 3 queues/groups

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

  • Queue / group 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 queues/groups

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

  • Queue / group 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 — Queue / group classification drives most savings.

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 Queue / group
  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

Queue / group 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
See all ROI examples & assumptions

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.

OTAI Direct Service

Included Support

Updates, patches, and direct OTAI support — no third parties.

Included with Full On-Prem
OTAI Direct

Basis

Included standard support

  • Hours: Mon–Fri, 9:00–17:00
  • First response: 2 business days
  • Resolution: 5 business days
OTAI Direct

Premium

Expanded support with faster SLAs

  • Hours: Mon–Sat, 8:00–20:00
  • First response: 8 hours
  • Resolution: 2 business days

What Support Covers

Six pillars that keep your on-prem deployment running.

Software Updates

Studio and runtime updates.

Security Patches

On-prem security patches.

SLA-backed Response

Agreed response and resolution targets.

Troubleshooting

Direct engineer access for deployment issues.

Accuracy Support

Helpdesk setup tuning for better classification.

Escalation Path

Clear path to senior engineers.

Partner Ecosystem

Need Implementation or Custom Work?

Implementation, integration, and custom dev are delivered by certified partners.

View Partners & Services

Deployment & Hardware

Full On-Prem runs completely on your servers. Use your existing GPU hardware or source a system through our partner.

ON YOUR SERVERS

Deploy via Docker alongside Zammad, OTOBO, Znuny, and other ticket systems.

THE RIGHT GPU

Requires a GPU with at least 24 GB VRAM. We provide exact hardware recommendations for your volume.

BUY YOUR WAY

Use your existing infrastructure or purchase hardware through our trusted partners.

TEST BEFORE YOU BUY

Evaluate OTAI risk-free with our Free Cloud Trial before purchasing hardware.

Ready for
helpdesk AI on your servers?

Run routing, priorities, and summaries on your infrastructure.