Freshdesk Ticket Forms & Templates Explained (Multiple Forms)

Ticket forms vs ticket templates: who they're for

The single most useful distinction to hold onto is direction. A ticket form faces outward, toward the person submitting a request through your customer portal or help widget. A ticket template faces inward, toward the agent creating or replying to a ticket inside Freshdesk. They solve different problems from opposite sides of the same ticket.

Forms are about intake quality. If everyone who contacts you sees the same "Report an issue" form, a refund request and a login bug arrive looking identical, and an agent has to chase the missing details. Multiple forms let you ask a billing question one set of fields and a bug report a different set — so the ticket lands complete.

Templates are about agent speed. When the same shape of ticket recurs — an onboarding request, a return, a known outage log — a template pre-fills the subject, description, and properties so an agent doesn't retype it. If you already lean on canned responses to speed up replies, templates are the equivalent for creating tickets.

Setting up multiple ticket forms

By default, every Freshdesk account has one form, "Report an issue." Multiple forms are a paid capability: per Freshworks' Understand and Use Ticket Forms documentation, creating additional forms is available from the Pro plan onward (Free and Growth are limited to the single default), and an account can hold up to 50 ticket forms.

To build one:

1. Go to Admin → Workflows → Ticket Forms and click New form.
2. Give the form a name and description, then click Create.
3. On the form builder, the left panel lists all ticket fields that have the "Can view" property enabled for customers. Drag and drop the fields you want into the form body — a billing form might pull in an "Order number" field; a bug form might pull in "Steps to reproduce."
4. Reorder and mark fields required as needed, then Save.

The fields available to a form are the customer-visible ones you've defined under your ticket-field settings, so if a field you want isn't in the left panel, check that its "Can view" (customer) property is switched on first.

Linking forms to your portal (and where the dropdown appears)

A form that isn't published does nothing. Once you've built one, click the Publish button in the form editor and select which portals and feedback widgets it should appear on. You can also manage the association from the portal side: go to Admin → Channels → Portals, click Edit on the portal, open the Manage sections tab, and add forms from the Add ticket form dropdown.

Here's the behavior that trips people up: when you attach more than one form to a portal, Freshworks' docs state the forms surface as the first dropdown on the ticket submission page. So a customer clicking "Contact support" first picks which kind of request they're raising, and only then sees the matching fields. Name your forms as the customer would think of them ("Report a bug," "Ask a billing question") rather than in internal jargon, because that dropdown label is the first decision you're asking them to make. Widgets work the same way: under Admin → Channels → Widgets, choose "Show form with ticket fields" and pick which forms to expose.

Setting up ticket templates for repetitive requests

Templates live in a different corner of Admin. Per Freshworks' Creating and using ticket templates documentation, go to Admin → Agent Productivity → Ticket Templates and click New Template. Like multiple forms, templates are a Pro-and-Enterprise capability.

Inside a template you can pre-fill:

• Subject and description — including inserting an existing canned response via the star icon in the description box, so the wording you've already refined for replies can seed a new ticket.
• Ticket properties — default and custom fields (with the exception of requester and source), tags, and document attachments.
• Visibility — scope the template to all agents or only agents in particular groups, so a returns template doesn't clutter the list for your engineering team.

One behavior worth flagging: template values override any field data already on the ticket when applied. That's usually what you want, but it means a half-filled ticket will get overwritten, so apply the template first and fill in specifics second.

To use one, an agent clicks New Ticket (or New Email for outbound) and picks the template from the list on the right; the fields populate instantly. For multi-step workflows like employee onboarding or a returns process, you can go further with parent and child templates — a parent ticket that automatically spawns pre-defined child tickets, each already assigned to the right group.

Which one do you actually need?

Most teams need both, but for a given problem one is the right tool. Use this to decide.

The honest limits — and where an AI layer picks up

Both features are well-built and worth using. But be clear about what they are: structured data entry. A ticket form makes a customer tell you which category their problem falls in and type the relevant details — it doesn't read the free-text description and figure the category out for itself, so a customer who picks the wrong form (or ignores the dropdown) still lands in the wrong place. And forms only work on channels that render them; a request arriving by plain email bypasses the whole form experience and comes in as a generic ticket.

Templates have a matching ceiling. They pre-fill static content — the same subject, the same boilerplate description, every time. They can't pull the customer's actual order status into the reply, can't tailor the wording to this customer's situation, and can't decide which template a given ticket needs. An agent still reads the ticket, picks the template, and edits it into a real answer. The template saved the typing, not the thinking.

This is the seam where an AI agent layer fits, and it's worth weighing the build-versus-buy tradeoff before adding one. The broader category of AI agents for customer service exists to do the reasoning a form or template can't: reading the free-text description, inferring intent, and producing a tailored reply. Macha is one such layer — it runs on top of the Freshdesk you already use as a native connector, and it does not replace your help desk, your forms, or your templates. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your forms create: triaging by intent (so a mis-selected form gets routed correctly), and drafting grounded replies that go beyond static boilerplate by looking up live order or account status through a custom tool that turns a REST API into something the agent can call. If you want the fuller picture, we cover the workflow in how to automate Freshdesk with AI. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — the pricing page has the breakdown.)

The clean division of labour: let Freshdesk forms and templates handle structure — capturing the request cleanly and saving agents keystrokes — and layer an agent on top for the reasoning — turning that structured ticket into an accurate, personalized answer.

FAQ

How many ticket forms can I create in Freshdesk? Up to 50 ticket forms per account. However, creating more than the single default "Report an issue" form requires the Pro plan or above — Free and Growth accounts are limited to that one default form.

Where do I create multiple ticket forms? Go to Admin → Workflows → Ticket Forms and click New form. You build the form by dragging customer-visible ticket fields from the left panel into the form body, then publish it to your portals and widgets.

How do multiple forms appear to customers on the portal? When more than one form is attached to a portal, they show up as the first dropdown on the ticket submission page — the customer picks which kind of request they're raising, then sees the fields for that form.

What's the difference between a ticket form and a ticket template? A ticket form is customer-facing: it defines what someone fills in to submit a request on your portal. A ticket template is agent-facing: it pre-fills a new ticket's subject, description, and properties so agents don't retype recurring requests. Templates are set up under Admin → Agent Productivity → Ticket Templates.

Can I add AI without replacing Freshdesk's forms and templates? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing forms and templates — it doesn't replace them. It reads the tickets your forms capture, triages them by intent, and drafts grounded replies, while Freshdesk stays the system of record.

Ready to turn a well-structured ticket into an actual answer? Start a free trial of Macha and connect it to your Freshdesk in minutes.