Chatwoot vs Zammad: Chat-First or Ticket-First Support?

Chat-First vs Ticket-First: What This Means

The fundamental difference is how each platform organizes work.

Chatwoot is a chat application. It pulls every message - live chat, email, WhatsApp, Instagram DM, SMS - into a unified inbox. Your team sees all conversations in real time. You assign them like you would a Slack thread. This is natural for support teams that manage high-velocity, multi-channel conversations.

Zammad is a ticketing system. It converts every incoming message into a structured ticket with fields, routing rules, SLAs, and audit trails. This is natural for teams that manage formal workflows: IT service desks, help desks, support centers with complex escalation.

Neither is wrong. They serve different mental models. If your team thinks "inbox," pick Chatwoot. If your team thinks "ticket," pick Zammad.

Feature Comparison

When To Choose Chatwoot

Choose Chatwoot if:

• Your team manages conversations across multiple channels (WhatsApp, Instagram, email, SMS all mixed).
• You prioritize speed and real-time response: your team needs to see and reply to messages in seconds, not minutes.
• Your industry is high-velocity (e-commerce, SaaS, consumer apps): you want a fast inbox, not formal ticketing.
• You value simplicity: assign and reply, rather than routing rules and SLA automation.
• You want a modern interface that feels like chat apps your team already uses.

When To Choose Zammad

Choose Zammad if:

• You manage formal help desk workflows: IT support, infrastructure issues, service requests with clear handoffs.
• You need audit trails for compliance: your industry requires tamper-proof records of who changed what, when (finance, healthcare, regulated sectors).
• Your team is larger and needs complex routing: auto-assign to the right department or agent based on category, priority, or skill.
• You manage email-heavy support: your primary channel is email, and tickets are natural.
• You have SLA requirements: track response time and resolution time formally.

Infrastructure and Self-Hosting

Both are free to self-host (Chatwoot is MIT; Zammad is AGPLv3). But deployment effort differs.

Chatwoot: Docker-based setup. Single machine can run it comfortably. Fast deployment (minutes). Requires less infrastructure tuning.

Zammad: Built on Ruby on Rails. Requires PostgreSQL database, Elasticsearch for search, and Redis for jobs. More moving parts. Larger resource footprint. Production deployments are more complex. 20K+ commits and 10+ year track record mean it's mature, but it's also heavier.

This is where Opsily saves the most time. You pick Chatwoot or Zammad, we handle the infrastructure, patching, backups, and scaling. No DevOps knowledge required.

Pricing Models

Chatwoot Cloud (Official Cloud)

Chatwoot charges per agent per month on their hosted cloud:

• Hacker (Free): Up to 2 agents, 500 conversations/month
• Tier 1: $19/agent/month
• Tier 2: $39/agent/month
• Tier 3: $99/agent/month

Example: A 5-person support team on Tier 2 costs $195/month ($39 x 5).

You pay only for the agents using the system. Inactive agents don't count. This is predictable and scales linearly.

Zammad Cloud/Hosted

Zammad pricing from available sources shows per-agent pricing in EUR:

• Entry Plan: EUR 7/agent/month (annual billing)
• Mid Plan: EUR 16/agent/month
• Enterprise Plan: EUR 25-27/agent/month

Example: A 5-person team on the Mid Plan costs EUR 80/month (EUR 16 x 5).

Zammad also sells direct enterprise support, and hosted pricing varies by region and commitment.

Self-Hosted (Free)

Both are free to download and self-host. What costs money:

• Infrastructure: Server, database, backups, monitoring (EUR 100-500+/month depending on scale).
• DevOps time: Setup, patching, troubleshooting (20-40 hours of your engineer's time).
• Downtime risk: No SLA if it's your responsibility.

With Opsily, all infrastructure and operations are included. You get 99.9% uptime SLA, automatic backups, security patches, and 24/7 monitoring. No separate DevOps team needed.

What Pricing Doesn't Show

Both platforms exclude add-on costs: integrations (Slack, Zapier, etc.), SMS credits (Twilio), and premium support. Chatwoot's AI assistant (Captain) uses a credits system. Zammad's enterprise features (SSO, advanced integrations) cost extra.

Real-World Scenarios

Scenario 1: E-Commerce Store (Chatwoot)

Your store has live chat on the website, WhatsApp business account for customer support, and an email inbox. Customers message from different channels throughout the day.

Chatwoot is ideal here. One unified inbox. Your support team (2-3 people) sees every message - "customer asks about order on WhatsApp," "another asks about shipping on live chat," "email comes in with returns request." All in one place. Assign, reply, done. Typical cost: $39-78/month.

Scenario 2: IT Help Desk (Zammad)

Your internal IT team manages 500+ employees. Requests come in through email, a self-service form, and phone tickets. Each request has a priority, category, assignment, SLA, and history that must be auditable.

Zammad is ideal here. Every request is a ticket. Routing rules auto-assign to the right person. SLAs track response time. Audit trails show who resolved what and when. Typical cost: EUR 50-80/month for a team of 5.

Scenario 3: Regulated Industry (Compliance Audit)

You work in finance, healthcare, or government. Regulators may audit your support process. You need to prove that customer requests were handled correctly, who handled them, and when.

Zammad's granular audit logs are built for this. Chatwoot has logs, but Zammad's compliance angle is stronger. Zammad is Berlin-based, operates under GDPR natively, and many of its users are regulated enterprises. This is a key differentiator.