Ask the right questions.
A request form that asks for the product area, the context, and the steps before a ticket ever reaches your team — so the first reply is an answer, not a follow-up question. Configured in the same workspace that handles the replies.
What customers get: the request type they picked, then one short page of targeted questions.
How it works
One form, configured by the people who answer it.
Every request starts with a type — bug report, help, feature request, or feedback. Each type carries its own set of follow-up questions, grouped into pages, that you arrange in the same workspace that handles the replies.
Customers see one page at a time: they pick what they need, answer a few targeted questions, and leave their name and email. Every answer, and any file they attach, lands on the request as structured context rather than a paragraph to decode.
There is no form to embed and no engineering ticket to file. The request form lives on your own domain next to your help center, and publishing a new version of the questions never breaks the link or changes an existing request.
What it does
Everything the reply needs, captured up front.
The back-and-forth on a support request is almost always the same: which part of the product, what you expected, what actually happened. Ask once, on the form.
Intake
Four request types, ready to use
Bug report, Help, Feature request, and Feedback — each with its own questions.
One question page at a time
Group questions into pages so the form never reads as a wall of fields.
Routed from your help center
A Request for Help link brings readers here when an article is not enough.
Question types
The field that fits the answer
Short and long text, number, single and multi-select, date, and file upload.
Required where it matters
Mark each question required or optional. A subject line is always captured.
Reword and republish
Edit questions anytime. Live requests keep the version they came in on.
Context on arrival
Answers, not a wall of text
Each response is stored against its question, ready to read at a glance.
Files from the customer
Screenshots, recordings, logs, and PDFs attach straight to the request.
Summarised as it lands
Supa adds a short summary of the thread when the request is assigned.
Publishing
Draft in private
Build and preview a workflow without touching the live form.
Versions you can trust
Every published version is immutable, so request history never shifts under you.
No embed to maintain
The form is hosted on your domain. No script, no iframe, no redeploy.
Also included. Contact matching, idempotent submissions, and all four request types on every paid plan.
Who it's for
Why teams put a form in front of support
The shape of the problem is the same everywhere: a request with too little in it to act on. What differs is what that costs.
SaaS support teams
Every bug report starts with three follow-up questions
Which browser, which account, what you expected — the same clarifying reply, over and over, before anyone can start work. A typed form asks all of it up front, so the request arrives ready to action instead of ready to triage.
The first reply is the answer
Product and ops teams
Feedback and feature requests arrive as one-line emails
Without structure, every request is a sentence you have to interpret and chase. Request types and required questions turn free-form email into something you can read, sort, and route without a meeting.
Requests you can actually sort
Solo founders
You are the one reproducing every bug
When you are the whole support team, a vague report costs you the afternoon. Asking for steps, expected result, and a screenshot on the form buys back the time you would spend going back and forth.
No back-and-forth to reproduce
Frequently asked questions
How many request types can I have?
Four, and they are fixed: Bug report, Help, Feature request, and Feedback. Each has its own workflow of questions that you configure.
Can customers submit without an account?
Yes. The request form is public. Customers give their name and email, which is matched to an existing contact or used to create a new one.
What question types are supported?
Short and long text, number, single-select, multi-select, date, and file upload. Every request also captures a subject line.
What happens to old requests when I change a form?
Nothing. Each published version is immutable. Requests stay attached to the version they were submitted on, with their original questions and answers.
Do I need to embed anything on my site?
No. The form is hosted on your own domain alongside your help center. You link to it — there is no script or iframe to install.
Can people attach files to a request?
Yes. Add a file upload question and customers can attach screenshots, recordings, logs, or PDFs directly to the request.