Post-event Survey Reminder
Description
3 steps
- 1
Read the new response
At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.
- 2
Decide the next action
Decide the next action from the response, score, date, or category.
- 3
Apply to operations
Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.
Prompt Example
Goal: Remind only participants who have not completed the post-event survey. Fields: Respondent email address, Response body, and Target date and time. Check participant status and survey completion from the response body. Rules: Send the first reminder 24 hours after the event and a final reminder after 48 hours if still unanswered. Do not send to completed respondents. Actions: Confirm the participant mailing_list_id, survey form_id, end time, URL, and an explicit real-email list of non-responders verified by the operator against completed responses. Run separately at 24 and 48 hours; review all pages of get_mailing_list_contacts as supporting evidence and have the operator refresh the verified target list each time. Do not reconstruct masked addresses or match people from similar names or masks alone. Pass only verified non-responder addresses in send_bulk_email emails; do not pass mailing_list_id when sending because it targets the entire list. Send after audience and message preview confirmation; stop if the subset cannot be verified. Never call update_response without a response ID. Return the check time, targets, and actual send results in an operations log. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance.
For you
- steps
- 3 steps
- Required plan
- Premium+
- Required integrations
- FORMLOVA
What this workflow solves
Form responses arrive, but targeted reminders for people who have not answered the event survey still depends on manual checking, causing delayed or missed follow-up.
Best for
- event operations
- registration management
Expected outcome
When you run the prompt in chat, each reviewed response moves into a clear targeted reminders for people who have not answered the event survey state, so the team can focus on the next required action.
Setup notes
- Connect FORMLOVA MCP in your AI client and confirm permission to read and update responses for the target form.
- Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them.
- The required FORMLOVA plan is Premium or higher. Native email operations follow the tool's recipient, copy, time confirmation, and monthly sending limits.
- Business labels are not response statuses. Read current tags/notes immediately before updating and preserve them when appending; tags allow at most 20 values of 50 characters each. Ask if values cannot be read or limits would be exceeded.
- A verified real-email list of non-responders is required. Masked reconciliation alone cannot supply that sending subset. Recheck the audience separately at 24 and 48 hours.
FAQ
Can this work with an existing form?
Yes. Map the existing response fields to the required slots and adjust the notification or record destination.
Read the background
More in this category
Event Reminder + Follow-up
EventsStandard+An official workflow for confirmation, reminders, and post-event follow-up for registrations.
Seminar Registration to Survey
EventsStandard+An official workflow for seminar registration, day-of reminders, and post-event survey.
Slack Notification + Google Sheets Log
EventsFreeAn official workflow for sending form responses to Slack while keeping a Google Sheets operations log.
