Beta Feedback

Feedback

IT & Operations · Marketing & Agencies

Collect a ship-or-wait call on a named build, plus where the product still felt unfinished.

betapreviewbuildqa

Beta notes in Slack vanish when the thread hits forty replies. This template asks which build they used, whether they would ship it, and where the product still felt unfinished.

Who it is for

Product and design teams running a closed preview who need a written call, not emoji on a Loom.

When to use it

Send it with the build email. Product Feedback is for generally available surfaces. Feature Request is net-new. Beta Access is the application to get in — this form is what they do after they are in. User Interview is the live conversation.

What this form collects

Build name, area, a readiness star rating, a ship/wait/cut radio, a required unfinished note, and an optional screenshot.

  • Closed-preview cohort after a week in the build
  • Design-partner readout before GA
  • Internal dogfood of an admin rewrite

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.

Beta Feedback

Collect a ship-or-wait call on a named build, plus where the product still felt unfinished.

Ready to use this template?

Frequently asked questions

Where should they file a crash?

Support Request. This form is a release judgment. Do not turn the unfinished box into a reproduction log — that is a different inbox.

Can I require a screen recording?

The optional file field accepts images and PDFs. Ask Customize with AI to widen accept types if you want a short clip, or keep text so nothing huge lands in the first inbox.

How is this different from Feature Satisfaction?

Feature Satisfaction assumes the thing already shipped. Beta Feedback assumes it might not. The ship-or-cut radio is the difference.

Nearby GRTforms templates for the same job or the next step after this one.

Browse all Feedback templates

Browse IT & Operations templates