Sends depend on someone remembering
Someone exports last week's closed cases every Monday and uploads a list. The survey arrives days after the conversation it asks about, or not at all when that person is on leave.
SurveyMonkey · Workflow Automation
SurveyMonkey automation services that act on every response
SurveyMonkey automation makes surveys send themselves when something happens in your business, and makes each response start the next piece of work without anyone watching an inbox. Twopir Consulting designs and builds it: Salesforce Flow and scheduled sends that reach the right person at the right moment, reminders and thank-yous, alerts in Slack or Microsoft Teams, and follow-up routing that gives every unhappy customer an owner and a deadline. The goal: no survey sent by hand, and no detractor left without an owner.
12+
500+
250+
40+
Trusted by 500+ organizations — including software, telecoms, hospitality and consulting businesses that run their customer processes on CRM automation built with Twopir Consulting.
What We Automate With
- Salesforce Partner
- Salesforce Flow
- SurveyMonkey for Salesforce
- Email Invitation Collectors
- Connect Quick Actions
- Slack
- Microsoft Teams
- Zapier
The survey goes out. Then nothing happens.
Most feedback programmes are automated at one end only. Invitations go out on a schedule, responses pile up, and the work a response should trigger still depends on someone reading it. These are the six gaps we find most often when we review a survey operation.
Detractors without an owner
A customer scores you a 2 and writes why. The response sits in SurveyMonkey, nobody on the account sees it, and the next conversation about it is the cancellation.
Alerts nobody reads
Every response is posted to a busy channel, so the one that needs action scrolls past with the forty that do not. Too many alerts end up working like none.
The same customer surveyed three times
Support, onboarding and marketing each automated their own survey. One contact gets three in a fortnight, and response rates fall for all of them.
Automations that fail silently
SurveyMonkey warns that editing an integration email in the collector instead of the integration can break custom data and the automation. Nobody notices until the scores stop arriving.
Automation tied to one person's login
Salesforce mappings are saved to the connected Salesforce user and stop working if that user is deactivated. A resignation can switch off a feedback programme overnight.
Definition
SurveyMonkey automation, defined
SurveyMonkey automation is the set of rules that sends a survey when a business event happens, follows up with respondents without manual effort, and turns each response into the next action, such as a channel alert, a follow-up task or an escalated case, without anyone watching the survey account. SurveyMonkey automation services design those rules, build them across SurveyMonkey and your CRM, and test and monitor them so they keep working after the people who set them up move on.
It helps to be precise about who does what. SurveyMonkey automates delivery: email invitations sent now, on a date or on a recurring schedule, automated reminders and thank-you emails, and Connect quick actions that post responses to Slack or Microsoft Teams or export them to a spreadsheet. The details are in SurveyMonkey's help center. Your CRM automates the work: in Salesforce, Flow decides when a survey is sent and what happens after a response lands on the record. Twopir Consulting designs the rules that join the two (eligibility, routing, escalation and suppression), builds them and documents who owns them.
Do you need a partner for this? One survey with a weekly reminder does not. A partner earns its place when sends must follow CRM events, when responses must create work for named owners, when several teams survey the same customers, or when the automation has to survive staff changes and audits. We help growing and mid-market companies solve complex CRM, integration and business system challenges, and we bring the same closed-loop design to enterprise teams running SurveyMonkey Enterprise.
Which systems the survey data should reach in the first place is covered on our SurveyMonkey integration services page, and the full programme, from instrument design to rollout, on our SurveyMonkey consulting and implementation services page. This page is about what runs by itself once those are in place.
Five stages, native and built
Every survey automation we build runs through the same five stages. For each one, the table shows what SurveyMonkey does on its own, what we build around it, and the plan requirement SurveyMonkey states, so nothing in the design depends on a feature your account does not have.
| Stage | SurveyMonkey does natively | What we build around it | Plan notes |
|---|---|---|---|
| 1 · Trigger the send | Email invitations sent now or scheduled for a date and time. Recurring emails send the same survey to the same group on a schedule, always to the current contact list. | A Salesforce Flow that sends the survey when a record meets your criteria, such as a closed case, a renewal or an onboarding milestone, after the eligibility checks pass. | Recurring emails are Enterprise only. Sending from Salesforce needs SurveyMonkey for Salesforce, an Enterprise add-on. |
| 2 · Personalise | Contacts carry custom data, inserted into invitations with [FirstName], [LastName], [Email] and [CustomData#] tags. Custom variables carry values such as a record ID into the survey link. | The CRM fields behind each tag, and the record ID that lets every response find its way back to the right record. | 6 custom data fields on every plan, up to 50 on Team and Enterprise. Salesforce integration emails take up to 6 custom data tags from Salesforce fields. |
| 3 · Remind and thank | One automated reminder per collector, sent a set number of hours or days after the invitation to non-respondents, partial respondents or both. One automated thank-you on completion. | A cadence chosen per process, so a support customer is not chased like a research panel, and thank-you copy that says what happens next. | Email invitation collectors. Open and click tracking is on some paid plans. |
| 4 · Signal the response | Connect quick actions post responses to Slack or Microsoft Teams, or export them to Excel or Google Sheets, on every response or only on responses with a chosen answer. | Which answers go to which channel, and which answers never get posted because they are sensitive. | Slack posts carry complete responses only, with up to 5 questions. Some question types cannot be used as filters. |
| 5 · Close the loop | SurveyMonkey for Salesforce writes responses onto Salesforce records, either into its managed-package objects or into fields you map. | Tasks, cases, owner assignment and escalation, built in Salesforce Flow from the mapped response data. SurveyMonkey's help center documents no built-in alerting step inside Salesforce. | Enterprise add-on. On an EU data center, the package's Lightning Flows and Components are not available. |
Surveys that send on the right event
A survey is worth most within hours of the moment it asks about. These are the ways we make it go out at that moment, and keep following up, without anyone building a list by hand.
Sends fired by Salesforce Flow
A Flow fires the survey when a record meets your criteria: as a web link in your own email template, as a SurveyMonkey email invitation through an Outbound Message SurveyMonkey builds for you, or as a text once SurveyMonkey enables it. New triggers are built in Flow, because Salesforce no longer allows new workflow rules. Setup detail is on our SurveyMonkey Salesforce integration page.
Scheduled sends
An invitation written once and sent at a date and time you choose, such as the morning after an event or the first working day of a quarter. Useful where the trigger is the calendar, not a record.
Recurring sends
On Enterprise, recurring emails send the same survey to the same group on a schedule, always to the current contact list. That suits a quarterly pulse or relationship NPS, as long as the list itself is kept current.
Automated reminders
One automated reminder per collector, sent a set number of hours or days after the invitation, to people who have not responded, who stopped partway, or both. It also covers people invited later. Extra one-off reminders are unlimited.
Automated thank-yous
A thank-you email sent on completion, at the next half-hour mark. One is allowed per collector, and each recipient receives it once. We use it to tell the respondent what happens next.
Custom data tags
Names, account names, case numbers or renewal dates inserted into the invitation from contact custom data. The same values appear beside each response and can be used as filters in Analyze.
Contact lists
Contacts imported from CSV or common mail tools and organized into groups. We treat each list as a working copy of the CRM and define how and when it is refreshed, so a recurring send never reaches last year's customers.
Webhooks as triggers
Where no connector exists, a SurveyMonkey webhook on an event such as a completed response lets another system act straight away. Building and securing that endpoint is engineering work, covered on our SurveyMonkey API and custom integration page.
Every detractor gets an owner and a deadline
Closing the loop means a person is responsible for each response that needs action, knows by when, and records what they did. Once the score is on the Salesforce record, Flow can do the assigning and the chasing. The rules below are our starting design; thresholds, owners and due dates are set with you.
| Signal | What the automation does | Owner | If nobody acts |
|---|---|---|---|
| NPS detractor (0 to 6) | Creates a follow-up task on the account with the score and comment, and flags the account for the next review. | The account owner | Past the due date, the task is reassigned or copied to the owner's manager. |
| Low CSAT after a support case | Opens a follow-up case linked to the original, so the support lead sees it in the same queue as any other case. | The support lead's queue | A second low score on the same account goes to customer success as well. |
| A specific answer, such as "unlikely to renew" | A Connect quick action posts the response to the account team's Slack or Teams channel, and Flow creates the task. | The account team | With a renewal coming up, the renewal owner is added. |
| Onboarding check-in reports a blocker | Creates a task for the onboarding manager with the answer that raised it. | The onboarding manager | Escalates to the implementation lead. |
| NPS promoter (9 or 10) | Creates a referral or review request task, only if no open case or escalation exists on the account. | The account owner | No escalation. The task closes on its due date. |
| No response at all | SurveyMonkey's automated reminder runs once. After that, nothing: no rep is asked to chase a survey. | None | Counted in response-rate reporting, not worked as a task. |
Collect, remind, signal
Sending the invitation, reminding and thanking respondents, posting chosen responses to Slack or Microsoft Teams, and writing each response onto the Salesforce record through SurveyMonkey for Salesforce.
Configured, not coded, and maintained by SurveyMonkey.
Assign, chase, record
Deciding who owns a response, creating the task or case, setting the due date, escalating when it slips, and recording the outcome where your reports already look. All of it in Flow, which your admins can read and change.
For CRMs other than Salesforce we build the same rules in Zapier, through our Zapier integration services.
Survey fatigue rules, checked before every send
Automation makes it easy to send too much. Every automated send we build checks a short set of rules first, so customers hear from you when it matters and your response rates hold up.
| Rule | How it is enforced |
|---|---|
| A cooling-off period per contact | A "last surveyed" date on the contact, written when a response syncs and checked by the Flow before it sends. You set the length of the period. |
| One response per person per survey | Native: an email invitation collector accepts one response per email address. |
| No accidental re-invites | "Allow duplicate invites" is an Enterprise option. We leave it off for event-triggered surveys and turn it on deliberately for recurring ones. |
| Opted-out contacts excluded | Email opt-out fields sit in the Flow's entry criteria. For text sends, a suppression list sync field excludes opted-out recipients, and SurveyMonkey adds a fixed opt-out line. |
| Fix the problem before asking about it | No satisfaction survey while another case is open for the same contact, and no NPS while an escalation is open on the account. |
| One survey wins when two qualify | A written priority order, such as renewal NPS before an onboarding check-in, applied in the Flow. |
| Internal and test records excluded | By record type, email domain or a test flag, so staff and sandbox data never receive or skew a survey. |
Six processes, automated end to end
Each design names the event that starts it, how the survey goes out and what a response sets in motion. These are the processes we automate most often.
CSAT After Case Close
Every closed case gets a short satisfaction survey while the conversation is fresh, and every low score reopens the conversation.
- Trigger
- Case status changes to Closed, no other open case for the contact
- Send
- SurveyMonkey email invitation fired by Flow, one reminder
- Response sets off
- Score on the case; low scores open a linked follow-up case
NPS After Renewal
A relationship survey timed to the renewal, so the account team learns how the customer feels while there is still a year to act on it.
- Trigger
- Renewal opportunity closed won, primary contacts only
- Send
- Email invitation with the account name as a custom data tag
- Response sets off
- Detractor task to the account owner; promoter referral task
Onboarding Check-Ins
Short check-ins at set onboarding milestones that catch a stalled rollout before it becomes a churn risk.
- Trigger
- Onboarding milestone reached on the account or project record
- Send
- Flow-fired invitation, record ID carried as a custom variable
- Response sets off
- Blocker answers create a task for the onboarding manager
Event Registration Confirmations
Registration forms that put each registrant into the CRM and confirm the place without anyone forwarding an email.
- Trigger
- A SurveyMonkey registration form is submitted
- Send
- Lead created or updated in Salesforce; Flow sends the confirmation
- Response sets off
- Post-event survey scheduled for the morning after the event
Won and Lost Deal Surveys
Win/loss feedback collected on every closed deal, not only the ones a sales manager remembers to ask about.
- Trigger
- Opportunity closed won or closed lost, above a value you set
- Send
- Separate won and lost surveys, sent by Flow to the deal contact
- Response sets off
- Reasons written to the opportunity; competitor answers alert product marketing
Employee Pulse Surveys
A recurring pulse to the current workforce, kept separate from customer data and from the CRM entirely.
- Trigger
- A recurring schedule (Enterprise)
- Send
- Recurring email to a list kept current by SurveyMonkey's Workday or BambooHR sync
- Response sets off
- Chosen answers posted to an HR Teams channel; no individual tasks
Automations that fail loudly, not silently
An automation nobody watches will eventually stop without telling anyone. For each point where a survey automation can break, we decide in advance where the failure shows up and who looks at it.
| What can break | Where it shows, and what we put in place |
|---|---|
| A response does not reach Salesforce | Failed syncs are written to the mapping's Error log, and successful ones to the Audit log. A named owner reviews the Error log on a fixed rhythm. |
| A Flow fails before the send or during routing | Fault paths on every Flow that log the error and notify an admin, as in our guide to Salesforce Flow fault paths. |
| An integration email is edited in the wrong place | SurveyMonkey says these emails must be edited in the integration, not the collector. That becomes a written rule, and a test response follows every edit. |
| A Connect quick action loses its authorisation | The Manage tab, where quick actions are toggled or re-authenticated. Each action is authorised by a service account with a named owner. |
| The connected Salesforce user is deactivated | Mappings stop working. We connect an integration-specific Salesforce user, which can use the Salesforce Integration user licence. |
| A Salesforce sandbox is refreshed | The sandbox connection breaks. We reconnect it and copy the mappings across before testing resumes. |
| A webhook endpoint is unavailable | SurveyMonkey does not document retry behaviour, so custom triggers get a reconciliation step. Covered on our API integration page. |
From manual sends to a loop that runs itself
Six phases, each with a deliverable your team keeps. The length depends on how many processes are automated, how many teams own follow-up, and whether existing automations need rebuilding, and we scope it before you sign.
Process Discovery
The surveys you run, what triggers each one today, who acts on the answers, and every existing reminder, alert, export and workflow, with its owner.
DeliverableCurrent-state map of sends and follow-up
Automation Rulebook
Trigger criteria, eligibility and suppression rules, routing, owners, due dates and escalation for each process, agreed with the teams who will do the follow-up.
DeliverableAutomation rulebook, signed off
Plan & Platform Check
Each rule checked against your SurveyMonkey plan, add-ons and data center, such as recurring sends on Enterprise or Lightning components outside the EU data center.
DeliverableFeasibility per rule, gaps listed
Build
Collectors, reminders and thank-yous configured, Connect quick actions set up, and Flows built in a sandbox under an integration user, with fault paths from the start.
DeliverableWorking automations in a sandbox
Test & Go-Live
The test script run end to end, including the sends that must not happen. Then a controlled switch-on, one process at a time.
DeliverablePassed test log and live automations
Tune & Hand Over
Thresholds and cadence tuned on real responses, admins trained on the rulebook, and ongoing support on offer for changes, failures and sandbox refreshes.
DeliverableRulebook, runbook and support plan
What changes when feedback runs itself
The value of survey automation is not the number of emails it sends. It is the follow-up that now happens every time, without depending on who is in the office.
Surveys at the Right Moment
Invitations go out when the event happens, so customers answer about the experience they just had.
- No weekly list exports
- Sends continue through holidays and staff changes
- The same rule applied to every record
No Unowned Detractor
Every response that needs action becomes work for a named person, with a due date and an escalation path.
- Tasks and cases where the team already works
- Escalation when follow-up slips
- The outcome recorded on the record
Fewer, Better-Timed Surveys
Suppression rules protect customers from being surveyed by three teams in one month.
- A cooling-off period per contact
- No survey while a problem is still open
- One survey wins when two qualify
Signals Worth Reading
Channels receive the responses that need attention, so an alert means something when it arrives.
- Filtered by answer, not every response
- Sensitive answers kept out of channels
- Each alert backed by a task
Failures Seen by Your Admins
When something breaks, an admin hears about it from a log or a fault path, before a customer or a manager does.
- Error log with a named reviewer
- Fault paths on every Flow
- No automation tied to a personal login
Rules Your Team Can Change
The rulebook says what each automation does and why, so a new threshold or owner is a quick admin change.
- Every rule written in plain language
- Flows your admins can read
- A test script for every change
Event-driven automation we have delivered
Neither engagement below is a SurveyMonkey deployment. They are here because the work is the same kind: a CRM event triggers an alert or a record, the right owner receives it, and the noise is tuned out. Each figure is scoped to the engagement that produced it.
SaaS Company — Slack Sales Elevate
Salesforce deal events turned into Slack alerts and deal channels, with Salesforce kept as the system of record.
0 Manual steps for stage-change alerts
5 User groups aligned on one system
5 Rollout issues found and resolved
- Alerts on stage changes, closed-won deals and renewals
- Workflow conditions that sent too many alerts were corrected during rollout
US Enterprise — Forms to Salesforce
FormTitan submissions turned into Salesforce leads, contacts and cases in real time, routed by Flow to the right owner.
0 Manual data entry steps remaining
5+ Automated workflows deployed
3 Salesforce object types automated
- Duplicate matching against existing records before anything is created
- Routing to the correct owner, and confirmation emails sent by Flow
More engagements are on our success stories page.
Automation designed around the follow-up
Sending surveys automatically is the easy half. The half that decides whether automation pays off is what happens after a response arrives, and that half lives in your CRM.
We write the rules before we build the Flow
Who gets surveyed, who owns each answer, and what happens when nobody acts are decided with your teams first, and written down where your admins can find them.
Salesforce automation is our home ground
Flow design, fault handling, record ownership and queues are everyday work for us as a Salesforce Partner, as is the alerting side, through our Salesforce Slack automation work.
We say what is native and what is built
Reminders and Slack posts are SurveyMonkey features. Detractor tasks and escalations are Flow we build. You always know which is which, and what each one costs to maintain.
We protect the respondent
Suppression and priority rules go into every design, because a programme that over-surveys its customers loses the response rate it was automated to protect.
We stay after go-live
Tuning thresholds on real responses, fixing failed syncs from the error log, keeping mappings on an integration user, and reconnecting after sandbox refreshes.
SurveyMonkey automation questions, answered plainly
SurveyMonkey automation services design and build the rules that send surveys when business events happen, follow up with respondents automatically, and turn each response into the next action. That covers triggered and scheduled sends, reminders and thank-you emails, Slack or Microsoft Teams alerts, and closed-loop routing that creates tasks or cases for named owners in your CRM, plus the testing and monitoring that keep it running.
Yes. Email invitations can be scheduled for a date and time, and on Enterprise, recurring emails send the same survey to the current contact list on a schedule. SurveyMonkey also sends one automated reminder per collector and an automated thank-you on completion. To send when a CRM event happens, such as a case closing, a Salesforce Flow fires the survey through SurveyMonkey for Salesforce, an Enterprise add-on.
Map the score onto the Salesforce record, then let Salesforce Flow do the follow-up: a task or case for the account or case owner, a due date, and an escalation if it is not worked. SurveyMonkey's help center documents no built-in alerting step inside Salesforce, so this routing is built in Flow, or in Zapier for other CRMs. A Connect quick action can also post the response to a Slack or Teams channel.
Check eligibility before every automated send. We use a last-surveyed date on the contact with a cooling-off period you set, no satisfaction survey while a case or escalation is still open, a priority order when two surveys qualify, opt-out fields in the entry criteria, and exclusions for internal and test records. SurveyMonkey adds one response per email address per collector.
Yes, through Connect quick actions, which post responses to Slack or Microsoft Teams on every response or only on responses with a specific answer. Slack posts carry complete responses only, with up to 5 questions and a link to the response, and some question types cannot be used as filters. We decide which answers go to which channel, and keep sensitive answers out.
Scheduled invitations, automated reminders and thank-yous, and Connect quick actions are part of SurveyMonkey's email invitation and Connect features. Recurring emails and allowing duplicate invites are Enterprise only, sending from Salesforce needs SurveyMonkey for Salesforce as an Enterprise add-on, and contacts hold up to 50 custom data fields on Team and Enterprise plans against 6 on others. We confirm each requirement in your account before the build.
Before go-live we push test responses through every path: a promoter, a passive and a detractor, a partial response, a contact inside the cooling-off period, an opted-out contact, a record with no owner and an overdue task. After go-live, failed Salesforce syncs show in the mapping's Error log, Flows carry fault paths that notify an admin, and each Connect quick action has a named owner who re-authenticates it from the Manage tab.
Next Step
Name the moments, we will close the loop
A first conversation covers the surveys you send today, the moments that should trigger them, and who should act on the answers: enough to say what can run natively, what needs building in your CRM, and what the work would take. No obligation to proceed.
Talk to an architect who builds both the sends and the follow-up
