Low-score Survey Owner Alert

Goal: Identify low-score responses during a chat review and ask the owner to respond. Fields: Respondent email address, Response body, and Score. Summarize the complaint and expected outcome from the response body. Rules: Notify Slack only when the score is 2 or lower, or when the text includes cancellation, dissatisfaction, refund, or similar risk terms. Actions: Review the target responses in chat and post respondent, score, summary, reply draft, and confirmed due date through Slack MCP. Use a low_score_owner_pending business tag; a Slack post does not resolve the response. 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. External connections: Separate Slack MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.