Run a game or app beta with in-app feedback
For: studios and app teams running a TestFlight, Play testing or Steam playtest. You get: one place for testers, builds, surveys, and every bug report, with the build and device on each ticket.
The setup
| Step | Where | Why |
|---|---|---|
| 1. Add the build | Releases → New release | One record of the version and build that testers play. |
| 2. Open a tester portal | Modules → Testbench | Testers sign up or are invited, accept consent and see only what you share. |
| 3. Start a round | Testbench → Rounds, preset Release Candidate | Instructions, the build link, a survey and a start and end date. Link the round to the release. |
| 4. Add a feedback button to the game | Settings → Support → In-app SDK | Players report from the pause or settings screen. A screenshot and log come along when they tick them. |
| 5. Route reports | Support intake lane + Workspace Settings → Automations | New reports land in one lane. Rules can set priority or move them on. |
How it runs day to day
- Testers play the build from the round's instructions.
- When something breaks, they tap Send feedback in the game. The ticket shows the stage, device, OS, app version and build, with the screenshot.
- Testers who prefer the web send Bug or Idea feedback in the Testbench round.
- Your team triages the intake lane. Create a child Bug from a report to track the fix, and link it to the next release.
- At the end of the round, read Survey results, then close the round.
Tips
- Use a Test SDK key while you wire up the button. Those reports arrive as
[Test]tickets. - In-game reports are one way. Thank players in the game, not by email.
- Use the ticket Release field and the board's release filter to see what is fixed in each build.
Related
Updated 2026-11-10. Owned by product.

