Discover · Feedback survey

A playtest survey that scores itself

Four one-tap rating scales tell you how much players enjoyed the build. Two open questions tell you why. Subo turns the ratings into a single satisfaction score, so you can compare this playtest to the last one at a glance.

Use this template Build it with the API
Discover GamersBusinesses Rating scalesSatisfaction scoreOpen-ended follow-upsOne-tap emoji answers
What it showcases

Features most survey bots don't have

⭐

One-tap rating scales

Fun, engagement, polish and would-recommend, each answered with a single tap on a face emoji. No typing, so more players actually finish.

📊

A score you can compare

Each scale is weighted one to five, so the ratings roll up into one satisfaction score per session. Watch it move build over build instead of eyeballing raw answers.

💬

The why, in their words

Two open questions capture what players loved and what they'd change, so the number always comes with the story behind it.

🎮

Send it while it's fresh

Fire it the moment a playtest, beta weekend, or content drop ends, when impressions are sharpest, right inside Discord or on the web.

Worked example This template comes with a an indie studio's beta weekend example so you can see exactly how it plays. Edit the questions and content to make it your own.

A 👍/👎 in a channel tells you nothing you can act on. This survey turns “how was the playtest?” into a number you can track and a set of reasons you can fix, in the time it takes a player to tap four faces.

Run it right after a playtest, beta weekend, or content drop. Players rate fun, engagement, polish, and how likely they’d recommend it, then tell you in their own words what landed and what didn’t. Subo scores every session so you can see whether this build actually beat the last one.

A number and a story, not just raw answers

Most feedback forms leave you with a pile of answers and no summary. Here each rating is weighted one to five, so every response produces a single satisfaction score. Compare that score across playtests to see the trend, then drop into the open answers when you need the why behind the move.

The example runs four ratings and two open questions on a studio’s beta weekend. Rename the dimensions, adjust the scales, and it fits any build you’re testing.

Variants

  • Product or beta CSAT: rename the scales to setup, performance, value, and recommend for a SaaS beta check-in.
  • Event feedback: repoint it at a tournament, workshop, or community event and ask how it went.
  • Classic NPS: add a single zero-to-ten recommend question and branch detractors into a “what went wrong?” follow-up.
  • Quick pulse: keep only two ratings and one open question for a 20-second post-session pulse.
How to run it

Live in a few minutes

  1. 1

    Clone and name your build

    Swap in your game or build name. Keep the four rating questions or adjust them to what you're testing this round.

  2. 2

    Tune the scales

    Each rating option is weighted one to five. Leave the defaults for a standard satisfaction score, or reweight if a dimension matters more.

  3. 3

    Publish and collect

    Players rate in four taps and answer two quick open questions. Every session gets a satisfaction score automatically.

  4. 4

    Read the score and the why

    Compare satisfaction across playtests in the results, then read the open answers to know exactly what to fix before launch.

FAQ

Common questions

Is this an NPS survey?

It's NPS-style. Instead of a single zero-to-ten score it uses four short rating scales that roll up into one satisfaction number, plus open follow-ups. Swap in a classic 'how likely are you to recommend' question if you specifically want NPS.

Do players have to type?

Only if they want to. The four ratings are one-tap emoji answers, and the two open questions are optional depth. Most players finish in under a minute.

Can I use it outside of games?

Yes. It works as a product or beta CSAT survey, an event or workshop feedback form, or a post-purchase check-in. Rename the four dimensions to fit what you're measuring.

Where does the satisfaction score come from?

Each rating option carries a weight from one to five. Subo sums the weighted answers per response, so a comparable score falls out with no spreadsheet or manual tallying.

More templates

Keep exploring

Measure how your community actually feels

Take the pulse of your community. A belonging and value health score you can trend, plus what members want more of and one thing to fix.

The exit interview, done right

Turn cancellations into your best feedback. Ask the real reason people leave, branch to a pricing or win-back follow-up, and learn exactly what to fix.

A roadmap vote that asks why, not just what

Let your community vote on what you build next, then ask why. The follow-up adapts to the vote, so you learn not just what people want but the reason behind it.

Use this template

Clone it into your community, swap in your content, and share it. No building from scratch.

Use this template Browse survey recipes