Freshdesk Custom Fields That Earn Their Place
Every one of your Freshdesk custom fields is a question you make a customer answer before you've helped them. A few are worth it.
Freshdesk custom fields, forms and dependencies
Custom fields capture one piece of information each. Ticket forms group them for a request type, so a returns question doesn't show technical fields.
Dependent fields are the useful trick: choosing a category reveals only the relevant sub-options, which keeps a form short while still capturing structured data.
Which fields to keep
A field earns its place if the answer changes routing, priority, or a report you genuinely read.
Fields that fail: anything agents fill in afterwards for a report nobody reads, and anything a customer has to guess. A guessed value looks like data and is worse than a blank.
Long forms create duplicates
Every required field loses you a percentage of submissions. Some of those people email instead. A few do both, abandoning the form, emailing, then coming back and submitting anyway.
That produces two tickets about one problem, arriving on two channels, worded differently. Shorter forms mean fewer of them.
Frequently asked questions
Are Freshdesk ticket fields the same as custom objects?
No. Freshdesk ticket fields describe one ticket. Custom objects in Freshdesk are separate records that tickets point at, which is what you want for assets, subscriptions or anything with a life of its own.
How many Freshdesk custom fields should a form have?
As few as change what happens next. Use dependent fields to keep it short while still capturing structure.
Can I show different forms for different request types?
Yes, on the plans that support multiple ticket forms, and it's one of the better reasons to be on them.
Fewer fields, fewer duplicates
People who abandon a form often email and then submit anyway. Ticket Merger merges the pair automatically.
Start free trial14-day free trial. No credit card required.