Inquiry History Note

Goal: Save inquiry history in Notion so future support has context. Fields: Respondent email address, Response body, and Owner. Search existing customers or past inquiries by email address. Rules: Append to existing history when found; otherwise create a new customer note with inquiry type and current handling status. Actions: Match responses from the specified form against history found through Notion MCP. Append summary, proposed owner, due date, reply direction, and links without overwriting existing notes. Confirm ambiguous matches and add history_saved only after the Notion write succeeds. 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 Notion 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.