Skip to main content

Ticket Forms - Structure different use cases

Updated

Ticket forms are the foundation for organising and structuring the many different enquiries received every day. By creating specific and tailored templates for different use cases, you ensure that each enquiry receives the relevant fields, the correct instructions and is sent in the right direction from the outset. The feature can transform a generic inbox into a specialised and efficient workflow.

What are ticket forms?

Ticket forms are dynamic templates that define which fields and settings are presented to a customer or an agent when a ticket is created. Each form is a unique configuration that can contain:

  • Selected custom ticket fields: Only fields that are relevant to the particular type of enquiry are included.
  • Specific instructions and help text: The user is guided to provide the necessary information.
  • Predefined routing rules: The ticket is ensured to be placed correctly from the outset.
  • Associated SLA policies: Different service targets can be applied depending on the nature of the enquiry.
  • Unique automations and triggers: Specific workflows can be activated based on the form selection.

Why are ticket forms crucial for an effective Zendesk solution?

Implementing a strategy with multiple ticket forms is an investment in efficiency, data quality and customer satisfaction.

1. Tailored data collection of high quality

When customers are only presented with relevant fields, the likelihood of receiving correct and complete data increases. This reduces the time agents spend following up on missing information and ensures that reporting and analysis are built on a solid data foundation.

  • Support form: Product, version, detailed error description, steps to reproduce.
  • Order form: Order number, delivery address, requested delivery date.
  • Complaint form: Reference to previous communication, expected compensation or resolution.
  • IT service form: System name, username, specific error message.
  • HR request form: Employee ID, department, type of request (e.g. holiday, equipment).

2. Intelligent and automated routing

The form selection functions as the first signal in the automation engine. Based on the selected form, a series of actions can be performed automatically and consistently:

  • Assign to the correct group: A technical support ticket is sent directly to "IT support", while an invoice query is sent to "Finance".
  • Set the right priority: A "Downtime" form can automatically receive high priority, while a general enquiry receives normal priority.
  • Apply specific SLA policies: Faster response times can be guaranteed for VIP customers via a dedicated form.
  • Activate relevant macros or automations: An "Onboarding" form can automatically send a welcome series of emails.

3. An improved, reduced-friction experience for the customer

A long and irrelevant form can be experienced as a barrier. A short and focused form that only asks the necessary questions makes the process faster, more intuitive and less frustrating, and signals respect for the customer's time and needs.

4. Increased efficiency and clarity for agents

Agents receive tickets that are already categorised and enriched with the necessary information. This reduces mental load and "click-to-find" time, so that the focus can be on solving the customer's problem.

How to build the perfect ticket form in Zendesk

Creating a form is straightforward, but a good form requires consideration.

  1. Navigate to configuration: Go to Admin Center → Objects and rules → Tickets → Forms.
  2. Create a new form: Click Add form to start with a blank form.
  3. Give the form a strategic name: The name should be descriptive and easy to identify in both lists and triggers, e.g. "Support - Technical Error" or "Sales - Price Enquiry".
  4. Select and arrange fields: This is the core task.
    • Drag relevant fields (both standard and custom) into the form.
    • Consider the order: start with the most basic (Subject, Description) and move towards the more specific.
    • Mark only critical fields as Required. Too many required fields can increase drop-off.
  5. Write clear instructions: Use the "End-user description" field to explain the purpose of the form and give examples of good answers. Clear instructions can reduce the need for follow-up questions.
  6. Save and activate: Save the form, and make sure that it is active and available for the relevant brands or help centres.

In-depth best practices for ticket forms

To maximise the value of ticket forms, a number of best practices can be applied.

Strategic naming and organisation

A naming convention is crucial, especially in complex environments.

  • Use a hierarchical structure: [Department] - [Purpose] - [Detail]
    • ✅ "IT - Software - Bug report"
    • ✅ "Sales - Enterprise - Demo request"
    • ❌ "Form 1"
    • ❌ "Standard form"

Intelligent use of fields

Fields are the primary tool for data collection.

  • Keep it relevant: Only include fields that directly contribute to resolving the enquiry.
  • Use dropdowns and checkboxes: Use fields with predefined options where possible. This ensures consistent data and makes reporting simpler.
  • Utilise conditional fields: Fields can be shown or hidden dynamically based on an earlier choice.
    • Example: If a customer selects "Type of problem" → "Technical", the fields "Product" and "Version" are shown. If "Invoice query" is selected, the field "Order number" is shown instead.

Designing instructions and help text

