Ask what helps you decide
Collect relevant experience, participant details and preferences for the trip. Keep the requested departure, room and party size attached to the application.
Collect relevant experience, preferences and participant information before accepting a booking. Keep the requested departure, room and next steps with the application.
Some trips need an experience check; some retreats or creative programmes curate the group. The application should state what you are reviewing and what happens next. Keep the departure, party and accommodation preferences with the submission so acceptance can lead into payment and preparation.
An application in a separate form leaves the team matching answers to room requests, capacity and email conversations. Review needs the trip context, then a clear route to confirmation for the accepted guest.
Explore the connected platformLea applies for the September departure and explains their walking experience. The team reviews the application against the trip and capacity, then invites payment for the accepted place.
6–12 September · room preference · Experience + relevant questions
Application + departure capacity · Clarify details or accept
Clear payment invitation · Confirmation follows your process
Required forms + documents · Travel details + guest itinerary
Collect relevant experience, participant details and preferences for the trip. Keep the requested departure, room and party size attached to the application.
Use the application alongside capacity and the guest’s information. Decide whether to accept, request more information or suggest a different departure.
Send the approved guest a clear route to pay and confirm. Once the booking is in place, the same record continues into forms, documents, messages and the itinerary.
Experience · goals · party size · room preference
Departure capacity · relevant requirements · internal notes
Payment invitation · booking status · preparation tasks
Configure messages around confirmation, payment due dates and arrival. Your team can focus on the guests and tasks that still need attention.
Acknowledge the application and explain the review step.
Send the payment invitation and relevant booking information.
Continue with the normal preparation and departure messages.
Guests understand that the trip involves an application and know the next step once the team has reviewed it.
Your team can review fit without losing booking context, then connect the accepted guest to payment and the normal preparation workflow.
Yes. Keep the application and guest context together while the team clarifies the relevant details.
No. Make the review stage clear; the booking becomes confirmed through your approval and payment process.
Yes. Keep review and confirmation distinct. Explain the payment and confirmation steps clearly to the guest, with the approved application connected to the booking journey.
Yes. Use a branded booking link, an embedded journey or an agreed custom integration. We map your booking model, configure the trips, payments, forms and messages, and help connect your website during free setup.
We’ll show you how Marnie brings your bookings,
guests and team together.