Automated Alchemer Partial Response Chasing
Every morning, WebRun opens Alchemer, filters your live surveys to partial responses, notes how far each person got and when they dropped, writes them into a Notion chase list with a drafted nudge, and texts you the count still outstanding.
How do I follow up on people who started my survey but never finished?
WebRun opens Alchemer every morning, filters your live surveys to partial responses, and notes how far each person got before stopping. It writes them into a Notion chase list with a drafted nudge for you to approve and texts you the outstanding count through Twilio, so nearly finished responses are not lost.
- Partial responses surface the next morning instead of at analysis time
- Every nudge is drafted and waiting, so a chase takes a click not an hour
- The question people stop at is visible, so the survey itself can be fixed
Built for research teams · customer experience managers · marketing teams · survey owners
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
alchemer.comin a real browser with your saved login - no setup, no API keys. -
1
Alchemer - find partial responses
WebRun opens Alchemer to find partial responses. - Open Alchemer and go to the responses for each live survey
- Filter the status to partial so only unfinished responses are read
- Capture the contact, the last question reached, and how long ago they stopped
- Skip anyone who came back and completed since the last run
Done when Every unfinished response is listed with its drop-off point.
-
2
Notion - build the chase list
WebRun opens Notion to build the chase list. - Write each partial into your survey chase database
- Record the survey, the contact, the last question reached, and days since the drop
- Draft a short, polite nudge for each one and put it on the row
- Sort so the people who got furthest sit at the top, they are the easiest to recover
- Leave every nudge unsent until you approve it
Done when The Notion chase list holds today's partials with a drafted nudge each.
-
3
Twilio - text you the count
WebRun opens Twilio to text you the count. - Text your own saved number the count of partials waiting and the survey they came from
- Note the most common question people stop at
- Send to your number only. Never text a survey respondent
Done when You know today's partial count without opening Alchemer.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it email or text respondents?
No. Every nudge is drafted onto the Notion row and left unsent for you to approve. The only message WebRun sends is a text to your own number with the count.
Does it change or submit anyone's response?
No. WebRun reads response status in Alchemer and never edits, submits, or deletes a partial. The respondent's own answers are left exactly as they left them.
What if someone finishes later?
They drop off the list. WebRun reads live response status every morning, so anyone who returned and submitted is removed from the chase list on the next run.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.