Weekly Inquiry Status Report

Goal: Summarize weekly inquiry status and reveal backlog or owner imbalance. Fields: Respondent email address, Response body, and Owner. Read each response status, category, and last-updated time. Rules: Count new, in progress, answered, overdue, and sales-filtered inquiries separately. Actions: At the weekly review, distinguish new, in_progress, resolved, and spam. Determine answered and overdue items separately from reply history and due dates in notes. Report counts, backlog, proposed-owner workload, and next-week priorities. Record weekly_report_created as a business tag. 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. History review: Check all available pages of get_email_activity. Sent events may not distinguish individual replies from auto-replies; missing events alone do not prove that no reply occurred. Corroborate actual replies with the operator and notes, and hold uncertain cases for review.