Auto-chase SurveyMonkey non-responders and report to Slack

Every Tuesday we find the surveys stalling below your target response rate, remind only the people who never answered, and post the numbers to Slack.

Agentic Task
SurveyMonkeySlack BotOperationsMarketingEmail AutomationDaily DigestsResearch & Monitoring
PromptCreate

Every Tuesday at 9am, chase my open SurveyMonkey surveys so response rates stop stalling out. The goal is to get every live survey to at least a 40 percent response rate by sending targeted reminders only to the people who have not answered yet.

Start with Search Surveys to find my active surveys. For each one, use List Survey Collectors to get its distribution channels, and focus on email invite collectors, since those are the only ones with named recipients I can actually chase. Use Get Collector to read each collector's close date.

For each email collector, use List Collector Messages to see the invites and reminders that have already gone out, and Get Message Stats on each message to pull its delivery and response statistics. Use those numbers to work out the survey's current response rate, meaning how many of the people invited have actually responded. Judge whether a survey is genuinely underperforming rather than merely young: an invite that went out yesterday is not the same situation as a survey that has been open three weeks and is sitting at 12 percent.

Use List Message Recipients on the existing messages to build the exact list of people who have not responded. Cross-reference recipients across every message on the collector, so you know how many reminders each individual person has already received.

For any survey sitting below a 40 percent response rate, write a fresh reminder using Create Message on that collector, using the reminder message type rather than sending a brand new invite. Draft subject and body copy that fits what the survey is actually about and acknowledges that this is a follow-up rather than a first ask. Attach only the non-responders using Add Message Recipients (Bulk), then send it with Send Message.

Hard rules. Never include anyone who has already responded. Never send a third reminder to the same person, so anyone who has already had two reminders is excluded even if they still have not responded. Skip any survey already at or above the 40 percent target. Skip any survey or collector that closes within the next 24 hours, since a reminder landing after the survey shuts is wasted.

Finish by posting one summary to my team channel with the Slack Bot Send a Message action. List each survey with its current response rate, how many reminders just went out for it, and call out which surveys are at risk of closing below target so someone can decide whether to extend the deadline. If nothing needed a reminder this week, still post a short all-clear so the team knows the check ran.

Example output

Survey chase for Tuesday 9am Q3 Customer Satisfaction: 31% response rate (54 of 174). 108 reminders sent. Onboarding Feedback: 47% response rate (23 of 49). Above target, no reminder sent. Partner NPS: 22% response rate (11 of 50). 28 reminders sent. At risk, closes Thursday. Employee Pulse: 38% response rate (95 of 250). Closes in 18 hours, skipped. Totals: 4 surveys checked, 136 reminders sent, 2 at risk of closing under target.

What does this prompt do?

  • Checks every open survey each week and works out how many of the people you invited have actually responded.
  • Sends a fresh reminder only to the people who have not answered yet, so nobody who already responded gets pestered.
  • Caps reminders at two per person, and skips any survey already hitting target or closing within a day.
  • Posts one weekly summary to your team channel with each survey's response rate, how many reminders went out, and which surveys are at risk of closing under target.

What do I need to use this?

  • A SurveyMonkey account containing the surveys you want chased
  • Surveys sent out through email invitations, since those are the ones with named recipients who can be reminded
  • A paid SurveyMonkey plan, which is what allows reminders to be sent through email invitations
  • A Slack workspace and a channel for the weekly summary

How can I customize it?

  • Change the target response rate from 40 percent to whatever counts as healthy for your surveys
  • Raise or lower the cap on how many reminders any one person can receive
  • Move the run from Tuesday morning to any other day and time that suits your team

FAQs

Will people who already responded get a reminder?
No. Before anything goes out, the workflow checks who has responded and removes them from the list, so reminders only reach people who never answered.
How many reminders will one person get?
Two at most by default. Anyone who has already received two reminders is left out of later sends even if they still have not responded. You can raise or lower that cap.
What happens to surveys that are already doing well?
They get skipped. Any survey at or above your target response rate receives no reminder, but it still appears in the weekly Slack summary so you can see where it stands.
Does this work on a free SurveyMonkey plan?
Sending email invitations and reminders needs a paid SurveyMonkey plan. On a free plan the workflow can still report response rates to Slack, but it will not be able to send the reminders.
What if a survey is about to close?
Surveys closing within the next 24 hours are skipped, since a reminder would probably arrive too late to matter. They are flagged in the Slack summary as at risk of closing under target, so you can extend the deadline if it is worth saving.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

Stop watching your survey response rates stall.

Let this run every Tuesday so the right people get chased and your team sees exactly where each survey stands.