How to Use Zammad: The Beginner’s Guide (First Install, the Wizard, First Channel, and First Ticket)

CodexFuse Team · 2026-11-01T23:53:04.239Z · 14 min read min read

Zammad is the free, open-source helpdesk you self-host: this beginner’s guide covers installing it, the setup wizard, your first email channel, groups and roles, triggers, SLAs, and your first ticket.

What Is Zammad, Exactly?

Zammad is a free, open-source helpdesk system: every customer message — an email, a chat message, a phone note, or a social post — becomes a single TICKET that your team works through one shared queue. It is web-based, so agents work from a browser, and it is designed to be self-hosted on your own server, which means your support data stays on your hardware. If you are searching for how to use Zammad and finding only the maker's own docs, this independent Zammad tutorial is the missing piece: it walks you through installing Zammad on a fresh server, finishing the first-time setup wizard, connecting your first email channel, organizing groups and roles, and handling your first ticket end to end. It is pinned to Zammad 7.2.2, the current stable release as of October 2026, and it assumes you have a server to install on — our VPS hosting guide explains what that looks like. Written as a Zammad for beginners walkthrough, it answers the real questions first-time admins ask.

Zammad speaks its own vocabulary, and learning it now saves confusion later: a customer request is always called a ticket, never a conversation or thread. Agents are the people who answer tickets, customers are the people who open them, and every ticket moves through states (new, open, pending, closed) and priorities until it is resolved. Everything in this guide maps back to that vocabulary.

If you come from the paid helpdesk world, the quick framing is this: Zammad gives you the core of a hosted helpdesk — the shared inbox, the automation, the reporting — as open-source software you install yourself. That history is why the Zammad vs OTRS question comes up so often: OTRS is the older open-source incumbent in this lane, Zammad was created as its modern successor, and for a new installation Zammad is the actively maintained open source helpdesk choice. This guide covers Zammad only. (One lane line, drawn once: you may also see Chatwoot mentioned alongside Zammad — Chatwoot is a live-chat tool, while Zammad is a ticketing system. Different jobs, never rivals.)

How Do You Install Zammad on a Server?

Zammad installs from official system packages: you install Elasticsearch first, add the repository key and repository, run sudo apt install zammad (or the equivalent on your distro), then connect Elasticsearch and configure your web server. The new Zammad Hub documents package installation as the primary path for Ubuntu 22.04, 24.04, and 26.04, Debian 12 and 13, CentOS/RHEL 9 and 10, and openSUSE Leap/SLES 15 and 16 — check your distro against that list before you start. If you are doing a Zammad install, Ubuntu 24.04 is the distro to pick: the Zammad install Ubuntu admins follow is the documented arc above — Elasticsearch first, then the repository key and list, then the package.

The one dependency beginners must understand is Elasticsearch: Zammad's docs call it "optional, highly recommended" rather than a hard requirement, and it is not auto-installed — but the install instructions include it because it is, in the docs' own words, "crucial for a proper Zammad setup." Without it you lose fast full-text search across tickets, which is half the value of a helpdesk. The supported range is Elasticsearch 8.11 through 9.x generally, and for Zammad 7.2 and later you need 8.15 or newer but below 10. Alongside it you need PostgreSQL 15 or newer (MySQL is deprecated — Zammad has been PostgreSQL-only since version 7.0) and Redis 7 or newer (Valkey on RHEL/CentOS 10).

If packages feel like too much for a first look, there is a second route: Docker Compose, and the Docker stack includes Elasticsearch by default, which neatly removes the hardest dependency question. Our Docker beginner guide covers the container basics if that lane appeals to you. Either route lands you at the same place: the first-time setup wizard in your browser. The official repository key is at https://go.packager.io/srv/deb/zammad/zammad/gpg-key.gpg, and the Ubuntu 24.04 repository list is a one-line addition under https://go.packager.io/srv/zammad/zammad/stable/installer/ubuntu/24.04.list — the Hub page lists the variants for every supported distro.

Whichever route you pick, finish the web server step properly: Zammad sits behind a reverse proxy with a real domain name and a valid certificate, because the notification links it sends will use that address. Our Caddy beginner guide shows the fastest way to get a proxied site with automatic HTTPS. There is no official one-command installer — if someone offers you one, it is their script, not Zammad's.

What Happens in the First-Time Setup Wizard?

The wizard runs in a strict order: first the admin account, then the company information, then the email notification channel, and finally an optional first email channel — and you are logged in automatically when it finishes. The admin account's password policy is strict (at least 10 characters with two uppercase and two lowercase letters), so have a password manager ready. The company step lets you upload your logo, and Zammad auto-detects your server's fully qualified domain name from the request.

