How to Create Custom Ticket Fields in Freshservice?

Quick Summary

Custom ticket fields in Freshservice let you capture the exact information your team needs — beyond the default fields — so every ticket arrives with full context. This guide covers every field type available, shows you how to create and configure fields step by step, and shares best practices for keeping your ticket forms lean and effective.

Freshservice is a modern, cloud-based IT Service Management (ITSM) platform by Freshworks that helps IT teams streamline incident management, service requests, change management, asset tracking, and more. To explore the platform in depth, visit Freshservice ITSM Software.

Every organization collects slightly different information when a ticket arrives. A software company might need to know the affected application version. A hospital IT team might require the ward number. A university help desk might ask for the student’s faculty. Freshservice’s default ticket fields cover the basics — subject, description, priority, and category — but they rarely cover everything a specific team needs.

That is exactly where custom ticket fields come in. By adding fields tailored to your workflow, you ensure agents always have the right data to resolve issues faster, and managers always have cleaner data for reporting. This article reveals how to create, configure, and manage custom ticket fields in Freshservice from start to finish.

---

What Are Custom Ticket Fields in Freshservice and When Should You Use Them?

Custom ticket fields are additional data-capture inputs that administrators add to Freshservice ticket forms. Unlike built-in fields, custom fields reflect your organization’s specific processes and terminology. They appear on ticket creation forms, agent views, and can even surface in customer-facing portals, giving requesters a guided experience that captures the right information upfront.

You should consider adding a custom field whenever your team consistently asks the same follow-up question after a ticket arrives. For instance, if agents routinely reply to tickets asking “Which office location are you in?” that question belongs as a custom field — not a back-and-forth in the ticket thread. Similarly, if your reports frequently require filtering by a dimension that Freshservice doesn’t capture by default, a custom field solves that gap.

What Problems Do Custom Fields Solve in Practice?

Custom ticket fields address three common pain points that IT teams encounter as their Freshservice instance matures:

• Incomplete ticket information — Agents spend time chasing missing details instead of resolving issues. A well-placed custom field eliminates this delay by making key information mandatory at submission.
• Inconsistent categorization — Without structured fields, requesters describe the same issue in dozens of different ways, making reports unreliable. Dropdown or checkbox custom fields enforce consistent values.
• Limited reporting granularity — Freshservice’s built-in reports are powerful, but they can only filter on data that exists in structured fields. Custom fields expand your reporting dimensions significantly.

---

What Types of Custom Ticket Fields Does Freshservice Support?

Before you start building fields, understanding the available field types helps you choose the right format for each data point. Freshservice offers a comprehensive set of input types that cover nearly every use case:

Field Type	Input Format	Best Used For
Single-line Text	Free-text, one line	Employee ID, asset tag, short reference numbers
Multi-line Text	Free-text, multiple lines	Detailed descriptions, workaround instructions
Number	Integer or decimal input	Quantity affected, ticket reference numbers
Dropdown	Single selection from a list	Office location, department, affected system
Checkbox	True/False toggle	VIP user flag, remote worker indicator
Date	Date picker	Deadline, scheduled maintenance date
Date/Time	Date and time picker	Exact incident start time, SLA deadline
Decimal	Decimal number input	Cost estimates, hours spent
Dependent Field	Multi-level dropdown (parent/child)	Category > Sub-category > Item hierarchies
URL	Web address input	Link to affected system, error screenshot URL
Multi-select Dropdown	Multiple selections from a list	Affected services (can be more than one)

Notably, the Dependent Field type deserves special attention. It creates a cascading dropdown experience where the options in a child dropdown change based on what the user selected in the parent. This is ideal for category trees like Hardware > Laptop > Battery Issue, and it dramatically reduces the number of irrelevant options agents and users see at any one time.

---

How Do You Access the Ticket Fields Configuration in Freshservice?

