Define what complete means
List the fields required for each experience and explain why they are needed. A pickup location may apply to one ticket type but not another. A group booking may require individual participant information. Avoid treating every empty optional field as an unfinished booking.
Write a precise request
Tell the guest which booking the request concerns and what information remains outstanding. Link to the supported completion route. A vague request to update their details creates extra questions; a clear request for a pickup choice is easier to act on.
Check the stopping rules
Before each reminder, confirm whether the information has arrived, the booking has changed or the departure has passed. Set a sensible limit on attempts and a staff escalation for unresolved cases. Test duplicate records and a booker who forwards a participant link to the group.
Measure readiness before departure
Track how many relevant bookings are complete at a defined cutoff and how much manual follow-up remains. Read failed or unanswered requests to find confusing instructions. Success means the team has usable information, not merely that a large number of reminders were sent.
A concrete example
Two bookings are approaching departure. One lacks a pickup point; the other is complete. Only the first should receive that request, and a later completion should stop the reminder.
Put it to work this week
Map one missing-field workflow from detection to completion, including a changed booking and an unanswered request.