Barq Meet
Create your free link

How to send guests to a thank-you page after booking

On this page

What should you prepare for a booking confirmation redirect?

Prepare a published thank-you page, the event it belongs to and a test inbox. Start with the destination copy. A page that says "Your request is received" can cover pending submissions, while "Your appointment is confirmed" requires you to know that approval isn't still outstanding.

You don't need a separate appointment type merely to create a thank-you page. Configure the destination on the event whose guests should land there, then test that event's actual public URL.

Our booking insights overview explains source reporting inside the account. A visit to a thank-you page is a browser action, so keep it distinct from the booking record when deciding what to count.

Where do you set redirect after booking?

Open Booking page in the event editor, expand "After booking" and enter the destination in "Redirect URL after booking". Use a complete URL. A misspelt path can leave the booking accepted but send the guest to a missing page, so test the destination independently before making a trial appointment.

  1. Open the event whose guests need the thank-you page.
  2. Select Booking page and expand "After booking".
  3. Paste the published destination into "Redirect URL after booking".
  4. Decide whether the receiving page needs booking details in the URL.
  5. Save and submit a test booking through the public page.
  6. Check the landing page and the booking status in the host account.

We show the redirect on the booking result screen, with "Pause redirect" and "Continue now" controls. The guest can therefore pause that navigation; a submission doesn't guarantee the destination page was viewed.

Use neutral copy if the same event can require approval. A thank-you page should help the guest understand the next action without upgrading a request into a confirmed appointment through wording alone.

Which details can the redirect pass to your website?

Enabling "Pass booking details to redirect" adds uid, start, end, name and email as query parameters. Make that an explicit choice. The receiving page doesn't need a guest's name or email merely to display a general acknowledgement that an appointment request was submitted.

ParameterMeaning
uidBooking identifier
startBooking start timestamp
endBooking end timestamp
nameGuest name
emailGuest email address

We leave the extra data conditional on that toggle; the redirect itself can work without appending those fields. Review how the destination handles its URLs before enabling it, especially if its analytics or server logs capture query strings.

The parameters don't include a confirmation-status field. A page can't establish approval merely by seeing a uid in a URL, and a visitor can alter query parameters before loading it.

Keep private booking details out of general analytics events. If the receiving application needs authoritative status, verify it through a trusted server-side process instead of treating a browser URL as authenticated evidence.

Can a thank-you page count confirmed appointments?

A thank-you page can count visits, but a visit alone doesn't establish a confirmed appointment. Check status at the booking source. Pending requests can reach the result screen too, and repeated loads of a destination can produce multiple page views for one original submission.

For example, suppose ten people submit a booking request and two remain pending. That's eight confirmed appointments only if the account records the other eight as confirmed; ten thank-you visits don't prove that total.

If one guest reloads twice, the receiving site could record twelve page views from those ten original arrivals. That's a hypothetical counting example, not a claim about your analytics configuration or a measured conversion rate.

We offer booking-source and UTM insights to help attribute recorded appointments. Our UTM setup guide explains how to keep the incoming campaign information distinct from a later destination-page visit.

How do you test the thank-you page after scheduling?

Book once using a test inbox, observe the result screen and confirm the expected destination loads. Then inspect the host record. Repeat with approval enabled if that is how the event will run, because the destination copy must remain accurate while a request is pending.

Check the following cases before using the address in a live campaign:

SymptomExplanation to investigateFix or test
Correct booking, missing destination pageURL path or site publication issueOpen the saved destination directly
No automatic arrivalGuest paused navigation or browser interrupted itTest Continue now on the result screen
Name/email visible in the addressDetails toggle is enabledTurn it off if the page doesn't need those fields
Pending request greeted as confirmedDestination copy assumes approvalUse request-received wording or verify status

We don't create your external website or control how it measures visits. In an embedded booking page, test the real placement too; don't assume navigation inside a frame behaves like the standalone page.

The webhook-to-CRM guide covers a server-side event path when a browser visit isn't enough. A redirect and a webhook have different recipients and different failure modes.

What happens if you leave the redirect field empty?

Without a destination, the guest remains on the normal booking result screen, where they can inspect the appointment and its management options. That's often enough. Add a redirect when the next page gives them something they need, such as preparation instructions, instead of moving them solely to make a counter increase.

We show pending and confirmed states differently on the result screen. Replacing that context with an external page means your page must explain any remaining approval step accurately.

Redirect settings are included without a paid upgrade in Barq Meet, subject to generous fair-use controls. Read the appointment settings included, or create an event with your own thank-you destination after testing both the accepted request and the landing page.

Steps

  1. Publish the intended thank-you page

    Open its full URL directly and confirm the copy covers the event's approval behavior. Keep personal details out of the address unless the page needs them.

  2. Open Booking page for the event

    Expand After booking and find Redirect URL after booking. Paste the full published destination.

  3. Choose whether to pass booking details

    Leave Pass booking details to redirect off for a generic acknowledgement. Enable it only after checking how the receiving page handles its query parameters.

  4. Submit a test booking

    Save the event and book once through its public page. Check both the result screen's redirect controls and the destination.

  5. Compare the landing page with status

    Inspect the host record and repeat for a pending request if approval is enabled. Adjust wording that implies confirmation before the request is approved.

Frequently asked questions

Can I use the redirect as proof that a visitor paid?

No. Barq Meet doesn't collect appointment payments, and a browser arrival doesn't establish a payment transaction elsewhere. If payment is part of your process, verify it through the payment system before recording the appointment as paid. Verify settlement through the payment process itself, because a browser arriving at a thank-you address doesn't establish that an invoice was paid or that any required financial check succeeded.

Will the destination receive the appointment status automatically?

No status parameter is added by the documented details toggle. The optional fields are the booking identifier, start, end, guest name and guest email, so an external page must obtain authoritative status another way if it needs it. Fetch or verify booking state through the documented integration when the destination needs it, instead of inferring status from the fact that a visitor loaded a page after leaving the form.

Do I need guest details for a generic thank-you message?

No. Leave the details toggle off when the destination only acknowledges submission or displays general preparation instructions. That avoids adding names and email addresses to the URL when the receiving page has no reason to use them. Keep the thank-you page neutral when no personalized detail is needed, avoiding unnecessary guest information in a URL that may be forwarded or captured in website logs and browser history.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link