---
title: "Booking confirmation page text examples"
url: https://meet.barq.dev/templates/booking-confirmation-page-text
updated: 2026-11-17
author: "Hammad Ali"
---

# Booking confirmation page text examples

> **Short answer:** A booking confirmation message should state whether the appointment is confirmed or awaiting approval, then give the next action. The four versions below cover common success-page situations. In Barq Meet, use custom copy on a page you control after a redirect; the built-in success heading isn't an editable text field.


## What should a booking confirmation message tell the guest first?

Tell the guest the actual booking status before asking them to prepare or open another link. A confirmed appointment can say "You're booked", while a request awaiting approval should say that a response is still needed; those messages describe different commitments and should never be interchangeable.


Status comes first. Follow it with the appointment details, the expected email and a route for changing the booking or asking for help.


We show different built-in wording for pending and confirmed bookings in Barq Meet. We also support "Requires approval" under "Booking page", so check that setting before choosing copy for a destination page that all guests will see.


The [booking page feature details](https://meet.barq.dev/features/booking-pages) explain the wider guest flow. These examples belong to the [booking-copy templates](https://meet.barq.dev/templates), and they are copy for a destination you manage, not instructions for replacing the built-in confirmation screen.


## Which booking confirmation message template should I copy?

Copy the version that matches what has happened and what the guest should do next. These booking confirmation message examples keep the joining route separate from the booking URL, and leave date or status details in brackets wherever you must supply real information before showing the text.


Use accurate information only. If your page can't determine whether approval is pending, choose neutral request-received wording instead of publishing a confirmed heading for every visitor.


### Confirmed appointment: reassure the guest and point to the email


```text
Heading: Your appointment is confirmed

You're booked for [Appointment name] with [Host].
When: [Date, start and end time, time zone]
Location: [Joining link or address]

Your confirmation email is on its way. Keep it for the appointment details and the links to change your booking.

Next step: [One preparation action, or remove this line]
Need help? Contact [Monitored contact route].
```


Use this when you know the booking is confirmed and can display the right details. If the destination is a static page without booking data, remove the When and Location lines and direct the guest to the email.


### Pending approval: acknowledge the request without promising the slot


```text
Heading: Your appointment request has been received

Thanks for requesting [Appointment type]. The host still needs to review it.

We'll contact you at the email address used for the request when there's an update.
Please wait for confirmation before treating the appointment as agreed.

If you need to change the request or ask a question, contact [Monitored route].

Next step: Check your email for the host's response.
```


Choose this when approval remains outstanding. Don't add a response-time promise unless you have an operational process that supports it; the scheduling setting alone doesn't make someone reply within your preferred time. For the written reply, use [dated availability-message examples](https://meet.barq.dev/templates/availability-message-examples) instead of an open-ended promise that any time next week will work.


### Confirmed consultation: add one preparation action


```text
Heading: Your consultation is booked

Your [Appointment type] is confirmed. The date and joining details are in your booking email.

Before we meet, please review [Preparation page] and bring [One item or question].
Please don't send confidential documents through this page.

Need another time? Use the reschedule link in your booking email.
If the message doesn't arrive, contact [Monitored address] with your name and appointment date.

Button label: Open the preparation page
Button destination: [Preparation page URL]
```


Use this on a static destination when every confirmed guest needs the same preparation. One practical action is enough; a second long [intake form](https://meet.barq.dev/glossary/intake-form) can make the guest wonder whether the appointment is still incomplete.


### In-person visit: make arrival instructions the next action


```text
Heading: Your visit is confirmed

We're expecting you for [Appointment type]. Check your booking email for the date and time.

Arrival information: [Address, building and room]
Please use [Confirmed entrance or reception process].
Bring [Required item, or remove this line].

For access arrangements or a question before arrival, contact [Monitored route].
To cancel or move the visit, use the links in your booking email.
```


Select this when you manage the destination and the arrival instructions apply to everyone who reaches it. Check the address and access process; the template doesn't establish reception hours or building access.


## Can I edit the built-in confirmation page in Barq Meet?

The current event editor lets you set a redirect destination after booking, but it doesn't provide a field for rewriting the built-in confirmation heading. Publish your chosen copy on a page you control, then use "Redirect URL after booking" under "Booking page" and "After booking" to send guests there.


Test both states. The confirmation component can redirect pending requests as well as confirmed appointments, so a generic destination must avoid telling every visitor that approval has already happened. For a post-booking destination, [set up the redirect](https://meet.barq.dev/guides/redirect-after-booking) without treating a page visit as verified payment or appointment state.


1. Publish your destination with status-neutral wording or verified booking status.
2. Open the event's "Booking page" section, then "After booking".
3. Enter the destination in "Redirect URL after booking".
4. Make a test booking and check the page and received email.


We offer "Pass booking details to redirect", but it doesn't turn bracketed writing prompts into automatic page content. Leave it off for a generic thank-you page that doesn't need guest data.


## How does the confirmation page change the follow-up email?

A confirmation page can carry fuller preparation instructions while the email keeps the appointment details and change links close at hand. A booking link belongs in the earlier invitation that asks someone to choose a slot; after booking, link to the preparation page instead of sending them back to time selection.


Keep the actions distinct. "Choose a time" in an invitation becomes "Read the preparation notes" in the confirmation, while the joining link remains the route for attending the booked appointment.


Use the [pre-meeting questions guide](https://meet.barq.dev/guides/ask-questions-before-a-meeting) for information you need before confirmation. Don't move essential eligibility questions to a thank-you page after the guest has already made a commitment.


We let hosts edit confirmation email content under "Notifications". Booking emails go through the platform with Reply-To set to the host; changing the destination page doesn't change the sender or add an SMS message.


Review [the available booking and email controls](https://meet.barq.dev/pricing), then [create a booking with a clear next step](https://meet.barq.dev/app/sign-in).

## Frequently asked questions

### Should I ask someone to book again on the thank-you page?

Keep the current appointment's details and next action first. Offer another booking only when there is a clear reason, such as a separate follow-up; an unexplained second booking button can make a guest doubt whether the first attempt succeeded. Give the guest the next practical step for their existing appointment, such as checking the joining details, instead of creating another invitation to reserve a second time unnecessarily.

### Can I say the confirmation email has arrived?

Say it is on its way unless you know it has been delivered. A booking success screen and email delivery are different events; give a monitored contact route for missing messages instead of telling every guest to submit the form again.

### Do square-bracket placeholders fill themselves on a redirect page?

No. The brackets in these templates are writing prompts, not a connection to live booking data. Replace them yourself or build a page that receives and validates the required details; otherwise use generic wording that stays accurate for every visitor.

## Related pages

- [Booking pages that ask the questions you need answered](https://meet.barq.dev/features/booking-pages)
- [How to ask guests questions before a meeting](https://meet.barq.dev/guides/ask-questions-before-a-meeting)
- [Free scheduling, with every feature included](https://meet.barq.dev/pricing)
- [What is an intake form?](https://meet.barq.dev/glossary/intake-form)
- [Availability message examples for any channel](https://meet.barq.dev/templates/availability-message-examples)
- [How to send guests to a thank-you page after booking](https://meet.barq.dev/guides/redirect-after-booking)

[Create your free booking link](https://meet.barq.dev/app/sign-in)
