Survey Throttling

Avoid survey fatigue amongst your respondents with Survey Throttling.

Survey throttling controls how frequently your respondents will receive a survey. Thus, it helps you avoid survey fatigue amongst your respondents.

For instance, when a user receives a survey, you can stop showing the survey to the same user for a particular duration of time. You can set the number of days and time according to your preference.

Note: The Throttling can be done both on Survey level and Account level. Keep in mind that Account level throttling does not apply if the survey level throttling is enabled. 

Advantages of Survey Throttling

  • Survey Throttling prevents you from spamming your respondents with surveys.

  • It allows your respondents the space and time that they deserve between multiple surveys.

  • Enough time between surveys lets you collect interesting insights from your respondents, and survey throttling lets you do that effortlessly.

Note: Survey Throttling doesn't work for reminder emails. You can trigger the remainder emails according to your preferences. 

Let’s see how it works.

  1. On your survey dashboard, click on Settings.


2. Now, navigate to Survey Throttling under Email Settings.



3. Once done, enable the toggle to initiate Survey Throttling.



4. Now that the toggle is enabled, you can set the time and days according to your preference. For example: If you enter 3 times in 30 days, surveys across the platform will be sent to contacts only 3 times in 30 days.



Survey-Level Throttling 

5. To access the survey-level throttling, go to the Survey Builder and Settings, you have Throttling below Set Quotas.

Note: Account level throttling does not apply if the Survey-Level throttling is enabled


6. You can choose to disable the Account-Level Throttling on clicking Open Account Level Settings. 

7. Once done, Hit Save to save the throttling conditions. 

Screenshot 2022-01-19 at 12.40.52 PM

That's it!

Please feel free to reach out to us if you have any questions.

See you in the next one.

Did this answer your question?