Two wizard details deserve your full attention. First, the notification channel: sendmail is the default, switchable to SMTP later, and notifications go out from noreply@<your-fqdn> — so get your domain and SSL certificate sorted before or immediately after the wizard. Our SSL certificate guide explains the setup. Second, the optional email channel: Zammad reacts to the emails it fetches — it deletes them from the mailbox and can send auto-generated answers — so if you are not ready for that, skip the step and connect the channel later from the admin settings.

The official recommended order after the wizard is worth following verbatim: configure groups, adjust triggers, set postmaster filters, define SLAs, add email/social channels and signatures, set up text modules, add organizations, define roles, invite agents, and set up backups. The rest of this guide walks that order for the pieces a beginner touches first.

How Does Your First Email Channel Create Tickets?

Connect an email channel and every incoming message becomes a ticket automatically. Your first Zammad email channel fetches mail over IMAP/SMTP, and Zammad also speaks the Microsoft 365 Graph and Google email APIs, so your support@ mailbox — or your Google Workspace or M365 shared mailbox — feeds the same queue as every other channel. The sender becomes a Customer user in the system; if they have never written before, Zammad creates that user for you.

The channel lesson to learn once is this: the email channel is a one-way door by design. Messages come in and turn into tickets — but remember the wizard warning from the previous section, because Zammad deletes the emails it fetches. Plan accordingly: use a dedicated support mailbox, never someone's personal inbox. Once the channel is live, test it the way the system expects: send an email to the support address and watch it appear as a new ticket.

How Do Groups and Roles Organize Your Team?

Zammad groups roles: groups decide who sees which tickets; roles decide what each person is allowed to do. A group is a department — Sales, Support, Billing — and tickets live inside groups, so an agent only sees the groups they belong to. A role bundles app permissions with a per-group access level: read, create, change, overview, or full. Zammad ships with three built-in roles — Admin, Agent, and Customer — and one user can hold several roles at once.

The practical order the docs recommend is groups first, roles later: decide your departments, then decide what each role may do inside each one. Start with two or three groups maximum — you can always split later, but a maze of groups on day one just confuses the agents.

What Does an Agent's First Ticket Look Like?

Your first ticket is the moment the whole system makes sense: a message arrives, it appears in the queue, an agent claims it, replies, and closes it. Run this arc once end to end before real customers arrive:

1. Send a test email to the connected support address and watch the ticket appear in the queue.
2. Open the ticket and read the full thread view — this is the agent's home screen.
3. Write an internal note first: notes are invisible to the customer, so this is the safe place to practice.
4. Send the actual customer reply, set a priority, and move the state forward.
5. Close the ticket and confirm the customer received your reply.

Inside the ticket, two features do most of the daily work. Internal notes let agents think out loud where the customer cannot see, and the customer sidebar shows every past ticket in one place — that history is what makes a helpdesk faster than a shared inbox. States and priorities keep the queue honest: mark what is urgent, close what is done, and never leave a ticket in "new" for a week.

How Do Triggers and SLAs Automate Your Support?

Zammad triggers are the system's "if this, then that" automation; Zammad SLAs are its promise-keeping. A trigger watches for an event — a new ticket, a reply, a state change — checks conditions, and runs actions like assigning the ticket or tagging it. Zammad ships with one trigger active out of the box: the auto-reply on new tickets, so every customer gets an immediate acknowledgment while the team is still reading.

SLAs live under Manage, and they enforce response discipline: they need a calendar defining your business hours, and they track First Response Time, Update Time, and Solution Time. A ticket that breaches its SLA gets escalated — flagged in red with notifications — so nothing quietly rots in the queue. The beginner move is to leave the default trigger alone and define one SLA with generous times before you ever promise customers a number.

How Do Text Modules Speed Up Replies?

Text modules are canned replies saved by admins and inserted with the :: shortcut or the toolbar button. They support variables — customer name, ticket number, agent name — so one template covers a hundred variations, and several useful ones ship with Zammad by default. Build your first five after a week of real tickets, not before: you will know which questions repeat only once you have seen the repeats.

How Do You Keep Zammad Healthy After Day One?

Updates come through your package manager and backups are your job — both are boring on purpose. Because you installed from the official repository, new Zammad releases arrive with your normal system updates; the 7.2.2 release that this guide is pinned to was itself an important security update, so do not let the server drift. Backups mean the database, the attachments, and the configuration — schedule them on day one, not the day you need them. If the Docker route was your entry point, the same rule applies to your volumes.

