Zum Hauptinhalt springen
War diese Seite hilfreich?

Customizing Booking Pages

Use this guide when you want the public booking experience to feel clear and intentional for customers before they submit a reservation.

Time to complete: 10-15 minutes
Difficulty: Intermediate

What Changed In The Booking Experience​

PrimeCal public booking pages now support a few quality-of-life behaviors automatically:

  • the language selector sits in the same header row as the organisation name
  • the Choose service selector is hidden when only one bookable service is available
  • the Booking summary card is visually emphasized so customers can review the important details quickly
  • when payment is optional, the customer can still finish the booking first and use a Pay now action from the success state afterward
  • success feedback is shown directly under the configuration area instead of floating above the whole page

Configure The Booking Page​

1. Decide how many services the customer should see​

If a booking page exposes only one active service, PrimeCal now selects it automatically and removes the extra selector box.

Use this when:

  • the page is for one room, one staff role, or one fixed paid offering
  • you want the shortest possible booking path

Keep multiple services on the same page only when the customer really needs to compare them.

2. Review the language selector placement​

The language selector appears in the header row next to the organisation identity.

This helps customers:

  • understand which organisation owns the page
  • change language before filling in any details
  • keep the booking flow consistent on mobile and desktop

3. Check the booking summary card​

The summary area highlights:

  • selected service
  • selected resource or Any available resource
  • slot and duration
  • payment state
  • total price when pricing is enabled

Before publishing the page, verify that the summary stays readable when:

  • the organisation language is changed
  • the service is free
  • payment is optional
  • payment is required

4. Decide between optional and required payment​

PrimeCal handles these cases differently:

  • Optional payment
    • the customer can submit the booking without Stripe checkout
    • after success, PrimeCal shows a Pay now action
  • Required payment
    • the reservation moves into the checkout path immediately
    • the customer must complete Stripe before the booking is fully confirmed

Use optional payment when you want:

  • deposit-free reservations
  • manual follow-up payments
  • a faster confirmation path for trusted customers

Use required payment when you need:

  • guaranteed prepayment
  • stronger no-show protection
  • automated checkout before confirmation

Best Practices​

  • Keep one booking page focused on one job. Do not mix unrelated services just because they belong to the same organisation.
  • Hide complexity whenever possible. A single-service page usually converts better than a page that forces an unnecessary extra choice.
  • Treat optional payment as a convenience feature, not a substitute for a clear billing policy.
  • Re-check the page on a narrow mobile viewport so the organisation badge and language selector wrap cleanly.

Validation Checklist​

Before you share the public link, confirm that:

  • the correct organisation name and branding appear in the header
  • the language selector works before submission
  • the summary card reflects service, slot, and pricing accurately
  • optional payment pages show Pay now only after a booking is created
  • required-payment pages still push the customer into secure checkout