Freshservice keeps all ticket field settings inside the Admin panel. You need Administrator-level access to create or modify ticket fields. Here is how to reach the configuration screen:

1. Log in to Freshservice as an Administrator.
2. Click the Admin icon (gear symbol) in the left-side navigation bar.
3. Under the Helpdesk section, select Ticket Fields.
4. The Ticket Fields screen displays all existing default and custom fields with a drag-and-drop interface.

From this screen, you can reorder fields by dragging them, toggle fields on or off for the agent view or the customer portal, and click Add New Field to start creating a custom field. Furthermore, Freshservice separates fields by ticket type — Incident, Service Request, Problem, Change, and Release — so you can tailor forms independently for each workflow.

Does Freshservice Support Different Fields for Different Ticket Types?

Yes — and this is one of Freshservice’s most useful form customization features. You can define completely different custom fields for each ticket type. For example, your Incident form might include fields for Severity Level and Affected Users Count, while your Change ticket form includes fields for Change Window Start Time and Rollback Plan Available. Switch between ticket types using the tabs at the top of the Ticket Fields screen to manage each independently.

---

How Do You Create a New Custom Ticket Field in Freshservice?

Creating a custom field in Freshservice takes just a few minutes once you know what data you want to capture. The process follows a consistent pattern regardless of the field type you choose.

What Steps Do You Follow to Add a Custom Field?

• On the Ticket Fields screen, click the Add New Field button on the right side of the page.
• Select the field type from the list (e.g., Dropdown, Date, Single-line Text).
• Enter a Field Label — the name agents and users see on the form.
• Optionally add a Placeholder Text to guide users on what to enter.
• Configure field-specific options (e.g., add dropdown choices, set date format).
• Toggle Required if agents or users must fill in this field before submitting.
• Toggle Visible to Customers if the field should appear on the self-service portal.
• Click Save Field to apply it to the ticket form immediately.

After saving, Freshservice adds the new field to the bottom of the ticket form. You can then drag it to the correct position in the form layout. Additionally, the field becomes available instantly in ticket filters, automation rules, and report builders — no extra configuration required.

How Do You Configure a Dropdown Custom Field with Multiple Options?

Dropdown fields require an extra configuration step: defining the list of choices. After selecting Dropdown as the field type and entering the label, you will see an Choices section where you add each option one by one. Freshservice also lets you reorder choices by dragging them and delete options you no longer need. For consistency, agree on naming conventions for your dropdown values before you create them — for example, always using title case (“North Office” rather than “north office”) ensures cleaner reports and filters downstream.

---

How Do You Configure Dependent Fields for Multi-Level Category Trees?

Dependent fields are the most powerful — and slightly more complex — custom field type in Freshservice. They build a hierarchical selection experience where each level of the dropdown filters the options available in the next level. This is especially useful for large organizations with many categories and sub-categories.

What Does the Setup Process for Dependent Fields Look Like?

To create a Dependent Field in Freshservice, follow these steps:

1. On the Ticket Fields screen, click Add New Field and select Dependent Field.
2. Enter a name for the top-level parent dropdown (e.g., “Category”).
3. Add the parent-level choices (e.g., Hardware, Software, Network, Facilities).
4. For each parent choice, click the expand icon to reveal the child level and add sub-choices (e.g., under Hardware: Laptop, Desktop, Printer, Monitor).
5. Optionally add a third level for even more granularity (e.g., under Laptop: Battery, Screen, Keyboard, Performance).
6. Save the field and drag it to the correct position on the form.

Consequently, when an agent or user selects “Hardware” in the first dropdown, the second dropdown instantly narrows to only hardware-related sub-categories. This eliminates irrelevant options and speeds up ticket submission considerably. Moreover, dependent field selections feed directly into Freshservice’s categorization reports, making trend analysis far more accurate.

---

How Do You Control Which Fields Appear on the Customer Portal?

