Inquiry Auto-reply + Escalation

Goal: Handle inquiry receipt, auto-reply, categorization, and escalation in one flow. Fields: Respondent email address, Response body, and Owner. Extract inquiry type, urgency, and information needed for reply from the response body. Rules: Prioritize outage, refund, and cancellation requests; route sales inquiries to sales; keep general questions in normal support. Actions: Review and configure the acknowledgment using auto_reply in update_email_template. Classify inquiries and prepare owner routing when this prompt runs in chat. Store normal_support, priority_support, or sales_followup as business tags and proposed owner and due date in notes. Do not treat AI classification or owner notification as an always-running background process. 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.