FOR EXAMPLE, TABLES FOR “AFTERNOON TEA”
Using the recently announced prepayment feature, we want to be able to take a deposit for people wanting certain dishes, like afternoon tea or sunday lunch.
We can set a custom field on the tabkle booking form asking what the customer would like (e.g AFTERNOON TEA? Y/N) but we are unable to use that to route onl;y those people down the prepayment path.
As it stands it is all all nothing based on a “number of people” rule.
Any ideas please?
FOR EXAMPLE, TABLES FOR “AFTERNOON TEA”
Using the recently announced prepayment feature, we want to be able to take a deposit for people wanting certain dishes, like afternoon tea or sunday lunch.
We can set a custom field on the tabkle booking form asking what the customer would like (e.g AFTERNOON TEA? Y/N) but we are unable to use that to route onl;y those people down the prepayment path. HealthCareGov
As it stands it is all all nothing based on a “number of people” rule.
Any ideas please?
To handle prepayments for specific dishes like afternoon tea while still using a general booking system, consider the following approach:
Custom Fields: Continue using the custom field on the booking form to ask if the customer wants afternoon tea (Y/N).
Conditional Logic: If your booking system allows for conditional logic, set it up so that if a customer answers “Y” for afternoon tea, they are automatically routed to the prepayment process. If they answer “N,” they can proceed without the prepayment.
Separate Booking Forms: If possible, create separate booking forms for dishes that require a prepayment (like afternoon tea or Sunday lunch). This way, customers who select these options will automatically go through the prepayment process.
Post-Booking Confirmation: If you can’t route them differently during the initial booking, consider sending a follow-up email after the booking confirmation. This email could prompt them to make a prepayment for specific dishes they indicated.
Payment Link: If a customer indicates they want afternoon tea, include a payment link in the follow-up email or a booking confirmation that directs them to a secure payment page.
Manual Review: As a fallback, you can manually review bookings for afternoon tea and send an invoice or payment request to those customers.