Freshservice gives you independent control over which fields agents see internally and which fields customers see when submitting tickets through the self-service portal. This separation is important because customers generally need a simpler form than agents — too many fields on the portal overwhelms users and reduces submission rates.

Visibility Setting	Where It Appears	Recommended Use
Agent Only	Internal ticket form only	Internal tracking fields, SLA tags, cost codes
Visible to Customers	Portal and internal form	Issue description, affected service, urgency
Required for Agents	Agents must fill before closing	Resolution category, root cause
Required for Customers	Customers must fill at submission	Contact number, department, location

As a best practice, keep the customer-facing form as short as possible — typically five to eight fields — while allowing agents to see and fill in additional fields as they work the ticket. This approach balances capturing useful data without burdening the people submitting requests.

---

How Can You Use Custom Fields in Freshservice Automations and Reports?

One of the biggest advantages of custom ticket fields is that Freshservice automatically makes them available across the platform the moment you create them. You do not need to register them separately in each tool.

How Do Custom Fields Work with Freshservice Automation Rules?

Freshservice’s Workflow Automator and Supervisor rules both support custom fields as trigger conditions and action targets. For example, you can build an automation that:

• Automatically assigns a ticket to the Network team when the custom “Affected Service” dropdown is set to “VPN”.
• Sends an escalation email when the custom “Business Impact” field is set to “Critical” and the ticket has been open for more than two hours.
• Sets the Priority to Urgent whenever the custom “VIP User” checkbox is ticked.

Furthermore, custom fields work equally well in Freshservice’s Scenario Automations, which agents trigger manually. An agent can apply a scenario that populates several custom fields at once with a single click, saving time on repetitive ticket categorization.

How Do Custom Fields Enhance Freshservice Reporting?

Inside Freshservice Analytics, every custom field you create becomes an available dimension for filtering, grouping, and charting. This means you can build reports like “Number of tickets by Office Location per month” or “Average resolution time broken down by Affected System” — reports that simply would not be possible with default fields alone. Additionally, you can export ticket data with custom field values included for further analysis in external tools like Excel or Power BI.

---

What Are the Best Practices for Managing Custom Ticket Fields in Freshservice?

Adding too many custom fields creates form fatigue — users rush through fields or leave them blank, defeating the purpose. Here are the key principles that keep custom field configurations clean and effective over time:

• Audit before adding — Before creating a new field, check whether an existing field already captures that data under a different name.
• Use required fields sparingly — Only mark a field as required if the ticket genuinely cannot be routed or resolved without that information.
• Standardize dropdown values — Agree on a consistent naming convention and avoid duplicates (e.g., “N/A”, “Not Applicable”, “None” should be a single option).
• Group related fields visually — Freshservice lets you drag fields into logical clusters on the form, which makes the experience less intimidating for users.
• Retire unused fields — Deactivate fields you no longer use instead of deleting them, so historical ticket data remains intact.
• Document your field library — Maintain an internal record of every custom field, its purpose, and who requested it, to prevent duplication over time.

---

What Should You Take Away About Custom Ticket Fields in Freshservice?

Custom ticket fields transform Freshservice from a generic help desk tool into a precisely configured system that matches your organization’s unique processes. By capturing the right data at the point of ticket submission, your agents spend less time asking follow-up questions and more time resolving issues — and your managers gain reporting dimensions that reflect how your business actually operates.

Moreover, the combination of custom fields with Freshservice‘s automation engine and analytics platform multiplies their value significantly. A single well-designed dropdown field can simultaneously route tickets to the right team, trigger SLA rules, and power monthly trend reports — all without any additional effort after the initial setup.

Start by mapping the questions your team consistently asks after a ticket arrives, then build custom fields to capture those answers upfront. Review your field library quarterly to retire what you no longer need and add what your team requests. The result is a Freshservice instance that grows smarter alongside your team. To discover what else the platform can do, visit Freshservice ITSM Software.

---

Frequently Asked Questions

---