Zendesk Ticket Forms
Zendesk ticket forms are a named set of fields in a chosen order. Most teams need two or three. Some end up with fourteen and can't remember why.
What Zendesk ticket forms actually are
Every Zendesk account has one form whether you notice it or not. Multiple forms let you show a different set of fields depending on what the request is about, and they can be exposed to end users in the help centre or kept agent-only.
Multiple ticket forms sit on the higher plans, so check what your account includes before designing around them. If you only have one form, conditional fields still do a lot of the same work.
When a form beats a field
This is the decision that matters, and there's a clean test for it.
Add a field when you need one more piece of information about a request you already understand. Order number. Affected product. Severity.
Add a form when the entire set of questions changes. A refund request and a bug report don't share a shape: different fields, different required answers, different follow-up. Forcing both through one form means either everyone sees irrelevant questions or nothing is required and agents chase details all day.
If two request types share more than half their fields, they're one form with conditions, not two forms.
The failure mode is real and expensive. Fourteen forms means fourteen field sets to maintain, fourteen things to update when a product name changes, and a dropdown so long that end users pick whatever is first.
Conditional fields, which do the heavy lifting
Conditions show or hide fields based on the answer to another field on the same form. Pick "Hardware" and the serial number field appears. Pick "Billing" and it does not.
Two things people miss:
Used properly, conditions let one form of thirty fields feel like a form of four. See custom fields for how to structure the underlying fields.
How forms affect routing
The form itself is a trigger condition. "Ticket form is Bug Report, then assign to Engineering Support and add tag bug" is one rule that replaces a lot of keyword guessing.
That's the strongest argument for forms in a support team that routes by group. The customer tells you what kind of request it's by choosing the form, and the routing follows from a fact rather than from a text match on the subject line.
It is also the reason your form names should be written for customers, not for your org chart. "Report a problem with an order" routes better than "Tier 2 Fulfilment", because people pick the one that sounds like their problem.
And what they do to reporting
Ticket form is available as an attribute in Explore, which makes it one of the cheapest useful segmentations you have. Volume by form, resolution time by form, CSAT by form.
The catch: change a form later, and historical tickets keep the form they were created with, while the fields on it may have moved. If you rename a form, your report keeps working. If you delete one, tickets that used it get awkward. Deactivate instead of deleting, always.
One practical habit. Before you add form number five, open Explore and check the volume on forms three and four. Roughly a third of the time nobody has used them in a quarter, and the answer is to switch them off rather than add another.
Frequently asked questions
Do multiple ticket forms change routing?
They can. Zendesk multiple ticket forms let a trigger route on which form was used, and Zendesk form routing plus Zendesk conditional fields is how you ask three questions instead of fifteen.
How many Zendesk ticket forms should we have?
Two to four for most teams. If two forms share more than half their fields, merge them and use conditional fields instead.
Do I need a paid plan for multiple ticket forms?
Multiple forms are a higher-tier feature. Conditional fields on a single form get you most of the way on lower plans.
Can I hide a ticket form from customers?
Yes. Each form can be agent-only, which is how you keep internal request types out of the help centre while still using them internally.
Should I delete forms we no longer use?
Deactivate them. Deleting complicates historical tickets and Explore reports that reference the form.
Better forms, fewer repeat submissions
Clear forms reduce confused resubmissions. For the ones that still arrive twice, Ticket Merger finds them.
Start free trial14-day free trial. No credit card required.