Usertick
Beta program survey template

Find beta testers among your active users, with the areas they want to try

Two quick questions after a short welcome: which areas a user would like to try first and how much time they could give each month. Use it as it is, or add an open question and Usertick reads every written answer for you.

What this beta program survey tells you

A beta program survey invites users into your beta group and learns what they want to test before you pick them. This template opens with a short welcome and asks two questions in about half a minute: which areas they would like to try first, from reports to automation, and how much time they could give each month. Both answers help you match each beta to the right testers.

It is written for a popup in your web app shown to users who were active in the last two weeks, targeted from Starter with a trait such as the last active date passed through Usertick.identify(). The same survey goes out by email to a list of your most active users. After the answer, a redirect can take users to your beta sign-up page or welcome document.

Results shows the share of users interested in each area and the share for each amount of time, against the period before. Select an area to see how much time its volunteers can give, and add an open question if you want Usertick to read and sort what they write.

On your websiteIn an emailAs a linkAs a conversation
Questions
2
Time to answer
Under a minute
Written for
A popup in your web app for users active in the last two weeks
Plans
Every plan, the free plan included

See it on every channel

The same template on your website, behind a link, in an email and as a conversation.

On your website

Show it as a popup, a side button or inside the page, and choose the pages and the moment it opens: on page load, after a delay, on scroll or as someone is about to leave, on every plan. Event and behavior triggers work on 1 survey on Free and on every survey from Starter.

The 2 questions, one by one

What each question asks, why it is there, what it shows you and what to change.

Question 1 of 2 · Multiple choice · Optional

Which areas would you like to try first?

Why ask it
Asking which areas users want to try matches each beta to the people who care about it. A tester who chose reports has a reason to look closely at reports, and users can pick as many areas as they like.
What you learn
Bars with the share and count of each area, compared with the period before. Select an area to see the users who chose it and the time they can give.
Make it yours
List only the areas with a beta planned in the next few months, so no volunteer waits for something that isn't coming.
Question 2 of 2 · Multiple choice

How much time could you give each month?

Why ask it
Time decides the kind of beta a user fits: half an hour suits a quick survey, and a few hours suit interviews and a longer test.
What you learn
A donut with the share of each amount, so you know how much testing time your group can give before you plan the beta. Select A few hours to see which areas the users with the most time chose.
Make it yours
Invite users who can give a few hours to interviews, and send the rest a short survey such as the Beta feedback template after they try the feature.

What the answers show

Results turns each question into numbers you can follow week by week.

Which areas would you like to try first?

The share of each answer with its count. Select an answer to narrow the whole page to those people and read what else they said.

How much time could you give each month?

The share of each answer with its count. Select an answer to narrow the whole page to those people and read what else they said.

Use this template in four steps

From the template to the first answers.

  1. 1

    Open the template

    Sign up free and pick Beta program invite in the template gallery. It opens in a matching style, ready to change.

  2. 2

    Make the questions yours

    Reword any question, change the options, and add logic or more questions.

  3. 3

    Choose where it runs

    Show it on your website, send it by email, share its link and QR code, or switch it to a conversation.

  4. 4

    Publish and read the answers

    Answers arrive in Results and the inbox as people send them, each written one read and filed by Usertick.

Tips for this survey

Small choices that keep people answering and the answers useful.

  1. 01

    Ask users who are active

    Show it to users active in the last two weeks, from Starter, or send it to a list of your most active accounts. Testers who use the product every week notice what changed.

  2. 02

    Know who answered

    In your web app, call Usertick.identify() with the user's ID and email, so every answer arrives with someone you can invite. By email, each answer is already tied to the contact.

  3. 03

    Send them to the next step

    Set a redirect after submit to your beta sign-up page or welcome document, so users who answer go straight to the next step.

  4. 04

    Build a tester list

    On every plan, a workflow adds each answer to a Google Sheet with the areas and the time, ready for picking testers. A HubSpot step can also add each volunteer to a HubSpot list.

More product feedback templates and questions

Templates like this one, and single questions from the library to add to it.

ProductProduct feedbackGive users one place to share what they think of the product, sorted by area so it reaches the right team. Run it as an always-on feedback button inside your app.
ProductFeature requestCollect feature ideas together with the problem behind them and how people cope today. Link it from your help menu, your roadmap or your changelog.
ProductBeta feedbackGet structured feedback from early users on a feature before it launches to everyone. Send it after testers have used the beta for about a week.
ProductFeature adoption checkFind out whether users have found a new feature, what keeps the rest away and what would make it part of their routine. Show it in the app two weeks after the release.

Questions from the library

Browse the question library
  1. Which support plan are you on?Multiple choice · Support plans
  2. How many seats does your plan include?Number · Seats and permissions
  3. How many of your seats are actually in use?Multiple choice · Seats and permissions
  4. How easy is it to add or remove a person?Customer effort · Seats and permissions

Frequently asked questions

Active users of the area you are testing. Users active in the last two weeks know the product well enough to notice what changed.

The answer is the sign-up when you know who the user is, through Usertick.identify() or an email send. To send them to a form or a welcome page, set a redirect after submit, or add a Call to action question with the link.

Yes, from Starter. Target by traits you pass with Usertick.identify(), such as plan or role, together with the last active date.

Send the Beta feedback survey after about a week with the feature, by email or by link, to collect what worked and what was confusing, missing or broken.

Only the areas with a beta planned in the coming months. A longer list spreads volunteers across tests you won't run for a while, and they may lose interest before their turn comes.

Yes. Every template comes with every plan, the free plan included, and the free plan covers 150 responses a month across your surveys.

Yes. The template becomes your own survey, so reword any question, add or remove questions, and change the options and the logic. The gallery stays as it is.

Yes, from Starter. The template is written in US English. Add languages by hand or with AI translation, and each person sees the survey in their browser's language.

Listen better, act faster, and build what truly matters.

Start free, see what your customers mean, and get each answer to the person who can act on it.

  • 150 responses a month on Free
  • Every channel and AI analysis
  • No card needed