A ready-to-use conversational form
Get bug reports your engineers can reproduce: steps, expected and actual results, and the right details for browser, mobile app or API problems.
Free to customize. No code needed.
What's inside
What a respondent is asked, in order.
Sorry something's broken. Let's get the details down so we can fix it.
In one line, what went wrong?
What steps lead to it? Number them if you can.
What did you expect to happen?
What happened instead?
How often does it happen?
Did this use to work for you?
Where did it happen?
Which browser?
Anything red in the developer console?
Does it still happen in a private window?
Which phone or tablet?
Which OS version?
Which app version? It's usually at the bottom of Settings.
Which endpoint, and which method?
What status code came back?
The request ID from the response headers, if you have it
A screenshot or screen recording, if you have one
Where should we reply?
Last one: how badly is this affecting you?
Endings
Bug reported 馃悰
Flagged as blocking 馃毃
Where each answer leads. Every route here is editable once the form is yours.
Short text
Long text
Short text
Short text
Single select
Yes / No
Single select
Single select
Long text
Yes / No
Short text
Short text
Short text
Short text
Number
Short text
File upload
Single select
A little guidance
Make the most of your next ask.
Triage by the severity answer first, then by frequency: a bug that happens every time and blocks work is a different job from a one-off annoyance. Try the numbered steps yourself before assigning the report, and use the private window answer to rule out extensions early. Export to CSV once a month and group reports by summary to see which parts of the product break most.
A one-line summary, numbered steps to reproduce, what was expected, what actually happened, how often it happens, and details of the device or browser. A screenshot saves a lot of guesswork.
Ask one thing at a time and ask for steps in order. This form does both, and the AI follow-up asks for more detail when an answer like "it doesn't work" is too vague.
Yes. The environment question branches, so a browser user is asked about the console and a mobile user about the device and app version.
Responses are collected in your dashboard, where you can read each report and export them all to CSV for your tracker.
A few more possibilities
Welcome aboard! A few questions now will save us a lot of back and forth later.
Who will be our main point of contact?
Form 路 Customer success
Everything you need from a new client before kickoff, asked in the order a good project lead would.
Make it yoursForm 路 Customer success
For shops and service businesses: a complaint about a purchase, with the order and the fix the customer wants.
Make it yoursForm 路 Customer success
Questions from shoppers and customers, each arriving with the product or order it's about.
Make it yoursThere is a good answer on the other side
Free forever. No credit card. Unlimited submissions.
