A ready-to-use conversational survey

Software customer satisfaction survey template

Ask users how satisfied they are with your software, which parts work well, what's missing and whether bugs got in the way. Unhappy users say why first.

12 questionsAbout 4 min2 branchesRead the template guide
Use this template

Free to customize. No code needed.

The real thing. Go ahead, try it.

Use this template
A live preview of this template. Answer the first question to begin.

What's inside

Every question, and where it leads

  • Single select
  • Rating
  • Long text
  • Matrix
  • Ranking
  • Yes / No
  • File upload
  • NPS
  • Email

The conversation

What a respondent is asked, in order.

Help us make the software better for you. About three minutes.

1

How long have you been using our software?

Single selectrequired
2

How often do you use it?

Single selectrequired
3

Overall, how satisfied are you with the software?

Ratingrequiredsplits the flow
4

Sorry it's not working for you. What's the main problem?

Long textrequiredsometimes asked
5

How would you rate each of these?

Matrixrequired
6

What matters most to you? Put the most important first.

Rankingrequired
7

Is there something you expected it to do that it doesn't?

Long textoptional
8

Have you run into a bug or error in the last month?

Yes / Norequiredsplits the flow
9

What happened, and where in the app were you?

Long textrequiredsometimes asked
10

Got a screenshot? Drop it here.

File uploadoptionalsometimes asked
11

How likely are you to recommend the software to a colleague?

NPSrequired
12

Your email, if you're happy for us to follow up

Emailoptional

Ends with

Thank you 馃檹

The flow

Where each answer leads. Every route here is editable once the form is yours.

A labelled route is taken only by answers matching the label

A little guidance

Make the most of your next ask.

Questions to consider for your software customer satisfaction survey

  • Do you want answers from every user, or from admins and power users only?
  • Which parts of the product should the grid rate separately?
  • Who picks up bug reports that arrive through the survey, and how?
  • Should you ask this in the app, by email, or both?

How to use the responses

Pass bug reports with screenshots to whoever handles support the same day, and reply to anyone who left an email. Split the satisfaction score by how long people have used the software: low scores from new users usually point to onboarding, while low scores from long-time users point to missing features or reliability. Compare the ranking with the grid, because a low rating on the thing users value most is the gap to fix first.

How to customize and share this template

  1. 1Replace "our software" with your product's name, and edit the grid rows to match its main areas.
  2. 2Add the user's plan or account ID as a hidden field so you can compare answers by customer type.
  3. 3Send it to active users after they have used the product for a few weeks, and repeat it every quarter with the same questions.

Frequently asked questions

What questions should a software satisfaction survey include?

An overall satisfaction score, ratings for ease of use, reliability, features, docs and support, a question about what's missing and a recommendation score. Asking about recent bugs is useful too.

What is the difference between CSAT and NPS for software?

CSAT asks how satisfied someone is right now. NPS asks whether they would recommend the product, which reflects loyalty over time. This template asks both.

How often should I survey software users?

Quarterly works for most products. Keep the questions the same each time so you can see whether satisfaction is moving.

Can users attach screenshots of bugs?

Yes. Users who say they hit a bug can upload up to three images with their description.

A few more possibilities

Keep the ideas coming.

Explore all surveys

There is a good answer on the other side

Make a formnobody minds filling in.

Start for free

Free forever. No credit card. Unlimited submissions.