Renewal Risk Alert

Goal: Detect renewal-risk or churn-signal responses and hand them to the owner. Fields: Respondent email address, Response body, and Score. Detect cancellation, competitor, price dissatisfaction, stopped usage, and low-score signals. Rules: Prioritize only responses with risk terms or low scores, and separate them from normal requests. Actions: Save the risk reason, recovery suggestion, proposed owner, and due date from verified response content in notes, and add renewal_risk as a business tag. Treat this as a review signal rather than proof of cancellation, rejected renewal, or customer contact. 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.