How to increase survey response rates

Most of what decides a response rate happens before anyone sees the first question: who is asking, at what moment, through which channel, and whether answering looks worth the time. The questionnaire matters too, but it only gets its chance once someone has decided to start.

This article works through those decisions in order. It also makes a case that is easy to forget while you watch a counter climb: what you want is answers from the right mix of people, which is not always the same thing as the most answers.

Know which number you are moving

A response rate is completed responses divided by the number of people you invited. A completion rate is completed responses divided by the number who started. They fail for different reasons. A low response rate is usually about the invitation and the moment; a low completion rate is about the survey itself.

Keep your own count of invitations, because no survey tool can see the email someone received and ignored. What a tool can show is what happened after the click. Plumeform's results summary shows views (the link was opened), starts (someone answered something) and completed responses, which separates the problems neatly: few views means the invitation is not working, many views and few starts means the first screen is not, and many starts with few completions points at the questionnaire.

Ask at the right moment

People answer when the experience is fresh and the survey is obviously about it. A question about a support conversation belongs soon after the conversation, not in a quarterly batch. A question about an event belongs while people still remember the sessions.

Avoid moments when answering competes with something the person is trying to do: a checkout, a deadline week, the first minutes with a new product. A survey that interrupts a task gets closed; one that arrives after the task is done gets read. If you ask on your own site, embedded surveys can sit inline on a page, open from a button or wait behind a small launcher, so you can choose where the question appears.

Write an invitation people can say yes to

The invitation is the part of the survey most people see, and many decide from it alone. A good one answers four questions in a few lines:

1. 1Who is asking? A named person or team, not an anonymous no-reply address if you can avoid it.
2. 2Why? One sentence about what the answers will change.
3. 3How long will it take? Stated honestly, in minutes.
4. 4What happens to the answers? Who sees them, whether they are anonymous, and when people will hear about the results.

Then give one link. Leave out paragraphs about how much you value feedback; a specific invitation shows it better. Keep the subject line plain and descriptive, because people are deciding whether the message is worth opening, and a clever subject line makes that decision harder.

Put together, an invitation can be this short:

Every sentence in it does a job: who, why, how long, what happens next. If a sentence in your draft does none of those, it can go.

Make starting effortless

Once someone clicks, the first screen has to confirm what the invitation promised: what the survey is for, how long it takes, and one button to begin. Then make the first question easy and clearly relevant, so that answering it feels like progress rather than paperwork.

Remove everything between the click and that first question. Plumeform surveys never ask respondents to create an account or sign in, and they are designed for phones first, which matters whenever an invitation is read on one.

Keep it short and relevant

Every extra minute is another point at which someone can decide to stop. Set a time budget for your audience and cut to it; the article on how long a survey should be shows how. Where a question only applies to some people, route the others past it instead of asking everyone.

Remind once or twice

A reminder reaches people who meant to answer and did not get to it. Send it only to people who have not responded yet, if your list lets you tell them apart, and write a new first line instead of resending the same message: someone who skipped the first version will skip the same words again.

Stop after one or two reminders. By the third, you are mostly reaching people who have decided not to answer, and each message spends goodwill you will want next time.

If you share a survey in several places, give each channel its own link. In Plumeform, each link per channel counts its own views, starts and completed responses, and the source is stored with every response, so you can see which invitation is working and where a reminder would do the most good. Each channel link also comes with a QR code to download, for posters, printed handouts and slides.

Use incentives carefully

Incentives can raise participation, and for research panels payment is the norm: participants are compensated for their time. For customer and employee surveys, think about what an incentive changes as well as how many answers it brings. A large prize attracts people who are there for the prize, and an incentive offered to some groups and not others changes who answers.

If you offer one, make it the same for everyone, never make it depend on what people say, and tell people what it is before they start.

Close the loop

People remember what happened after the last survey. If they answered and heard nothing, the next invitation arrives with that memory attached.

Share a short summary of what you learned and one or two things you will do because of it. It does not need to be a report; a paragraph in the next newsletter or team meeting is enough. If you want to share the numbers themselves, a Plumeform public results link shows the charts and counts on a read-only page, without free-text answers or individual responses.

More responses are not the goal

A higher response rate is a good sign, but it is not the point. What matters is whether the people who answered differ from the people who did not in ways that affect your question. That gap is nonresponse bias, and collecting more answers from the same kind of people does not shrink it. It only makes a biased number more precise.

So when a push for responses works, check who it brought in. If one group is thin, a targeted follow-up to that group will do more for your results than another round to everyone. The sample size guide covers how many responses you actually need, and how to plan invitations from the response rate you expect.