Reservation Cancel + Waitlist

Goal: Contact waitlisted people in order when a reservation is canceled. Fields: Respondent email address, Response body, and Target date and time. Confirm canceled slot, requested slot, and waitlist priority from the response body. Rules: Pick the next waitlisted person matching the canceled slot, include a response deadline, and move to the next person if it expires. Actions: For the native waitlist, check the shared capacity of one form with get_form. Configure waitlist enablement and offer expiry through set_waitlist using operator-specified values, then verify the successful response. The native mechanism sends offers in queue order when space becomes available and expires offers; the AI must not infer sent or accepted results. Native waitlist rows have no response ID and cannot be read through get_responses; never call reply_to_respondent or update_response for them. For a separately supplied queue and vacancy list, use reply_to_respondent only for candidates whose existing response IDs the operator has verified. Ask instead of using that route for external candidates without response IDs. Confirm multi-slot or party-size allocation separately from native shared capacity. 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.