Set up Frappe Helpdesk

Docs › Setup guides

Frappe Helpdesk Setup Guide

Frappe Helpdesk setup, step by step: install the app, add agents and teams, connect email, ticket types and priorities, SLAs, saved replies and knowledge base.

4 min read · Updated November 2026 · By Vivek Choudhary

Frappe Helpdesk gives your support team a fast ticket screen at /helpdesk and gives customers a portal to raise and follow tickets. This Frappe Helpdesk setup guide follows a sensible order, so the first real ticket is routed, timed and answered correctly. For an overview, see Frappe Helpdesk explained.

Before you start

  • Decide where it will run: Frappe Cloud, or added to an existing Frappe or ERPNext bench.
  • List your agents and group them into teams (for example Billing, Technical, Onboarding).
  • Have the support email address and its login or app password ready.
  • Agree response and resolution targets per priority, and your support working hours and holidays.
  • Collect your most common customer questions; they become saved replies and knowledge base articles.

Step-by-step setup

  1. Install the app. On Frappe Cloud, sign up for Helpdesk or add it to an existing site from the Marketplace. On your own bench run bench get-app helpdesk --branch main and then bench --site yoursite install-app helpdesk. A fresh self-hosted production server can use Frappe's easy-install script.
  2. Open the agent view. Go to yoursite/helpdesk. Settings open as a panel inside the app, grouped into Email Settings, App Settings, Customer Portal and Integrations.
  3. Settings > App Settings > General. Review the general options such as branding and defaults before agents start work.
  4. Settings > Invite Agents, then Agents. Invite each agent by email. Check the agent list afterwards and deactivate anyone who should not take tickets.
  5. Settings > Teams. Create teams and add agents to them. Teams are used to route tickets and to limit who sees what.
  6. Settings > Email Settings > Email Accounts. Add the support mailbox and enable incoming and outgoing. Emails to this address become tickets, and agent replies go back from the same address. Set up Email Notifications for customers and agents as needed.
  7. Ticket types and priorities. Ticket types (HD Ticket Type) describe the kind of request, such as Bug, Question or Billing, and can carry a default priority. Priorities (HD Ticket Priority) have a name and level. Keep both lists short so agents choose consistently. If a settings screen for these is not shown in your version, manage them from the desk list of the same DocType.
  8. Settings > Business Holidays. Create the holiday list your SLAs will use, so deadlines skip non-working days.
  9. Settings > SLA Policies. Create a policy with a name, the holiday list and working hours per day. In the priorities table set the First Response Time and Resolution Time for each priority and mark one as the default priority. Add assignment conditions if the SLA applies only to some customers or ticket types, and mark one SLA as the default.
  10. Settings > Assignment Rules. Auto-assign new tickets to agents, for example in turn or by workload, and use conditions such as team, ticket type or priority.
  11. Settings > Saved Replies. These are the canned responses. Write replies for your top questions with clear titles, and limit them to a team if they are team-specific.
  12. Settings > Customer Portal > Knowledge Base and the agent Knowledge Base page. Create categories, then articles in plain language with steps and screenshots. Publish only reviewed articles; customers can search them from the portal before raising a ticket.
  13. Settings > Customer Portal > Portal Settings. Choose how customers sign up and log in, then test the portal as a customer: raise a ticket, reply to it and view its status.
  14. Integrations (optional). Settings include telephony and an ERPNext integration. Set these up only after the email flow works.

Where things live

SettingDocType behind it
Agents and teamsHD Agent, HD Team
Ticket types, priorities, statusesHD Ticket Type, HD Ticket Priority, HD Ticket Status
SLA policiesHD Service Level Agreement
Saved repliesHD Saved Reply
Knowledge baseHD Article, HD Article Category
CustomersHD Customer

Check your work

  • Send an email from an outside address and confirm a ticket is created, assigned and shows an SLA due time.
  • Reply as an agent and confirm the customer receives it from the support address.
  • Raise a ticket from the customer portal and confirm the customer can see the reply.
  • Insert a saved reply on a ticket and check the formatting.
  • Search the knowledge base from the portal for a common question and confirm the article appears.

Common mistakes

  • Connecting a personal mailbox instead of a shared support address.
  • SLAs without a holiday list or working hours, so tickets breach overnight and on Sundays.
  • Too many priorities and ticket types, which agents then pick at random.
  • Going live without assignment rules, so tickets sit unassigned.
  • Publishing knowledge base articles that nobody has reviewed.

After go-live

  • For the first few weeks, check every day for tickets with no agent or with a breached SLA, and fix the rule that let it happen.
  • Read the tickets that came in by email and look for repeated questions. Each repeated question is a candidate for a saved reply or a knowledge base article.
  • Review SLA targets after a month of real data. Targets nobody can meet only teach agents to ignore them.
  • Remove agents who leave the company straight away, so tickets are not assigned to them.
  • Ask a few friendly customers to use the portal and tell you what confused them. Small wording changes in the portal and articles often cut repeat tickets.
  • Keep one person responsible for the knowledge base, so articles stay current when your product or process changes.

Using Frappe CRM for sales as well? See setting up Frappe CRM.

Sources

Written from the official documentation and source code below. Menus and fields can differ between versions, so check the docs for your version.

Planning ERPNext or a Frappe app for your business? See our ERPNext implementation and Frappe development services, or talk to us.
ERPWork app icon
ERPWork: ERPNext on your phoneFree Android app for your ERPNext site: check in with location, approve documents, see sales and stock dashboards and get notifications.

Get it on Google PlayLearn more →