Frappe Helpdesk

communicationsmall business

Open source customer support platform built on the Frappe framework. Ticket management, SLA tracking, automation rules, a customer portal, and a clean agent interface — all self-hostable and free for teams that do not want to pay Zendesk's per-agent fees

#helpdesk#support#ticketing#sla#self-hosted#frappe

Quick Start

git clone https://github.com/frappe/frappe_docker && cd frappe_docker && docker compose -f compose.yaml -f overrides/compose.helpdesk.yaml up -d

Overview

Frappe Helpdesk is an open source customer support platform built on the Frappe framework — the same foundation that powers ERPNext. It provides a ticketing system with SLA management, automation rules, a customer-facing portal, and a clean agent interface, all self-hostable without the per-agent pricing that makes Zendesk and Freshdesk expensive as teams grow.

The agent interface puts the ticket conversation, customer history, and ticket metadata on one screen. Agents do not need to navigate between tabs to see who they are talking to, what their previous issues were, or what SLA deadline applies. Tickets are assigned to teams or individual agents, and status updates are tracked with timestamps throughout the lifecycle.

SLA policies define response and resolution time targets by ticket priority. When a ticket is at risk of breaching its SLA, Frappe Helpdesk escalates it automatically and can notify supervisors. Automation rules handle the routine triage work — routing tickets from specific customers to dedicated teams, auto-assigning based on subject keywords, sending acknowledgement messages when tickets are opened — so agents spend time on resolution rather than administration.

The customer portal gives end users a place to submit tickets, track their open requests, and search a knowledge base without emailing support directly. For products with a self-serve support model, this reduces the volume of inbound tickets for issues the knowledge base already answers.

The deployment path uses the Frappe framework, which introduces more moving parts than a typical single-container app — MariaDB, Redis, background workers, and the Frappe bench tooling. The official Docker Compose setup handles this, but it requires more initial configuration than simpler PHP-based help desks like FreeScout.

Frappe Helpdesk: Pros & Cons

Pros (The Wins)Cons (The Friction)
Clean agent UI:
Ticket, conversation, and
context on one screen.
AGPL licence:
Commercial use or
white-labelling needs review.
SLA + escalation:
Response and resolution
targets with auto-escalation.
Frappe deployment:
More moving parts than
simpler help desks.
Automation rules:
Auto-route, assign, and
acknowledge without manual triage.
Smaller community:
Fewer guides and integrations
than Zammad or FreeScout.
Customer portal:
Self-service ticket submission
and knowledge base.
ERPNext overhead:
Frappe ecosystem benefits
only if you use it.

Use Cases

Specific ways to use Frappe Helpdesk for your workflow.

01
Run a customer support inbox where tickets are triaged, assigned to agents, and tracked through resolution with SLA deadlines
02
Give customers a self-service portal to submit tickets, check status, and browse a knowledge base without emailing support
03
Automate ticket routing — assign incoming tickets to the right team based on subject, customer tier, or product area
04
Replace a shared Gmail inbox used as a makeshift help desk with a proper ticketing system that tracks response times

Deployment Strategy

Recommended ways to host Frappe Helpdesk in your own environment.

docker
self-hosted