How to Build Employee Service Request Forms in Freshservice?
Quick Summary
A request form is often the first real interaction an employee has with IT, so a confusing form creates a bad impression before an agent even sees the ticket. Freshservice ITSM Software gives administrators a flexible, drag-and-drop way to design request forms that capture exactly what agents need, without overwhelming the person submitting the request. In this article, you will learn how to plan, build, and refine employee service request forms in Freshservice, so every ticket that lands in your queue arrives complete and ready to action.
What Makes a Service Request Form Effective?
Before diving into configuration, it helps to understand what separates a good form from a frustrating one. An effective form asks for only the information an agent truly needs, presents fields in a logical order, and adapts based on earlier answers so employees never see irrelevant questions.
Freshservice supports this goal through a flexible field manager, so admins are not stuck with a rigid, one-size-fits-all template. Instead, every service item can have its own custom form, tailored to the specific request it represents.
Why Does Form Design Affect Ticket Quality?
When a form is vague, employees leave fields blank or enter unclear answers, and agents then have to chase down details before they can start working. Consequently, resolution times stretch out and both sides get frustrated. A well-designed form, on the other hand, front-loads the right questions, so agents receive complete context immediately and can begin fulfilling the request right away.
How Does Freshservice Approach Form Building?
Freshservice separates two related but distinct concepts: ticket fields, which apply broadly across the service desk, and service catalog item fields, which apply to a specific request type. Understanding this distinction matters, since it determines where you go to make a particular change.
Where Do You Configure Ticket Fields in Freshservice?
Ticket fields form the foundation that every request shares, including default fields like requester, subject, priority, and category. Because these fields appear across the whole service desk, admins usually configure them at the global level first.
To reach the ticket field settings, follow this path:
- Go to Admin > Global Settings > Service Management > Field Manager > Ticket Fields, if configuring at the global level.
- Alternatively, go to Admin > Workspace Settings > Workspace > Service Management > Service Desk Settings > Field Manager, if configuring at the workspace level.
- Select the module you want to edit, choosing from Ticket, Problem, Change, Release, or Time Entry fields.
- Click any default field to view and update its properties, then click Done.
How Do You Add a New Custom Field to a Ticket Form?
Adding a new field only takes a few steps once you are inside the Field Manager. First, select the field type you need from the Drag & Drop Field options, such as Date, Dropdown, or Checkbox. Next, enter a clear name in the Field Label box, since employees will see this label when filling out the form. Afterward, adjust any additional properties, such as whether the field is mandatory, and click Done to add it to the form.
Because default fields like requester, subject, status, priority, and category belong to the global form fields, the order in which the fields are organized can be rearranged as per the local workspace requirements, though default fields cannot be modified or deleted. This means you can reorder existing fields freely, but you will always work around the built-in ones rather than removing them entirely.
What Is the Difference Between Global and Workspace-Level Fields?
Since content fields and dynamic sections can be configured only at a workspace level and cannot be configured for global form fields, some customization options are only available once you drill down into a specific workspace. Additionally, the visibility of form fields created at a workspace level is limited to that particular workspace, while the global form fields can be accessed and made visible across all the workspaces. Therefore, plan carefully before deciding whether a field belongs at the global level or should stay scoped to one workspace.
How Do You Build a Custom Form for a Service Catalog Item?
While ticket fields apply broadly, service catalog items often need their own dedicated forms. For instance, a laptop request needs different fields than a software license request, even though both eventually become tickets.
Which Field Types Can You Use in a Service Request Form?
Freshservice offers a wide range of field types, so admins can capture almost any kind of information an employee might need to provide. The table below summarizes the most common options.
| Field Type | What It Captures |
|---|---|
| Single Line Text | A short line of free text, such as a device serial number |
| Paragraph Text | Longer free-text input, useful for detailed explanations |
| Checkbox | A true/false selection, such as agreeing to a policy |
| Number / Decimal | Numeric input, including whole numbers or decimals |
| Dropdown / Multi Dropdown | A choice from a predefined list, single or multiple selections |
| Date | A specific calendar date, such as a requested start date |
| Dependent Field | Values that change based on an earlier field’s selection |
| URL | A website address, useful for linking supporting documents |
| Rich Text Editor (RTE) | Formatted text with images, tables, and links |
| Attachment | Uploaded files, such as screenshots or signed documents |
| Formula | Real-time calculations based on other field values |
Because these configurations apply to both the agent and requester service request forms, and any modifications or updates made by admins take effect instantly, changes show up immediately without requiring a system restart or delay. That said, some newer field types come with limits worth knowing before you rely on them heavily.
Are There Limits on These Field Types?
Yes, several of the newer field types carry specific restrictions. For the Rich Text Editor field, the content limit for each RTE field is 1 MB, and you can add up to 5 RTE fields per service item. Similarly, you can add up to 10 Attachment fields per service item, and you can add up to 5 Formula fields per service item. Beyond individual field types, Freshservice also caps the overall form size, since the total number of fields must not exceed the maximum limit of 150 across a form.
How Do You Actually Add a Field to a Service Item?
To add a custom field to a specific service item, open the service catalog item you want to edit, then navigate to its Custom Fields section. From there, drag the desired field type onto the form, name it clearly, and configure whether it should be mandatory, editable by the requester, or visible only to agents. Once satisfied, save the changes so the updated form goes live for future requests.
How Do You Use Dependent Fields to Simplify Long Forms?
Long forms discourage completion, especially when many fields do not apply to every request. Dependent fields solve this problem by showing or hiding options based on an earlier answer, which keeps the form short and relevant for each individual employee.
What Is a Practical Example of a Dependent Field?
Consider a repair request form. Instead of listing every possible device type at once, a dependent field can narrow the choices step by step. For example, if you provide repair services, you can share information such as “TV → Plasma → Sony Bravia 50-inch” or “TV → CRT → LG 32-inch” via a dependent field setup, since dependent fields are extremely helpful when you need to offer up to three levels of options to choose from.
How Do Dynamic Dropdowns Work With Data Sources?
Beyond manually typed dependent fields, Freshservice also supports dropdowns populated from live data. Admins can choose a custom dropdown, which allows manually defining the list of values, or select from a data source, which dynamically fetches values based on standard objects. For instance, a dropdown could filter by Location or Department when the data source selected is All Users, so the choices employees see automatically reflect real company data rather than a static list that quickly goes out of date.
How Do You Configure Requester Permissions on a Form?
Not every field should be editable, or even visible, to the person submitting the request. Some fields exist purely for internal agent use, while others need to stay locked once submitted.
How Do You Control Whether a Requester Can Edit a Field?
Freshservice lets admins set this at the individual field level. To adjust these permissions:
- Open the relevant service item, then go to its Custom Fields section.
- Click the specific custom field you want to configure.
- Ensure the Display to Requester checkbox is selected if employees should see the field at all.
- Enable the Requester can edit checkbox if they should be able to change the value themselves.
- Click Done to save the update.
This setup proves especially useful after a rejection, since enabling edit access lets requesters correct a field in the support portal after an approver rejects their service request, rather than forcing them to submit an entirely new ticket from scratch.
Can Employees Add Their Own Custom Details?
Beyond service item fields, Freshservice also supports custom fields tied directly to the requester’s profile. Admins configure these by going to Admin > User Management > User Fields, or Admin > Global Settings > User Management > User Fields if the account has more than one workspace. Once created, these custom fields become applicable for both agents and requesters, which means a workflow built around a requester field also works consistently when that same person is acting as an agent.
How Do You Test a Request Form Before Publishing It?
Testing prevents avoidable frustration once a form goes live to the entire company. A field that looks fine in the admin panel might behave unexpectedly once a real employee starts filling it out.
Before publishing broadly, walk through the form yourself as if you were an employee. Check whether:
- Every mandatory field is genuinely necessary, rather than adding friction for no reason
- Dependent fields reveal the correct next options at each step
- Dropdown values sourced from live data pull in the right results
- Attachments and rich text fields render properly on both desktop and mobile
Afterward, consider running the form past a small pilot group, similar to how you would test a new service catalog item. Their feedback often surfaces confusing wording or missing options that are easy to miss when you already know exactly what the form is supposed to capture.
Conclusion
Building a strong employee service request form takes more thought than simply listing every possible question you can imagine. Freshservice makes the technical side straightforward, since custom fields, dependent logic, and requester permissions are all just a few clicks away inside the Field Manager and Service Catalog settings. However, the real work lies in deciding what to ask, in what order, and who should see each field. Once you get the balance right, a Freshservice request form becomes far more than a data entry screen. It becomes the starting point for a smooth, well-documented request that agents can act on immediately, without back-and-forth clarification slowing everything down.
Frequently Asked Questions
A single form should stay under the platform limit, since the total number of fields must not exceed the maximum limit of 150 across a form. In practice, most well-designed forms use far fewer fields than this ceiling, since shorter forms generally lead to higher completion rates and fewer errors.
Yes, under specific conditions. Admins can enable the Requester can edit option on individual custom fields, which allows an employee to update their answer, particularly useful after an approver rejects the original request and sends it back for corrections.
Ticket fields apply broadly across the service desk and include default fields like requester, subject, and priority. Service catalog item fields, on the other hand, belong to a specific service request type, such as a laptop request or a software license request, and only appear on the form for that particular item.
