Ticket Statuses
Ticket Statuses define the lifecycle of support tickets in Frappe Helpdesk. They indicate the current stage of a ticket, help agents track progress, and determine how Service Level Agreements (SLAs) behave throughout the support process.
Each status belongs to a category that controls whether the SLA timer continues running, pauses, or stops completely. Statuses can also have different labels for agents and customers, making communication clearer while preserving internal workflows.
Tip
Every Helpdesk instance must always have at least one enabled status in each category: Open, Paused, and Resolved.
Managing Ticket Statuses
Ticket Statuses are managed through the HD Ticket Status DocType.
- Switch to Desk.
- Search for HD Ticket Status.
- Open the HD Ticket Status DocType.
- Create a new status or edit an existing one.
- Save your changes.
Ticket Status Fields
Each Ticket Status contains the following properties:
| Field | Description |
|---|---|
| Enabled | Determines whether the status is available for use. |
| Agent Label | The status name displayed to support agents. |
| Order | Controls the position of the status in dropdown lists. |
| Different Customer View | Allows customers to see a different status label than agents. |
| Customer Label | The label shown to customers when a different view is enabled. |
| Category | Determines how SLA timers behave: Open, Paused, or Resolved. |
| Color | Displays the status using a colored badge for easier identification. |
Status Categories
Every ticket status belongs to one of three categories, each affecting SLA calculations differently.
| Category | SLA Behavior |
|---|---|
| Open | The SLA timer continues running. |
| Paused | The SLA timer is temporarily paused until the ticket moves back to an Open status. |
| Resolved | The SLA timer stops because the ticket is considered completed. |
Choosing the correct category is important because it directly affects first response and resolution time calculations.
Default and Reopen Status
Helpdesk automatically assigns statuses when tickets are created or reopened.
Global Settings
From HD Settings, you can configure:
- Default Ticket Status — Applied when a new ticket is created.
- Reopen Ticket Status — Applied when an existing ticket is reopened.
SLA-specific Settings
Each SLA can define its own default and reopen statuses.
When both are configured, Helpdesk follows this priority:
- SLA configuration
- HD Settings (fallback)
This allows different teams or support workflows to use different ticket lifecycles while still maintaining system-wide defaults.
Customer-Friendly Status Labels
Some internal workflow names may not be suitable for customers.
By enabling Different Customer View, you can display a separate status label on the customer portal while agents continue seeing the internal status name.
For example:
| Agent View | Customer View |
|---|---|
| Pending Internal Review | In Progress |
| Waiting for Engineering | Being Investigated |
| Awaiting Customer Reply | Waiting for Your Response |
Permissions
Only users with the following roles can manage ticket statuses:
- System Manager
- Agent Manager
These users can create, edit, and delete custom ticket statuses.
Important Rules
- The Closed status cannot be deleted.
- For the Closed status, only the Color and Order fields can be modified.
- If Different Customer View is enabled, a customer label becomes mandatory.
- Every Helpdesk instance must always contain at least one enabled status in each category: Open, Paused, and Resolved.
- Status categories directly control SLA timer behavior.
Typical Workflow
- A new ticket is created and receives the default status.
- An agent begins working on the ticket while the SLA timer continues running.
- If waiting for customer input, the ticket can move to a paused status.
- Once the issue is resolved, the ticket moves to a resolved status and the SLA timer stops.
- If the customer responds again, the ticket can automatically return to the configured reopen status.
Related Features
- Service Level Agreements (SLA)
- Ticket Priorities
- Ticket Types
- HD Settings
- Customer Portal
Best Practices
- Keep status names simple and meaningful for agents.
- Use customer-friendly labels when internal workflow names may be confusing.
- Choose the correct status category to ensure SLA timers behave as expected.
- Configure default and reopen statuses for each SLA when different workflows are required.
- Avoid creating unnecessary statuses that duplicate existing workflow stages.