The single health check that matters most is search: if Elasticsearch is running and connected, full-text search across tickets is instant; if it stops, agents feel it immediately. Watch it the way you would watch the database — because for a helpdesk, search is the database.

7 Beginner Mistakes That Break a New Zammad Install

Sources

• Zammad product releases page (zammad.com) — 7.2.2 released 8 October 2026 (security update for packager.io DEB/RPM packages); 7.2 released 23 September 2026 (Admin Audit Log, spam protection, AI knowledge features); 7.1.3 released 25 August 2026; emergency 6.5.5 released 15 October 2026 for the unsupported 6.5 line.
• Zammad Hub — Package installation guide (next.zammad.org) — supported distros (Ubuntu 22.04/24.04/26.04, Debian 12/13, CentOS/RHEL 9/10, openSUSE Leap/SLES 15/16), Elasticsearch first, repository key and list URLs, sudo apt install zammad, connect-Elasticsearch and web-server steps, Docker Compose alternative.
• Zammad Hub — Package installation guide (next.zammad.org) — Elasticsearch "optional, highly recommended", "crucial for a proper Zammad setup"; version ranges 8.11–9.x, 8.15+ for Zammad 7.2; PostgreSQL 15+ supported, MySQL deprecated; Redis 7+, Valkey on RHEL/CentOS 10.
• Zammad System Documentation — First Steps (docs.zammad.org) — wizard order (admin account with password policy, company information with logo upload and FQDN auto-detection, email notification channel with sendmail default and noreply@<fqdn> sender, optional first email channel) and the recommended further-steps order.
• Zammad Hub — First steps tutorial (next.zammad.org) — wizard steps and the warning that Zammad reacts to fetched emails (deletes them, sends auto-generated answers).
• Zammad Admin Documentation — Start with Zammad (admin-docs.zammad.org) — email channels (IMAP/SMTP, M365 Graph, Google), inbound mail auto-creating tickets, unknown senders becoming Customer users, groups as departments, the three built-in roles and per-group access levels.
• Zammad Admin Documentation — Triggers (admin-docs.zammad.org) — if-this-then-that automation, one active trigger (auto-reply on new ticket) shipping by default.
• Zammad Admin Documentation — SLAs (admin-docs.zammad.org) — Manage > SLAs, business-hours calendar, First Response / Update / Solution times, escalation of expired tickets.
• Zammad Hub — Advanced features (next.zammad.org) — text modules (canned replies, :: shortcut, variables, defaults shipped).
• Simplicy blog — Zammad (blog.simplicy.info, ~February 2026) — personal Docker-Compose setup notes.
• Scaleway — Zammad ticketing tutorial (scaleway.com) — deploy guide on Ubuntu, 529 days old.
• HowVPS — How to Install Zammad 2.0 on CentOS 7 (howvps.com, 2019) — stale reference, obsolete.

Frequently Asked Questions

Is Zammad really free?

Yes — Zammad is open-source software you install on your own server, so there is no license fee and no per-agent charge. Your costs are the server it runs on and the time to maintain it. That is the core trade against paid hosted helpdesks: you pay in infrastructure and attention instead of subscriptions.

Do I need Elasticsearch to run Zammad?

Strictly, no — the docs call Elasticsearch "optional, highly recommended" — but in practice, yes. The install instructions include it because it is "crucial for a proper Zammad setup," and without it you lose fast full-text search across tickets. Use version 8.11 through 9.x, or 8.15+ if you are on Zammad 7.2 or later. The Docker Compose stack includes it by default.

Can Zammad connect to Gmail or Microsoft 365?

Yes. Zammad fetches mail over standard IMAP/SMTP and also speaks the Microsoft 365 Graph and Google email APIs, so a Google Workspace or M365 shared mailbox feeds the same ticket queue as a plain IMAP mailbox. Remember that fetched emails are deleted from the mailbox, so connect a dedicated support address.

What is the difference between Zammad and OTRS?

OTRS is the older open-source incumbent in the helpdesk lane; Zammad was built as its modern successor with a redesigned interface and architecture, and the two share some history. For a new installation today, Zammad is the current, actively developed choice — this guide covers it end to end.

What happens to my emails when I connect an email channel?

Zammad fetches the messages, turns each one into a ticket, and deletes the originals from the mailbox — and it can send auto-generated answers, which is why the setup wizard lets you skip that step. Never connect a personal inbox. Use a dedicated support mailbox so nothing important is deleted by automation.