A support request form covers the reporter’s contact details, urgency, supporting evidence, what happened, when it started, and what systems are affected.
A system breaks, access looks wrong, or an alert lands and nobody wants the first response to make things worse. The support request form gives the report a fixed path, so the person on the other end sees urgency, context, and evidence in one place instead of chasing details across messages. The page uses deep teal and magenta with Raleway headings over Inter body text, so the intake reads steady even when the situation isn’t.
The opening block explains what the request is for, then How we work sets the expectation for urgent cases, including a call to start containment. The questions collect the basics that usually decide the first move: who’s reporting, how to reach them, how urgent the issue feels, and any screenshot, photo, or error report that helps preserve what was seen. From there the form asks for the narrative, when it first showed up, and which systems, accounts, or users are affected, so support can start triage without guessing... and without turning the back-and-forth into the whole job.
- Support Request Form The intro text explains what the request covers and what happens after someone submits it.
- How we work The process note spells out what counts as urgent and who calls to start containment.
- Urgency question The choice field records whether the issue stops work, gets in the way, or is just a heads-up.
- Evidence upload The file field holds a screenshot, photo, or error report when someone can attach one.
- What happened The narrative, timing, and affected systems questions capture what occurred, when it started, and what’s impacted.
Once the form is in your workspace, you keep the wording or change it to match your support or incident response process, then share the link and collect responses in one place. Each submission arrives with the required fields filled in, plus the optional file upload when somebody has evidence to attach, so the first review starts with the same set of answers every time.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What to include in a support request form
| Part | What it covers |
|---|
Support Request Form | The opening written block frames what the request is for and what support does with the details that come in. |
Your name | A required full name field identifies who’s reporting the issue. |
Email address | A required email field gives a dependable reply path for follow-ups. |
How urgent is this issue? | A required choice records urgency as “It stops me working”, “It gets in the way”, or “Just letting you know”. |
Attach a screenshot, photo, or error report | An optional file upload captures evidence without forcing it when someone can’t provide it yet. |
How we work | The second written block explains the urgent-case handoff to an incident response lead for a containment call. |
Describe what happened and what you expected | A required long-answer field captures the sequence of events and the expected behavior in the reporter’s words. |
When did you first notice this? | A required date field anchors the timeline for investigation and triage. |
Which systems, accounts or users are affected? | A required text field records the scope, like specific systems, accounts, or users. |
Best phone number to reach you now | A required phone field gives a fast callback option when email isn’t enough. |
Who it is for
IT support teams, managed service providers, and security operations groups that need a consistent intake for incidents, monitoring alerts, and access problems.
The form in full
Support Request Form
Tell us what is wrong with systems you already use with us. We check your details and call if we need to contain or investigate further.
- Your name (required)
- Email address (required)
- How urgent is this issue? (required)
- It stops me working
- It gets in the way
- Just letting you know
- Attach a screenshot, photo, or error report
How we work
If urgent, our Incident response lead, Salim Al Harthi, will call to start containment.
- Describe what happened and what you expected (required)
- When did you first notice this? (required)
- Which systems, accounts or users are affected? (required)
- Best phone number to reach you now (required)
