title: Support Request Form Template - Help Desk & Service Tickets
description: Pre-built support request form with urgency levels, request categorization, and issue tracking. Perfect for IT and customer support teams.
keywords: support request form, help desk form, service ticket form, IT support form, technical support form
sidebar_position: 15
The Support / Service Request template is designed for IT teams, help desks, and customer support departments that need to triage and route support tickets efficiently. This template captures request details, urgency levels, and affected systems to help support teams prioritize and resolve issues faster.
What's included
This template includes seven pre-configured fields:
Your Name (Short Text)
Requester's full name for ticket tracking and follow-up communication. Essential for internal support teams to identify who needs help.
Email Address (Short Text)
Contact method for status updates, resolution notifications, and follow-up questions. Links the ticket to the requester's conversation history.
Request Type (Dropdown)
Four categories: Technical Support, Account Issue, Billing Question, and General Inquiry. Routes tickets to the appropriate support team or specialist.
Urgency Level (Radio Buttons)
Four-tier priority system: Critical (system down), High (major issue), Normal (standard request), and Low (question or feedback). Radio buttons make priority selection fast and visually clear.
Affected Area or Product (Short Text)
Free-text field to identify which system, feature, or product the issue affects. Examples: "Mobile App", "API", "Dashboard", "Checkout Flow". Helps support teams understand scope.
Issue Description (Long Text)
Detailed explanation of the problem, error messages, steps to reproduce, or request details. The most important field for support teams to understand and resolve the issue.
Confirmation (Checkboxes)
Checkbox confirming information accuracy. Reduces incomplete or rushed submissions that waste support time. Can be customized to include SLA acknowledgment.
Who should use this template
This template is ideal for:
IT support teams in companies providing internal technical support to employees. Urgency levels help prioritize critical infrastructure issues over routine requests.
SaaS customer support teams handling product questions, bug reports, and feature requests. Request type categorization routes tickets to product vs technical vs billing specialists.
Managed service providers (MSPs) supporting multiple clients with varying service levels. Urgency field ensures SLA compliance by flagging time-sensitive issues.
How to use this template
- Navigate to your form in the dashboard
- Click the Fields tab
- Click Use Template in the empty state
- Select Support / Service Request from the template grid
- Customize urgency levels and request types to match your support structure
- Click Save to apply the template to your form
Share the form URL with customers or employees, embed it in your support portal, or link from your product's help menu. All tickets flow into your SupportRetriever inbox organized by priority.
Customizing the template
Adapt the template to your support workflow:
Align request types with your team structure
Edit categories to match how your support team is organized. Examples: "Bug Report", "Feature Request", "How-To Question", "Account Access", "Performance Issue".
Adjust urgency definitions
Customize priority levels to match your SLA tiers. For example: "P1 - Production Down", "P2 - Critical Feature Broken", "P3 - Standard Issue", "P4 - Enhancement Request".
Add customer/account ID
Include a Short Text field: "Customer ID" or "Account Number" for faster ticket lookup and context. Especially useful for B2B SaaS or companies with enterprise customers.
Include affected users count
Add "Number of Users Affected" (Dropdown: Just me, 2-5 users, 6-20 users, 21+ users) to help prioritize issues by impact.
Add environment details
For software support, include dropdowns for "Browser" (Chrome, Firefox, Safari, Edge), "Operating System" (Windows, Mac, Linux, Mobile), or "App Version".
Include attachment instructions
Since file uploads aren't in custom fields, add guidance in Issue Description placeholder: "Include screenshot URLs or error logs in your description."
Best practices
Define urgency criteria clearly: In your form description or confirmation email, explain what qualifies as "Critical" vs "High". Without clear definitions, customers mark everything urgent.
Respond to Critical within SLA: If someone marks an issue Critical, acknowledge within your SLA (typically 1-4 hours). Even if you can't resolve immediately, acknowledgment shows you're on it.
Use affected area for auto-routing: Set up filters or tags in SupportRetriever to automatically tag tickets based on affected area. "API" mentions route to backend team, "Dashboard" to frontend, etc.
Track urgency accuracy: After resolving tickets, note if the customer-selected urgency matched actual priority. If customers consistently over-escalate, you need clearer urgency guidelines.
Encourage detail in descriptions: The more context in Issue Description, the faster resolution. In placeholder text or confirmation email, ask for: error messages, steps to reproduce, screenshots, what they expected vs what happened.
Close the loop: After resolving an issue, use the same conversation thread to confirm resolution and ask if the customer needs anything else. This prevents reopened tickets.