OTOBO

Fewer tickets and faster answers in OTOBO

A chatbot answers from your OTOBO FAQs in the customer portal and on your website. New tickets land in the right queue. Agents get a summary and a reply draft. Your ticket data stays on your servers.

  • Chatbot for customers
  • Right queue on arrival
  • Summary and reply draft
  • Data stays on your servers
Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO

Your benefits

What OTAI does for your OTOBO team

Your agents keep working in OTOBO. OTAI takes over the repetitive part.

Fewer repeat tickets

The chatbot answers from your OTOBO FAQs in the customer portal and on your website. If a person is needed, it opens the ticket with the details.

No sorting by hand

New tickets land in the right queue, with priority, type, and service already set.

Faster answers

Agents see a short summary at the top of the ticket and start from a reply draft. A person still checks and sends every reply.

Your data stays with you

OTAI runs on your own servers. Ticket text does not leave your network.

ROI estimate

What you can save

Example monthly savings for OTOBO teams, net of the OTAI subscription. Open the full calculation to see how the numbers add up.

Small team · 50 tickets/day · 3 Queues

≈ €2,700–€3,000

estimated monthly savings

Mid-size · 200 tickets/day · 10 Queues

≈ €12,600–€13,300

estimated monthly savings

High volume · 750 tickets/day · 40 Queues

≈ €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 Queue → 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 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 Queues

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

  • Queue 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 Queues

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

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 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 classification drives most savings.

Pack: Premium

High volume

Heavy ticket load across many targets with complex initial routing.

750 tickets/day · 40 Queues

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

  • Queue 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 Queue
  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 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 OTOBO

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

Chatbot in the customer portal

Signed-in customers ask in the OTOBO customer portal. The chatbot answers from your OTOBO FAQs. If a person is needed, it creates the ticket.

Your benefit: Fewer repeat tickets, and the tickets that still come in already have the details.

OTAI Studio: customer chatbot with welcome text, example questions, and tools

Chatbot for your website

Visitors who are not logged in ask on your website. The chatbot answers from your public OTOBO FAQs.

Your benefit: Simple questions get answered before they become tickets.

OTAI Studio: public chatbot with the code to add it to a website

AI Chat for agents

Agents open AI Chat in OTOBO and ask about internal FAQs and procedures.

Your benefit: Agents find the answer without searching the FAQ module.

OTAI Studio: internal chatbot with model and knowledge settings

Quick setup, model already running

Install two OTOBO packages and start OTAI with Docker Compose. The model is already included. OTAI Studio opens from the OTOBO menu.

Your benefit: You go live in days, and your admins never leave OTOBO to sign in.

OTOBO dashboard with OTAI Studio in the main menu

Queue assignment

OTAI reads each new ticket and moves it to the right queue. It uses your queue names and descriptions. No ticket history is needed.

Your benefit: Tickets reach the right team without anyone sorting them by hand.

OTAI Studio: queue agent with queue descriptions

Priority, type, and service

OTAI sets priority, type, service, and your dynamic fields from the values you already have in OTOBO.

Your benefit: Urgent tickets stand out at once, and reports work with clean values.

OTAI Studio: priority agent with its values

Ticket summary

A short summary appears at the top of the ticket in OTOBO.

Your benefit: Agents know what a long ticket is about in seconds.

OTOBO ticket with the OTAI summary at the top

Reply drafts

OTAI prepares a reply to the last customer message, using your FAQs. The agent reads it, edits it, and sends it.

Your benefit: Faster answers, and an agent still checks every reply. OTAI sends nothing on its own.

OTAI Studio: reply draft agent with reply style and FAQ search
Comparison

Why OTAI and not just OTOBO AI?

OTOBO offers its own AI add-on. It writes reply suggestions and gives agents a chat in the ticket. Here is where OTAI goes further.

Sorting new tickets

OTOBO AI: OTOBO AI writes reply suggestions. It does not sort new tickets.

Open Ticket AI: Sets queue, priority, type, service, and dynamic fields when the ticket arrives.

Answers for customers

OTOBO AI: Built for agents: reply suggestions and a chat inside the ticket.

Open Ticket AI: A chatbot in the customer portal and on your website answers from your FAQs.

AI model

OTOBO AI: You run a language model, an embedding model, a vector database, and the chat yourself. Or you use the Managed AI from Rother OSS.

Open Ticket AI: The model comes with OTAI and is already running.

Where ticket text goes

OTOBO AI: With the Managed AI, ticket text goes to the Rother OSS data center for processing.

Open Ticket AI: Ticket text stays on your servers.

Sources: OTOBO AI · OTOBO AI manual

Quick Start

Common OTOBO Setups

What a typical rollout looks like. We map your Queues in Studio; Runtime classifies new tickets and writes queue, priority, and dynamic fields back to OTOBO.

IT Service Management

  • Ticket: “Email is down for the whole floor”
  • Writes Queue: Incident::Email
  • Sets Priority: 4 and type: Incident
  • Same pattern for service requests, changes, and problems

Customer Support

  • Ticket: “Order 4821 never arrived”
  • Writes Queue: Fulfillment
  • Sets Priority: 3 and type: Complaint
  • Same pattern for returns, billing, and technical support

Internal IT

  • Ticket: “Need laptop and VPN for a starter on Monday”
  • Writes Queue: Service Request::Onboarding
  • Sets Priority: 2 and tags: hardware, access
  • Same pattern for network, software, and offboarding
How it works

Go live with OTOBO

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

01

Connect OTOBO

02

Describe Queues

03

Configure Studio

04

Run On-Prem

  1. 01

    Connect OTOBO

    Enable Generic Interface and connect OTAI with a web-service token.

  2. 02

    Describe Queues

    Use queue names and descriptions from your helpdesk setup — no ticket history.

  3. 03

    Configure Studio

    Zero-shot classification for queues, priority, and dynamic fields.

  4. 04

    Run On-Prem

    Runtime classifies new tickets locally and writes results back to OTOBO.

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

OTOBO

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 OTOBO

Queue

Queue Assignment

Priority

Priority Classification

Type

Type Classification

State

Status Prediction

Dynamic Field

Custom Field Population

Requirements

OTOBO 11.0 and 11.1 (Community or Enterprise)
Docker / Docker Compose for OTAI Runtime
Generic Interface web service enabled
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 based on agents and tier.

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

No. Full On-Prem classification uses your helpdesk setup — not bulk exports of historical ticket content to an external vendor.

What OTAI uses instead:

  • OTOBO queue names, descriptions, and keywords
  • Live ticket fields during inference on your OTAI Runtime host
  • Generic Interface write-back as dynamic fields or queue moves

For IT and procurement reviews, that means a narrow data path: ticket fields in, predicted attributes out, with no standing hosted replication of ticket bodies.

Read the Setup-based classification guide for the full architecture walkthrough.

Ready to automate classification
for OTOBO?

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

Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO