SOURCE-BASED ANALYSIS · NO HANDS-ON RATING
Give each field an operational job
Freshdesk describes ticket fields as metadata about a request and provides default fields such as requester, subject, source, status, priority, group and agent. Add a custom field only when its value changes routing, ownership, reporting or the next support action. A field collected “for later” creates maintenance and privacy cost without a clear outcome.
Design choices before labels
For a fictional equipment support desk, “Issue type” might contain Access, Billing and Product fault. Define who selects it, whether the customer sees it, which automations use it and how an agent corrects a wrong value. Test renamed and retired choices before changing production because Freshdesk warns that deleting choices can affect tickets, automations and analytics.
Separate status from category
Status represents lifecycle state; issue type describes the request. Freshdesk documents Open, Pending, Resolved and Closed as default statuses, with customer replies moving a ticket back to Open. Do not use a category field as a hidden substitute for workflow state. Document what action moves a ticket into and out of every custom status.
| Field | Question answered | Dependent configuration |
|---|---|---|
| Issue type | What kind of request is this? | Routing and reporting |
| Status | What is the current lifecycle state? | SLA clock and agent queue |
| Priority | How urgently should it be handled? | SLA targets and ordering |
Make SLA behavior explicit
Freshdesk ties its standard Priority field to SLA policies and allows SLA behavior to be configured for custom sources and statuses. For every waiting status, decide whether the SLA timer should continue or pause, then create a timed synthetic ticket to verify the chosen behavior. Do not infer an SLA result from the label alone.
Test the complete intake path
- Submit a synthetic request through each relevant form or channel.
- Verify required fields, customer-facing labels and default values.
- Confirm source, priority, group and status are populated as intended.
- Run the routing and notification rules that depend on the values.
- Change a field as an agent and verify reporting and SLA behavior remain understandable.
Maintain a field dictionary
Record the internal name, public label, type, allowed values, owner, purpose and dependent rules. Review fields with no recent use and choices that agents frequently override. Retire a value through a migration plan rather than deleting it without checking historical tickets and downstream reports.
Sources and verification
Official documentation checked on 2026-10-29. Worked examples are hypothetical planning exercises, not measured product benchmarks.