Booking Change Request
Description
3 steps
- 1
Read the new response
At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.
- 2
Decide the next action
Decide the next action from the response, score, date, or category.
- 3
Apply to operations
Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.
Prompt Example
Goal: Organize booking change requests by original booking, requested dates, reason, and urgency. Fields: Respondent email address, Response body, and Target date and time. Always extract original booking time and requested new time. Rules: Save multiple requested times as candidates, and ask for clarification when the original booking or contact details are missing. Actions: Create an acknowledgment draft, internal review note, and candidate-date list. Use change_under_review or needs_clarification business tags. Keep the original confirmed booking until the operator verifies the change, and do not send a change-completed message before then. 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.
For you
- steps
- 3 steps
- Required plan
- Free
- Required integrations
- FORMLOVA
What this workflow solves
Form responses arrive, but organizing booking change requests still depends on manual checking, causing delayed or missed follow-up.
Best for
- reservation desks
- paid application workflows
Expected outcome
When you run the prompt in chat, each reviewed response moves into a clear organizing booking change requests state, so the team can focus on the next required action.
Setup notes
- Connect FORMLOVA MCP in your AI client and confirm permission to read and update responses for the target form.
- 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.
- Response review, organization, and ordinary individual replies are available on Free. Check AI client and external service terms separately.
- Business labels are not response statuses. Read current tags/notes immediately before updating and preserve them when appending; tags allow at most 20 values of 50 characters each. Ask if values cannot be read or limits would be exceeded.
FAQ
Can this work with an existing form?
Yes. Map the existing response fields to the required slots and adjust the notification or record destination.
Read the background
More in this category
Gmail Reservation Confirmation
ReservationsFreeAn official workflow for sending reservation confirmation through Gmail.
Reservation Cancel + Waitlist
ReservationsFreeAn official workflow for contacting waitlisted people when a reservation is canceled.
Reservation Reminder + No-show Prevention
ReservationsStandard+An official workflow for day-before reminders to reduce no-shows.
