This IT Support Request Form Template helps service desk and operations teams collect incident-ready information: what broke, for whom, since when, and what was already tried—so analysts spend less time on discovery and more time on fixes.
Pair it with your status page, on-call rosters, and major-incident comms. For catalog-style asks such as a new laptop or standard role access without an active failure, use your IT Service Request flow instead so fulfillment teams are not buried under outage traffic.
Incident evidence fields for faster diagnosis
Order fields from fastest triage signals to deeper technical detail:
- Requester and reachability: contact, location or time zone, preferred channel for follow-up if policy allows callbacks.
- Symptom category: device, network, identity, email, collaboration, line-of-business app, printing—pick lists aligned to your resolver groups.
- Scope: just me, my team, a site, or company-wide suspicion—helps spot duplicates during incidents.
- Timeline: first noticed, constant or intermittent, last successful use, any change window overlap.
- Impact: cannot work, degraded but workaround exists, minor annoyance—define each label beside the option.
- Environment: asset tag or hostname, OS version, browser if relevant, on VPN or not, wired versus Wi‑Fi for office issues.
- Evidence: exact error strings, correlation IDs, URL, steps to reproduce in numbered lines—not one paragraph stream of consciousness.
- Already tried: checklist tied to your top knowledge articles for that category.
- Security flag (branch): phishing, suspected account compromise, data leak worry—routes to SOC or IR per policy.
Routing branches for security and major incidents
- Application-specific paths ask for tenant region, workspace name, or integration ID fields your SaaS vendors need on first contact.
- Customer-facing roles can surface AV and headset questions; back-office roles skip them.
- Major incident mode: replace long forms with a minimal duplicate-aware intake that links users to the known incident record.
Use skip logic for those branches and make your questions required only on fields that materially change routing or safety response.
Support channels and ITSM connection points
- Website embedding on the intranet next to chat shortcuts so people find the official path first.
- E-mail notifications to resolver groups and confirmation to the requester with ticket ID and expected first-response window.
- Connect Responsly to Zapier to create or enrich incidents in your ITSM with structured fields instead of pasting unstructured email bodies.
- Slack survey response notification for small teams that want a lightweight ping when high-severity answers arrive during business hours.
- Show ticket number, link to portal status, and link to any active incident thread.
- If auto-resolution tips appear, label them clearly as self-help—not a closed ticket unless your policy allows it and users consent.
Support intake anti-patterns to eliminate
- Demanding screenshots for every category including password resets—adds friction without signal.
- Mixing project consultation requests into the incident form because the URL is shorter.
- Letting users pick assignee individuals instead of queues—creates coverage gaps when that person is out.
- No deduplication guidance during outages—every person filing separately overwhelms triage.
- Storing sensitive attachments without malware scanning or retention limits.
Practical setup resources for support teams
Use create survey, free text questions with examples in the prompt, question library for reusable incident templates, and multilingual surveys for global support desks.
Then read survey question types for clearer structured prompts, customer effort score (CES) to keep reporting effort proportionate to pain, and closed loop feedback so users see status changes instead of silent tickets.
