Confirmation page
A guest’s confirmation page is the page they land on right after submitting a booking request, whether they submitted it themselves or your team entered it for them on the phone. It exists for every request, whether or not your account has online payments turned on. This page covers what it shows and how your team can use it.
What the guest sees
Section titled “What the guest sees”The confirmation page’s heading reflects exactly where the request stands:
| Situation | What the guest sees |
|---|---|
| Online payments on, price known, not yet paid | “Finish booking [boat],” holding the request for 24 hours, with the Due now amount and a button to pay. |
| A payment attempt failed | “Your payment was unsuccessful,” with a button to try again. |
| A payment session expired unpaid | “Your payment session expired,” with a button to start a fresh one. |
| A payment is processing | “We’re processing your payment.” |
| Payment received | “Payment received,” noting that the booking itself is not yet confirmed; your team still does that from the request queue. |
| Online payments off, or no pricing configured for this boat/date range | “We have received your request,” and (when there’s a price) a note that your team will follow up with payment details. |
In every case, the request itself is already sitting in your request queue, and nothing about payment changes whether or when you see the lead.
Using the confirmation-page link to get a guest to payment
Section titled “Using the confirmation-page link to get a guest to payment”The same copyable confirmation-page link shown on a request in Reviewing requests is what a guest would land on themselves, so it’s the fastest way to get a guest you’re in touch with (by phone, email, or any other channel) to payment without them needing to search your site again:
- While you’re in touch with them: open the request, copy the link, and send it over before you end the call or the conversation.
- Afterwards: the link still works whenever the guest is ready. It always reflects the live status (unpaid, paid, or ready to retry), so it’s safe to send more than once.
