IT departments
Use this as a starting point when you need the same essential information from each person. Review the questions against your process before sharing your copy. Review “Department” in particular and adapt it to the detail you need.
Vague IT requests waste everyone's time. This help desk ticket form collects issue type, priority level, affected device, and a detailed description upfront — so your IT team can triage immediately instead of playing 20 questions. Works for any team from 5 to 5,000.
Free for non-commercial projects, with unlimited forms and responses.
Last updated
Most IT teams receive support requests via Slack, email, phone, and walking up to someone's desk — each channel producing a different level of detail. A centralized help desk ticket form standardizes the intake process so every request includes the information needed to actually resolve it: what type of issue it is, how urgent it is, which device is affected, and a coherent description of what went wrong.
This template is designed around how IT teams actually triage. The issue type dropdown routes tickets to the right specialist immediately. The priority scale uses plain-language descriptions ('blocking work, no workaround' rather than a vague 'High') so employees self-classify accurately without IT training. The description field's placeholder text guides employees to include error messages and steps they've already tried — eliminating the back-and-forth that delays resolution.
For teams without a dedicated help desk platform, formformform provides everything you need: instant email notifications, a searchable submission history, and a form that can be linked from your company intranet, pinned in Slack, or embedded on your IT portal. For teams that do have a platform, this form works as a clean intake layer that funnels structured requests into your existing workflow.
Use your own copy to change labels, remove questions and add the details you need. Try the preview alongside this guide to see what respondents will be asked.
Review the starting questions and choices. You can change them in your own copy.
Jane Smith
jane@company.com
Marketing
ext. 1234 or (555) 123-4567
e.g., Cannot connect to VPN from home
Describe the problem in detail: what happened, what you were doing when it occurred, any error messages you saw, and steps you've already tried.
e.g., MacBook Pro 2023, Windows 11 PC, Salesforce
Suggested uses, and why this starting point can help. Adapt the questions to your own process.
Use this as a starting point when you need the same essential information from each person. Review the questions against your process before sharing your copy. Review “Department” in particular and adapt it to the detail you need.
Ask for the context needed to understand the request before replying. This reduces the back-and-forth needed to establish the basic facts. Review “Issue Type” in particular and adapt it to the detail you need.
Give participants a clear set of questions and keep the information together, making it easier to prepare, respond and follow up. Review “Priority” in particular and adapt it to the detail you need.
Turn initial interest into information you can review. Use the answers to prepare a relevant follow-up and decide whether the opportunity fits your work. Review “Ticket Subject” in particular and adapt it to the detail you need.
Replace scattered requests with a consistent starting point. The answers help you understand the work, identify gaps and prepare a follow-up. Review “Issue Description” in particular and adapt it to the detail you need.
Replace scattered requests with a consistent starting point. The answers help you understand the work, identify gaps and prepare a follow-up. Review “Affected Device or System” in particular and adapt it to the detail you need.
Turn initial interest into information you can review. Use the answers to prepare a relevant follow-up and decide whether the opportunity fits your work. Review “When Did the Issue Start?” in particular and adapt it to the detail you need.
Get a useful brief before the first conversation. Written context helps you assess fit, prepare questions and decide what to discuss next. Review “Department” in particular and adapt it to the detail you need.
Click 'Use this template' to open the IT help desk ticket form in formformform.
Update the intro paragraph with your IT team's actual response time commitments for each priority level.
Customize the Issue Type dropdown to include systems specific to your organization (e.g., add your ERP, CRM, or other business-critical tools).
Set your IT team's shared inbox or ticketing alias as the notification email.
Share the form link in your company Slack, pin it in your IT support channel, or embed it on your company intranet.
Consider creating separate forms for different office locations or teams if your IT setup is distributed.
add the form link to your company Slack sidebar, Teams tab, or intranet homepage. A form nobody can find doesn't get used.
the intro paragraph is a great place to communicate response time commitments by priority level. It reduces follow-up 'any updates?' messages.
'Critical' tickets should mean genuine outages, not 'I'd like this fixed today.' A brief explanation in your IT onboarding prevents priority inflation.
over time, your ticket history reveals which devices or systems generate the most issues, informing replacement and upgrade decisions.
the description placeholder reminds users to include error messages, but reinforce this in your IT onboarding. An exact error message cuts resolution time significantly.
recurring issue types signal systemic problems (a flaky network switch, a software license issue) that are worth fixing at the root rather than resolving ticket by ticket.
Yes, completely free. You can collect unlimited support tickets with no subscription required.
formformform stores all submissions in your dashboard and can send email notifications. You can use Zapier or similar automation tools to route new submissions into your existing ticketing platform automatically.
You can share a direct link — pin it in your company Slack, Teams, or intranet. You can also embed the form on an internal IT portal page using the iframe code.
Yes. formformform does have file upload — it is a section in the form editor, up to 2 MB per file, which is ample for a screenshot. This template does not arrive with the field placed, because the template generator cannot seed one, so add an Upload field in the editor after you clone it. A pasted link to a hosted image still works well alongside it: some people already have a screenshot in a shared drive and would rather send the URL than re-upload it.
Yes. The Issue Type dropdown is fully customizable — add, remove, or rename options to match the software and hardware your organization actually uses.
Yes. You can customize the post-submit message in formformform to show a confirmation with a ticket reference and expected response time immediately after submission.
Collect detailed bug reports with steps, severity, and environment info.
Document workplace incidents, near-misses, and hazards in a structured way.
Take repair and maintenance requests with category, priority, and access details.
Collect product warranty claims with all the details needed to assess and resolve issues.
Take service requests with location, urgency, and access details.
Streamline equipment requests with a structured IT asset request form.
Collect bug reports, suggestions, and content errors directly from site visitors.
Manage software access provisioning with a structured request and approval form.
Explore how formformform fits the forms you need to build.
Opens with product context and a link to this page.
Free for non-commercial projects, with unlimited forms and responses.
Use this template