Support Request / Bug Report
Contact & support
Collect reproducible bug reports with severity, steps, and optional screenshots.
A useful bug report is a story: who hit it, how bad it is, and how to see it again. This template is the intake form help desks actually want — not a blank “describe your issue” box.
Who it is for
SaaS teams, IT desks, and product ops people who triage inbound defects before they become Slack archaeology.
When to use it
Publish it on a /support page when you need reproducible steps and a severity signal. Keep Contact Us for vague questions and Feature Request for ideas that are not broken today.
What this form collects
Reporter identity, severity, a short summary, steps to reproduce, expected versus actual results, and an optional screenshot or log.
- Public bug reporter next to release notes
- Internal IT ticket form for staff
- Agency intake when a client says “it’s broken”
Preview mode: This is a live read-only render of the template. Sign up to clone it into your account, or customize it with the guest AI builder first.
Support Request / Bug Report
Frequently asked questions
Why ask for expected and actual results separately?
A single paragraph usually mixes those together. Splitting them makes the first responder’s job a scan, not a translation.
What file types can reporters attach?
The shipped file field accepts images, PDFs, and text logs. You can tighten accept types in the builder after you clone the template.
Does the preview submit a real ticket?
No. Guest preview is read-only. Use this template to create a form in your account, then submissions land in GRTforms like any other form.
Related templates
Nearby GRTforms templates for the same job or the next step after this one.
Contact Us
Simple contact form for general inquiries with name, email, and message fields.
Feature Request
Collect product ideas with the job to be done, urgency, and who would use the feature.
Security Disclosure
Give researchers a place to report a vulnerability with severity, product area, and a non-public write-up.
Change Request
Intake a planned change with systems touched, risk, and a needed-by date — not a bug ticket.
Partnership Inquiry
Qualify inbound partnership ideas with company fit, audience overlap, and a concrete next step.