Browse all guides

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

StepWhereWhy
1. Add the buildReleases → New releaseOne record of the version and build that testers play.
2. Open a tester portalModules → TestbenchTesters sign up or are invited, accept consent and see only what you share.
3. Start a roundTestbench → Rounds, preset Release CandidateInstructions, the build link, a survey and a start and end date. Link the round to the release.
4. Add a feedback button to the gameSettings → Support → In-app SDKPlayers report from the pause or settings screen. A screenshot and log come along when they tick them.
5. Route reportsSupport intake lane + Workspace Settings → AutomationsNew reports land in one lane. Rules can set priority or move them on.

How it runs day to day

  1. Testers play the build from the round's instructions.
  2. When something breaks, they tap Send feedback in the game. The ticket shows the stage, device, OS, app version and build, with the screenshot.
  3. Testers who prefer the web send Bug or Idea feedback in the Testbench round.
  4. Your team triages the intake lane. Create a child Bug from a report to track the fix, and link it to the next release.
  5. 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.

Updated 2026-11-10. Owned by product.