Zammad

AI Attribute Classification for Zammad

Groups, attributes, chatbot — on your GPU. Nothing leaves your network.

  • Zammad Groups
  • On-prem GPU
  • Chatbot
  • No data export
Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO

How it works

Go live with Zammad

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

01

Connect Zammad

02

Describe Groups

03

Configure Studio

04

Run On-Prem

  1. 01

    Connect Zammad

    Install the connector plugin and connect with an API token.

  2. 02

    Describe Groups

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

  3. 03

    Configure Studio

    Zero-shot classification for groups, priority, tags, and object attributes.

  4. 04

    Run On-Prem

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

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

Zammad

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 Zammad

Group

Group Assignment

Priority

Priority Classification

State

Status Prediction

Tag

Auto-Tagging

Object Attribute

Custom Field Population

Requirements

Zammad 6.0+ (self-hosted or managed)
Docker / Docker Compose for OTAI Runtime
API access with admin token
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
Quick Start

Common Zammad Setups

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.

IT Helpdesk

  • Ticket: “VPN to the office is down”
  • Writes Group: Network
  • Sets Priority: 3 and tags: outage, vpn
  • Same pattern for hardware, software, and access tickets

Customer Service

  • Ticket: “I was charged twice on my invoice”
  • Writes Group: Billing
  • Sets Priority: 2 and tags: invoice, duplicate-charge
  • Same pattern for returns, shipping, and product questions

Municipal Services

  • Ticket: “Pothole on Main Street near the school”
  • Writes Group: Infrastructure
  • Sets Priority: 3 and tags: roads, public-works
  • Same pattern for permits, registrations, and public safety
ROI Estimate

See Your Potential Savings

Example monthly savings from replacing manual ticket routing with OTAI. See the full page for the assumptions behind these figures.

Quick ROI Estimate

See how much Zammad can save you

Small team (50 tickets/day)€3,500
Mid-size (200 tickets/day)€13,600
High volume (750 tickets/day)€54,500

estimated monthly savings vs. manual routing

See full ROI examples
Pricing

Editions

Free Cloud Trial to evaluate. Full On-Prem quotes based on agents and tier.

Free Cloud Trial

Evaluate & test

Free
  • Pre-configured GPU environment with OTAI installed
  • Includes sample ticket system and OTAI Studio
  • Instant access to evaluate features
  • No local hardware required
Instant setup

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

No. Full On-Prem classification is built from your helpdesk setup — not from historical ticket exports or a vendor-hosted copy of your data.

What OTAI uses instead:

  • Zammad group names, descriptions, and keywords
  • Live ticket fields during inference on your OTAI Runtime host
  • Connector write-back to predicted groups or object attributes

Ticket subjects and bodies stay inside your network. Security and procurement teams can document exactly which fields OTAI reads, where Runtime runs, and who has admin access — without granting blanket archive access to an external SaaS.

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

Ready to automate classification
for Zammad?

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

Constanze Krishnaratne

Your host

Constanze Krishnaratne

CEO