Unhandled Response Reminder

Goal: Detect responses that still need follow-up and remind the owner. Fields: Respondent email address, Response body, and Score. Check status, owner, last-updated time, and next-action date. Rules: Notify responses needing follow-up with no update for 24 hours, raise priority after 48 hours, and exclude completed items. Actions: At each chat review, compare open-response notes with available sent history from get_email_activity and calculate 24-hour and 48-hour age from a verified last-action time. A sent event may not distinguish an individual reply from an auto-reply; ask the operator when unanswered status cannot be established. Summarize current reasons, next actions, and deadlines by owner, then notify only operator-specified owner addresses through send_bulk_email emails after preview confirmation. Add followup_reminded only after a verified send and leave unfinished work open. This prompt does not configure automatic re-evaluation at 24/48 hours; run it again at each review point. 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.