The text should function as support and not as a barrier.

  • Be short and precise: Use clear language and avoid jargon.
  • Give concrete examples: Instead of "Describe the error", it could say: "Describe the error. Example: 'When I click 'Save', I get a red error message with the text Error 503.'"
  • Set expectations: The customer can be informed of the expected response time for this type of enquiry.

Test, iterate and optimise

A ticket form is not static. Performance should be evaluated on an ongoing basis.

  • Test from the customer's perspective: Create test tickets to ensure that the flow is logical and that routing works as expected.
  • Analyse data: Review reports to identify fields that are often left empty, or tickets that are often re-categorised. This can indicate a need for optimisation.

Concrete examples across departments

Example 1: Technical support

  • Name: "IT - Software - Bug report"
  • Fields:
    • Subject (Required)
    • Description (Required)
    • Product (Dropdown: CRM, ERP, Webshop) (Required)
    • Version (Text field)
    • Error message (Text field)
    • Attachment (log files, screenshots)
  • Instructions: "Please describe your problem in as much detail as possible. Include steps for how the error can be reproduced, and attach any screenshots or log files."
  • Routing:
    • Group: Technical Support
    • Priority: Medium
    • SLA: Standard Support SLA

Example 2: Sales and enquiries

  • Name: "Sales - Enterprise - Demo request"
  • Fields:
    • Subject (Required)
    • Company name (Required)
    • Industry (Dropdown)
    • Number of employees (Dropdown)
    • Requested demo date and time
    • Specific interests (Checkboxes: Invoicing, Reporting, Integration)
  • Instructions: "Thank you for your interest. Please fill in the fields so that the most relevant demo can be prepared for your organisation."
  • Routing:
    • Group: Sales - Enterprise
    • Priority: High
    • Tag: demo-anmodning

The synergistic power: integration with the Zendesk ecosystem

Ticket forms are not an isolated feature; they function as the engine for several parts of a Zendesk setup.

  • Triggers: Triggers can react to Ticket form as a condition.
    • Example: Trigger: Ticket created | Condition: Ticket Form is "Downtime" | Action: Set Priority to High, Assign to the group "Incident Response", Send notification to Slack channel #incidents.
  • Automations: Automated follow-up can be created based on the form type.
    • Example: Automation: Ticket has been open for 24 hours | Condition: Ticket Form is "Invoice query" | Action: Add internal note: "Follow up on this invoice case".
  • SLA Policies: Specific service targets can be linked to specific forms.
    • Example: An SLA policy for the "VIP Support" form can have a First Reply Time target of 15 minutes, while "General enquiry" has 8 hours.
  • Views: Agents can use views filtered on Ticket form to see a specialised queue with relevant tickets.
  • Reporting: Dashboards can be built to analyse performance, volumes and resolution times per form and provide insight into the business.

Common challenges and their solutions (troubleshooting)

Even with good planning, challenges can arise.

  • Problem: Customers cannot see the right form in the Help Center.
    • Solution: Check the form's Permissions. Is it set to "Everyone" or a specific user role/organisation? Is the form Active and assigned to the correct Brand?
  • Problem: A field that has been added does not appear in the form.
    • Solution: Verify that the field has been dragged into the form editor. Also check whether the field is hidden by a conditional field rule that is not met.
  • Problem: A trigger that should assign a ticket based on the form does not work.
    • Solution: Open the trigger and double-check that the condition is Ticket form | Is | [The form's exact name]. A small typo can prevent the trigger from working. Triggers react to the form's ID, so renaming a form does not affect the trigger's function, but it is good practice to keep names synchronised.

Implementation and next steps

Once ticket forms have been defined and created, the work continues with establishing the ecosystem that supports them.

  1. Map and create triggers: Build triggers for routing, prioritisation and notifications for each form.
  2. Configure automations: Set up automations for follow-up and escalation.
  3. Implement SLA policies: Define and apply relevant service targets for each type of enquiry.
  4. Build agent views: Create specialised views so that agents can work efficiently within their areas.
  5. Test thoroughly: Carry out end-to-end testing for each form – from creation to resolution.
  6. Communicate internally: Ensure that agents understand how the new forms work and why they have been implemented.

Conclusion

Ticket forms are more than templates; they are a strategic tool at the core of a mature and effective customer service organisation. With a strategic design and a targeted implementation, support can be developed from a reactive function into a proactive, data-driven and specialised workflow. This provides better data, fewer manual tasks, an improved customer experience and strengthened agent efficiency. The investment in structuring enquiries with ticket forms can thus deliver returns in the form of efficiency, quality and satisfaction.

Powered by Zendesk