Introduction
Tell us what you were trying to do and what went wrong. A few sentences is enough, and we will ask follow-up questions if we need more.
Support ticket form: capture enough to triage on the first reply
A support ticket form collects what a support team needs to understand, reproduce and sort a problem: who is asking, what they were trying to do, what happened instead, and how much it affects their work. The key judgment is how much to ask in the first message, enough to act on without making people give up before they finish. Decide before you publish who reads each ticket and what the form's settings will do with it.
What people search
Support ticket form: 20 average monthly searches.Google Ads Keyword Planner · 2026-10-09 · United States
Words for the respondent
Set expectations before the first field
Confirmation
Thanks, we have your request. We will reply to the email address you entered.
What were you trying to do?
Describe the task, not the button. For example: 'I was exporting last month's orders to send to my accountant.'
Account or order number
A reference number is enough. Do not include a password or a full card number.
How urgent is it?
Choose the option that matches your day. This helps us sort the queue; it is not a guarantee of a reply time.
Field blueprint
The fields a reader needs to sort a ticket
| Field | Type | Required | Why you ask it |
|---|---|---|---|
Your name | Short text | Required | Lets the reply open with the right name and ties the request to a person, not only to an email address. |
Email address | Required | The address your team replies to. A typo here stops the reply from arriving at all. | |
Phone numberOnly add it if you would like a call. Optional | Phone | Optional | Gives a second route for a problem that needs a conversation, without making a call the default. |
Account or order numberFound on your invoice or confirmation email. Do not include a password. | Short text | Optional | Lets the team find your records without asking you to search for them. |
What type of problem is this?Something is brokenI cannot sign inBilling or account questionHow do I do something?Other | Dropdown | Required | Gives the first sort, so the reader knows whether this is a defect, an access problem or a how-to question. |
What were you trying to do?For example: send the monthly summary to my manager | Long text | Required | The goal behind the problem. A fix for the wrong task wastes a day, so name the job first. |
What happened instead? | Long text | Required | The gap between the expected and actual result. This is the sentence a support engineer tries to reproduce. |
Where did it happen?A screen name or the step you were on, such as Settings, then Team members. | Short text | Optional | Points the reader to the right part of the product and the matching help article. |
When did it start? | Date | Optional | Shows whether this is a recent change, which often has a clear cause, or a long-running problem. |
How often does it happen?Every timeOftenOnce or twiceNot sure | Single choice | Required | Separates a repeating defect from a one-off, which changes how quickly it needs a look. |
How many people are affected?Only meMy teamSeveral teamsNot sure | Single choice | Required | Scope changes the order of the queue more than how strongly the request is worded. |
How urgent is it?I cannot do my workI can work around it, but it slows me downIt is a question with no deadline | Single choice | Required | Your view of the impact. It is an input to the sort, not a commitment about when someone replies. |
What have you already tried?Restarting, signing out or trying another browser all count. | Long text | Optional | Helps the team skip asking for steps you have already taken, and shows what a fix must not repeat. |
At a glance
Length check before you publish
13Fields
8Required fields
6Estimated time (minutes)
Estimate based on question types; actual completion time varies.
Try it
Try the form the way a customer would
After a response arrives
What happens after someone sends a ticket
Know the delay before you promise a reply
A saved ticket waits for the scheduled job, which runs hourly in production, before the form's creator is notified. Write the confirmation around your team's real reply window, not around the form's timing.
Check the case settings if the form creates cases
When the form creates a Customer Care case, each ticket gets the priority, tags and assignees set in form settings. Those settings apply to every submission, so review them before you share the link.
Read the grid and export it for the weekly review
Tickets appear in a grid that you can export as CSV. Count the problem types each week, and move the repeats into your help content so fewer people send the same question through the form.
Mistakes to avoid
Mistakes that slow the first reply
Asking for screenshots through the form
The form cannot take screenshots. Ask for the exact error text and the steps, then say how to send an image through the channel your team already uses.
Making every field required
A required 'When did it start?' produces guesses. Require the answers the reader cannot sort without, and leave the rest optional.
Presenting urgency as a guarantee
An option such as 'critical' can read as a promise of a fast reply. Describe the impact on the customer, and keep your response commitments on your support page where they can be checked.
Setting the case priority once and forgetting it
Priority and assignees in form settings apply to every ticket. Revisit them when the team changes, or new tickets will land with someone who has moved on.
Frequently asked questions
What should a support ticket form ask for?
Ask for the person's name and an address to reply to, the account or order reference if one exists, and the task they were attempting. Then ask what happened, how often it happens and how many people it affects. Leave out passwords and full card numbers, and give people one optional final field for anything else.
Can customers attach screenshots to a support ticket form?
Attain OS does not accept file uploads on forms, so ask for the exact error text and the steps instead. Tell people how to send screenshots through your usual channel, and link to that channel from the confirmation message.
Is there a support ticket request form template?
The field list in this guide works as a starting template. Copy the questions you need, match the problem types to the work your team actually does, and remove any question that nobody reads in the weekly review.
Can I use the same form for bug reports?
A bug report and a support ticket overlap. Keep the 'what were you trying to do' and 'what happened instead' questions in either one. A bug report also needs exact steps and the browser or app version, because those details decide whether an engineer can reproduce the failure.
How long should a support ticket form be?
Keep it short enough to finish on a phone in a few minutes. The count and time estimate in this guide update from the field list, so check them after each change and drop any question your team does not use.
Browse by category
More requests in Customer Service & Support
Requests
Feature Request
Requests
Return Authorization (RMA)
Requests
Service Cancellation
Reports
Warranty Claim
Reports
Customer Complaint Form
Intake forms
General Contact Us
How to build it
Choose a category and a form type in the wizard. Answer three Atty Suggestions questions, then give the form a title. Atty builds the fields in the background. Edit the fields and ask Atty to refine them, then publish and share the /f/ link.
