Support Request Form Template

Triage result: Use this support form to create a ticket that can be routed and investigated from product area, practical impact, observed behavior, and reproduction steps without requesting credentials.

Collect the details needed to reproduce and route a support issue.

Download the field schema

Preview the support ticket

Area and impact drive triage. Summary, observed behavior, and steps give the investigator a usable starting point.

Requester and route

Your name Required
Area RequiredAccountBillingForm builderResponsesOther
Impact RequiredQuestionWork slowedBlockedService unavailable

Evidence for investigation

Short summary Required
What happened? Required
Steps to reproduce
Create support request

How the ticket moves to resolution

The queue receives a scannable case with impact, ownership clues, and a safe reply route instead of an unstructured complaint.

Acknowledge the case

Acknowledge with a case reference.

Route and investigate

Route impact and product area to the responsible queue.

Resolve and document

Record resolution and update reusable help when the issue repeats.

Ticket fields that reduce back-and-forth

Area and impact drive triage. Summary, observed behavior, and steps give the investigator a usable starting point.

  • Your nameIdentifies the requester for case communication.
  • Email addressProvides the reply channel for updates and resolution.
  • AreaRoutes the request to the product or account owner most likely to resolve it.
  • ImpactHelps triage the practical effect without requiring the user to assign technical severity.
  • Short summaryCreates a scannable case label for queues and notifications.
  • What happened?Captures expected and observed behavior in the user's own words.
  • Steps to reproduceProvides an optional sequence for repeating and diagnosing the issue.

The triage and ownership decision

This template creates a triage-ready support record with product area, impact, summary, observed behavior, and reproduction details. It gives the support team enough context to route and investigate without asking the user for credentials or secrets.

Connect each impact choice to a documented form response workflow so urgent requests are not merely labeled and left in the same queue.

Use this when a case needs investigation

Use this to create a triageable support record with impact, area, summary, and reproduction context.

Match choices to the actual support queue

  • Define impact choices in user language.
  • Warn against sharing passwords or secret keys.
  • Keep account lookup separate from the public message field.

A blocked user reaches the right team

Triaging a blocked form-builder user. A support team can route a form-builder issue by area and impact, read the short summary first, and then reproduce the reported behavior from the detailed steps. The acknowledgement supplies a case reference and a safe channel for follow-up.

Support request questions

Answers about the choices, limits, and handoff shown on this page.

What information should a support request collect?

Collect the affected area, practical impact, a short summary, observed behavior, reproduction steps, and a safe reply address.

Should support forms ask for account passwords?

No. Passwords and secret keys should never be requested through a support form. Use approved identity and account lookup controls instead.

Create a support ticket your queue can use

Replace product areas and impact choices, prohibit secrets, and test acknowledgement, routing, escalation, and closure.

Compare form workflows