Event Capacity + Waitlist

Goal: Switch event registration between accepted, waitlisted, and closed when capacity is reached. Fields: Respondent email address, Response body, and Target date and time. Read party size and requested slot from the response body. Rules: Confirm the registration if capacity remains, waitlist it if capacity is full, and close it if the registration deadline has passed. Actions: Read capacity, deadline, and registration settings with get_form; configure update_form and set_waitlist only for operator-confirmed rules. Capacity counts responses in one form; do not infer available seats across party sizes or multiple slots. Native waitlist entries have no response ID and are not returned as responses by get_responses; never target them with reply_to_respondent or update_response. The configured native waitlist mechanism handles offer notices from actual capacity and expiry. Use reply_to_respondent only for ordinary registrants with a verified existing response ID, and append verified business tags to those responses. 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.