Booking site settings

Booking site settings is where you design the public booking pages your customers use to browse events and reserve slots. You can run multiple templates from a single account, each with its own URL, styling, event list, checkout configuration, and confirmation experience. One template is marked as your main template and is served at your base booking URL.

Getting started

Navigate to Bookings > Booking site settings from the sidebar. You'll see a list of your templates. Click a row to edit, or click Create new template to start fresh.

How it works

A template is a self-contained booking page with its own URL slug, visual styling, event selection, customer-info fields, payment rules, checkout rules, and confirmation experience. One Save changes button in the editor footer saves every section at once; the footer reads All changes saved or Unsaved changes so you always know where you stand.

Templates have two tabs:

• Publish: URL slug, main-template toggle, embed code
• Content: seven sections in a left-column nav covering everything the customer sees on the page

Custom fields (checkboxes, text inputs, dropdowns) are defined once in the central library at Settings > Custom fields, then attached to each template from the Customer info section. Each attachment carries its own per-venue toggles for Required, Requires user interaction, and Creates alert — so the same field can be required at one venue and optional at another. Updating a field's label, type, or options in the library still applies to every template it's linked to.

Reference

Template list columns (Active tab)

Switch to the Archived tab to see deactivated templates. Archived rows have a single Restore action.

Template list actions (three-dot menu)

In the Archived tab, the only action is Restore, which returns the template to the active list.

Publish tab

Content tab sections

The Content tab has seven sections, selectable via the left-column section nav:

1. General settings — header, colors, typography, logo
2. Event selection — layout, events list, display options
3. Availability & time slots — calendar defaults, availability behavior, slot display and messages
4. Event details — event detail page configuration
5. Customer info — built-in standard fields (name, email, phone, address) plus custom fields that appear during checkout
6. Checkout & payment — pay on arrival and payment methods, promo codes, event upsell, deposit presentation, cart timeouts
7. Confirmation — post-booking messages and redirect

One Save changes button in the editor footer saves every section at once. A live schematic preview on the right of the editor updates as you adjust the currently-active section.

Section 1 — General settings

Five cards:

Header

Page colors, Card colors, and Typography

A shared color-palette layout (also used by the Payment pages editor), split into three cards. Each color field has a preset swatch row, an editable hex input, and a custom color picker.

Input border controls the border color on every text-entry control customers see: text inputs, dropdowns, promo code and tip fields, and card payment forms. It applies across the booking page, the check-in page, the waiver page (when reached from this template), the shareable waiver link, and the payment page. Date-picker fields keep a fixed neutral border and don't follow this setting. The default is a neutral gray (#7d7d7d99) that stays readable on both dark and light backgrounds, so the field borders are visible out of the box even if you never touch this control.

A Reset colors to defaults link at the bottom of the Card colors card restores every color in the palette to the platform defaults.

Logo

Section 2 — Event selection

Three cards:

Layout

Pick Cards (grid) or List (board style). For list layout, configure image size and position.

Events

Event display

When Show event description before time selection is on, more fields appear to control the trigger's look and position:

The schematic preview reflects the trigger's position on both card and list layouts as you change settings.

Customer-side behavior:

Section 3 — Availability & time slots

Two cards, moved here from Event selection:

Availability

Time slots

When Show booking deadline countdown is on, customers see a banner directly under the progress bar reading "Slot will become unavailable in MM:SS minutes. Complete your booking now to secure the slot," with the timer ticking in real time. The banner follows them through every step (booking details, customer info, payment) and disappears the moment they reach the confirmation screen. When the cart has more than one slot, the countdown reflects whichever slot closes first. The banner inherits the template's colors and font and is translated into every language the booking site supports.

Section 4 — Event details

Two cards:

Pricing

Add ons

Controls the header and description shown above the add-on items on the booking details step of the customer checkout. Info hint verbatim: "Shown above the add-on items on the booking details step. Customers only see this section when the selected event has add-ons for sale. Leave a field empty to hide it. You can use [Company Name] and [Company Group Name] as placeholders."

Both fields accept the [Company Name] and [Company Group Name] placeholders and are replaced with the real names at checkout. The schematic preview at the right of the template editor updates as you type, so you can see how the header and description read before saving. When the selected event has no add-ons for sale, neither field renders and the customer sees the checkout exactly as they did before. Templates that leave both fields empty look and behave exactly as they did before this setting shipped.

Duplicating a template copies both fields to the new copy.

Section 5 — Customer info

Two cards: Standard fields and Custom fields.

Standard fields

The built-in customer details collected at checkout. The card help text reads: "Choose which details customers provide on the customer info step. Collected values are saved to the customer's profile."

The booking site's customer info step renders only the fields you've set to Optional or Required, with country-correct labels (e.g., "Postcode" for UK venues) and the customer's country pre-selected to match the venue. The live preview reflects each change as you make it.

Form layout adapts automatically. When Phone is Hidden, the Email field grows to full width. When Phone is shown alongside the zip-only address option, Zip and Phone share a row.

Where collected values go. Customer-provided values save straight to the customer's profile — both the company's customer record and the customer's master record on first creation. Repeat bookings update only the company record, and only with newly provided values; blank fields never overwrite data the customer gave you previously.

Safe defaults for existing templates. Templates that existed before this feature shipped keep their prior behavior: Phone stays Required; Zip and Address stay off. You opt in when you're ready.

Custom fields

Active custom fields render as a draggable list of cards (same style as the waiver editor). Each card carries its own per-venue behavior toggles so the same library field can be configured differently for each booking site template.

The toggles save in place — flip a switch and the new value persists on refresh. No modal confirmations; toast notifications confirm each change.

To create or edit the field itself (label, type, options), go to Settings > Custom fields. The Required, Requires user interaction, and Creates alert behaviors are no longer in the central library — they live on each venue's attachment of the field.

Section 6 — Checkout & payment

Five cards:

Payments

Decides whether customers on this page pay online, at the venue, or either, and which payment methods the page offers. The methods themselves are managed in the catalog on Purchases > Payment settings under the Payment methods tab; this card picks which of them this page uses.

A new template shows "Save the template first, then link the payment methods customers can use on this page." in place of the list until it is created. When gift cards are enabled on the template and no card method is linked, the card warns: "Gift cards are enabled on this page but no card method is linked, so customers cannot buy gift cards here."

Promo codes

Event upsell

Suggests other events to customers who already have a booking in their cart. When it is on, an upsell card appears on the Your information and Payment steps of the booking site. The card lists up to three other events from the same template, each with up to three bookable times on the same day as the customer's booking.

How suggestions are chosen:

Selecting a time opens the ticket step for that event. The customer picks tickets as usual, and the booking joins the same cart.

Deposits

Controls how the deposit choice appears at the payment step of checkout. The card help text reads: "Controls how the deposit choice appears at checkout. Customers only see deposit options when deposits are enabled for the event or booking slot. Checkbox shows a single 'pay deposit' checkbox (classic), buttons shows 'pay in full' and 'pay deposit' side by side, and stacked cards shows two full-width options with amount breakdowns."

The deposit money logic itself doesn't change — the same amounts are charged and the same per-event and per-slot rules apply (configured in Event pricing and deposits). This setting only controls how the choice is presented.

Special cases:

Cart & timeouts

The Add another booking button section is temporarily unavailable while being rebuilt. It will return in a future release.

Section 7 — Confirmation

Two cards:

Messages

Redirect & links

Step-by-step guide

Create a template

1. Open Bookings > Booking site settings
2. Click Create new template
3. The editor opens; go to the Publish tab
4. Enter Template name, optional Description, and set a URL slug
5. Click Create template in the footer
6. Go to Content > Checkout & payment and link at least one method under Payment methods on this page, or set Pay on arrival to Optional or Required, before you activate the template

A new template starts with Pay on arrival set to Off and no payment methods linked.

Configure the Content tab

1. Go to the Content tab
2. Click each section in the left-column nav in order (General settings → Event selection → Availability & time slots → Event details → Customer info → Checkout & payment → Confirmation)
3. Update the fields in each card
4. Click Save changes in the footer; the footer reads Unsaved changes until you do and All changes saved afterwards

The schematic preview on the right reflects your current section's settings.

Set pay on arrival and payment methods

1. Open the template and go to the Content tab
2. Click Checkout & payment in the left-column nav
3. In the Payments card, pick a Pay on arrival mode: Off (every booking is paid online), Optional (customers choose between paying online and paying at the venue), or Required (every event booking is paid at the venue, with no payment step)
4. Optional: turn on Show custom pay on arrival text and enter the label customers see in Pay on arrival text
5. Under Payment methods on this page, click Add method to link each method customers can use, and drag the rows into the order they should appear
6. Pick Dropdown or Buttons under Payment method layout
7. Click Save changes

With Pay on arrival set to Off, the template needs at least one linked method before it saves. Otherwise the save stops with "Link at least one payment method in the Payments section, or allow pay on arrival on this page".

Tip: To run a booking page that only takes payment at the venue and a gift card page that takes cards, create two templates: set the booking template to Required, and link Card on the gift card template.

Choose where the promo code field appears

1. Open the template and go to the Content tab
2. Click Checkout & payment in the left-column nav
3. In the Promo codes card, make sure Show promo code field is on
4. Under Show the promo code field on, choose Every checkout step or Final step only
5. Click Save changes

The preview on the right follows your choice: with Final step only, the promo code field leaves the Customer info preview step and stays on Checkout & payment.

Tip: If customers enter gift card codes in the promo code field and get an error, choose Final step only. The promo code field then sits on the Payment step, where the gift card payment option is also available.

Suggest other events at checkout

1. Open the template and go to the Content tab
2. Click Checkout & payment in the left-column nav
3. In the Event upsell card, turn on Suggest other events at checkout
4. Enter a Section title and Section text, or leave them empty to use the default wording
5. Pick a Position: Above the form, Below the form, or Below the summary
6. Optional: choose a Discount promo code and enter the Discount badge text customers see on each suggested event
7. Click Save changes

The page preview on the right shows the upsell card in the position you picked.

Tip: To reward a second booking, first create a promo code with a Buy X Get Y eligibility rule under Purchases > Promo codes, then select it here. See Promo code eligibility rules for how to set the rule up.

Configure which standard customer fields to collect

1. Open the template editor and go to the Content tab
2. Click Customer info in the left-column section nav
3. In the Standard fields card, set each row's mode with the pill segmented toggle:

• Phone — Hidden, Optional, or Required
• Address — Hidden, Optional, or Required, with a Collects dropdown for Full address or Zip/postal code only

1. Name and Email stay locked as Always required; you can't hide or de-require them
2. Watch the schematic preview update to match
3. Click Save changes

Whatever customers enter at checkout saves to their customer profile (both your company's record and their master record on first creation). Repeat bookings only update fields the customer fills in again; blank fields don't overwrite earlier data.

Link custom fields to a template

1. Create or edit the field at Settings > Custom fields
2. Return to the template's Content > Customer info section
3. Use the + Add custom field dropdown to attach the field
4. Drag cards to reorder how fields appear on the booking form
5. Flip Required (or Requires user interaction for checkbox fields) on if the customer must fill it in to submit
6. Flip Creates alert on if you want responses to surface as a warning icon on the calendar and booking drawer
7. Remove a field from this template by clicking the X on the card

Toggles save in place per template; switching them on one venue does not affect any other venue. Field label, type, and options are still updated in the library and apply to every template the field is linked to.

Activate a template

1. On the template list, open the three-dot menu on the template
2. Click Activate
3. If no payment gateway is configured, activation is blocked with an error. Configure your gateway first in Settings, then retry
4. Make sure the template's Payments card links at least one method or allows pay on arrival, so customers can complete a booking

Set a template as the main one

1. On the template list, open the three-dot menu
2. Click Set as main
3. Confirm the prompt

The main template is served at your base booking URL. Other templates are reachable at the URL slug you set in the Publish tab.

Duplicate a template

1. On the template list, open the three-dot menu
2. Click Duplicate
3. The editor opens on the new copy, ready for changes

Archive and restore a template

1. On the template list, open the three-dot menu
2. Click Archive
3. The template moves to the Archived tab
4. In the Archived tab, open the three-dot menu on any row and click Restore to bring it back

Preview the live page

1. On the template list, open the three-dot menu
2. Click Go to booking site
3. The live public page opens in a new tab at the template's URL

Good to know

• Payment gateway is required before you can activate a template. If you try to activate without one, the action is blocked.
• Pay on arrival and payment methods are set per template. Each booking page decides on its own whether customers pay online, at the venue, or either, and which methods it offers. Changing one template never changes another.
• A template with Pay on arrival Off needs at least one linked method. The editor stops the save with "Link at least one payment method in the Payments section, or allow pay on arrival on this page". To remove the last method, switch the mode or add another method first.
• Required skips the payment step for event bookings. The booking completes as pay on arrival. Gift card purchases on the same page always charge online with one of the linked methods.
• Gift cards need a linked method. If gift cards are enabled on a template with no linked methods, customers see "Gift cards cannot be purchased on this page." and cannot continue. The editor warns: "Gift cards are enabled on this page but no card method is linked, so customers cannot buy gift cards here."
• A new template starts with Pay on arrival Off and no methods. Link methods in the Payments card before activating it.
• Duplicating a template copies its pay on arrival mode, custom text, and linked methods.
• Setting a new main template does not deactivate the previous main. You can keep multiple templates live; only one is served at the base URL.
• The Cards and List layouts affect how customers browse events. Cards is best for small event catalogs with strong imagery; List is better when you have many events and customers scan by name.
• Real-time availability updates is useful during high-traffic periods where multiple customers may be viewing the same slot.
• The schematic preview is a quick visual reference, not a pixel-perfect rendering. Use Go to booking site to see the real page.
• The booking page opens in your location's default language. Set the default under Settings > Company settings > your location > Locale and formatting. The language switcher only appears when Display language switcher is on for the template, and a customer's own language choice is remembered on their device for future visits. Text you author yourself (titles, custom messages, policies) is not translated automatically, so write it in the language your customers should see.
• Custom fields are managed once and reused everywhere. If you need the same field with different visibility per template, create separate fields for each scenario.
• Use Standard fields for built-in customer details, not custom fields. If you need a zip code, address, or phone number, the Standard fields card collects them and writes them straight to the customer's profile — searchable, reportable, and reusable across visits. Custom fields are for venue-specific questions that don't belong on a profile.
• Hidden phone affects more than checkout. If Phone is set to Hidden, customers who don't already have a phone on file won't get SMS reminders, and your staff won't have a fallback number for callbacks. Lean toward Optional unless there's a strong reason to hide it.
• Address-only-as-zip is the common case. Most venues that want a postal code don't actually need a full address; pick Zip/postal code only to keep the form short while still capturing what you need.
• Card payments capture a postal code even when Address is Hidden. Stripe, Square, and Authorize.net card forms ask for a postal code once a card from a country that uses them is entered, and that value is saved to the customer's profile after payment. If the template also collects a zip or address, the value typed into the booking form wins.
• Country-correct labels are automatic. The booking site relabels "Zip" as "Postcode" in the UK and adjusts city/state labels to match. The dropdown also pre-selects the venue's country for the customer.
• Defaults preserve old templates. Existing templates keep their prior behavior (Phone Required, Zip and Address off) until you open the editor and change them. Nothing breaks until you opt in.
• Event description before time selection is off by default, so existing templates render unchanged until you flip it on. The trigger is per template — duplicating a template carries the setting (and the chosen icon or text) with it.
• The trigger shows the Booking page highlight, not the full Event description. Set the highlight on each event's Event details tab (Events > Event setup) for a short, punchy teaser that reads cleanly on the booking page. Leave it blank to fall back to the full description, which is what existing events do automatically.
• The trigger corner is configurable. If your event artwork puts badges, logos, or names in a specific corner, use the Location picker (Cards layout) to send the trigger to a clear corner instead. Defaults to bottom right so existing templates render exactly as before until you change it.
• Events with neither field never show the trigger. If a player only sees the trigger on some events, the rest are missing both a highlight and a description. Add at least one of those on the event itself and it picks up automatically.
• The description matches your site theme. The flip card (on Cards layout) and full-width expansion (on List layout) inherit your booking site's colors, typography, and shadows, so it reads as part of the page rather than a generic popup.
• Reduced-motion preferences are respected. Players who have reduced motion turned on see the description appear without the flip animation. Accessibility labels are translated across 5 languages for screen readers.
• Deposit layouts only change presentation. The amounts charged and the deposit rules per event / slot live in Event pricing and deposits and don't change when you pick Buttons or Stacked cards. The new layouts just make the choice clearer to customers; Checkbox keeps the prior look exactly.
• The deposit description is a single language. It renders verbatim in whatever you wrote. Fixed labels (like "pay in full" and "pay deposit") are translated automatically into English, Spanish, French, Swedish, Greek, and Danish. If you serve customers in a language you don't speak, lean on the translated labels rather than relying on the custom description.
• Stacked cards work well when there's a meaningful gap between deposit and full price. When the deposit is a small percentage of the total (e.g., 20%), the cards make the choice obvious. When the deposit is close to the total, Buttons reads cleaner; if the deposit equals the total because of a promo, both layouts hide the choice entirely.
• Booking deadline countdown is off by default and opt-in per template. Brands that prefer not to show urgency timers can leave it off. When on, the banner only appears once a slot in the cart is within the configured window — most customers never see it, since most book well before the cutoff.
• The countdown is a nudge, not the final word. The booking site re-checks availability at submit time, so a customer who races the timer can still hit a real "slot unavailable" error if they miss the deadline. The banner just reduces how often that happens by warning them sooner.
• Multi-cart countdowns reflect the soonest deadline. If a customer's cart has more than one slot, the banner ticks down for whichever one closes first; the other slots' deadlines are checked at submission as usual.
• Late-booking slots aren't included in this version. The countdown is built around the standard minimum-booking-notice cutoff. Slots configured to allow late booking (book past the start) don't trigger the banner today.
• Countdown window (minutes) tunes how aggressive the banner is. Set it small (e.g., 5) and the banner only appears on the truly last-minute bookings — fewer customers see it. Set it large (e.g., 30 or 60) and customers see it earlier — useful for venues with longer booking forms. 15 minutes is the default.
• The promo code field position is set per template. Each template keeps its own choice, and duplicating a template copies it.
• Final step only follows the step that completes the booking. This is usually the Payment step. When there is nothing to pay or the template requires pay on arrival, the booking is completed on the Your information step, so the promo code field appears there.
• Applied promo codes stay visible on every step. A code that is already applied is listed in the order summary with its remove button on both steps, whichever position you choose.
• Event upsell is off by default and set per template. Existing templates look the same until you turn it on. Duplicating a template copies the upsell settings with it.
• The upsell card only appears when there is something to suggest. If no other event on the template has a bookable, non-overlapping time that day, the card is not shown.
• The discount promo code is applied for the customer. It is added when a suggested event joins the cart and removed again if the cart stops qualifying, for example when the customer removes one of the bookings.
• Link a promo code whose rules require a second event. The code works like any other promo code, so a customer who learns it could type it in. A Buy X Get Y rule keeps the discount tied to booking two events.
• Archived and internal only promo codes are not applied. If the linked code is archived later, the editor marks it as archived and the booking site stops applying it.
• The Add another booking button is currently unavailable in the editor while being rebuilt. Existing booking sites still show the default behavior.
• Add-on section header and description are per template. Each booking site template carries its own copy, so a "Group experiences" template and a "Private events" template can frame the add-on step differently. Duplicating a template copies both fields to the copy.
• Both fields are optional and default to empty. Templates created before this setting shipped, and any new template you skip past, look and behave exactly as they did before: no header, no description, straight to the add-on items.
• The section only renders when there are add-ons for sale. Events with no add-ons show nothing in this area of checkout, regardless of what you've typed. Nothing to hide by hand.
• [Company Name] and [Company Group Name] are supported in both fields. Use them to keep a template neutral across a multi-location group; each location's real name is substituted at checkout.

FAQ

Q: How do I let customers pay at the venue instead of online?

A: Open the template's Content > Checkout & payment section and set Pay on arrival in the Payments card to Optional (customers choose) or Required (every event booking on this page is paid at the venue, with no payment step). Save changes.

Q: Customers on my gift card page see "Gift cards cannot be purchased on this page." What do I do?

A: That page has no payment method linked. Gift cards are always paid online, even when pay on arrival is Required. Open the template's Payments card, click Add method, link Card, and save.

Q: Why won't my template save after I removed a payment method?

A: With Pay on arrival set to Off, the page needs at least one linked method. Add another method, or set Pay on arrival to Optional or Required, then save.

Q: Can one template take pay on arrival only and another take cards?

A: Yes. Set Pay on arrival to Required on the booking template and link Card on the other template. Each template has its own mode and method list.

Q: Where do I create a new payment method?

A: In the catalog on Purchases > Payment settings, under the Payment methods tab. Once it exists, link it to each template that should offer it from the template's Payments card.

Q: How do I add a custom header above the add-on items at checkout?

A: Open the template's Content > Event details section and expand the Add ons card. Fill in Add-on section header (up to 255 characters) for the heading, and optionally Add-on section description (up to 500 characters) for a short intro line under it. Save changes. On the customer checkout, the header and description appear above the add-on items whenever the selected event has add-ons for sale. Leave a field empty to hide it.

Q: Can I use the venue name inside the add-on section header or description?

A: Yes. Both fields accept the [Company Name] and [Company Group Name] placeholders and swap in the real names at checkout. This is useful when the same template serves several locations.

Q: My checkout looks the same after saving an add-on header. Why?

A: The section only renders when the selected event has add-ons for sale. Confirm the event has active add-on items attached. If it does and the header still doesn't appear, refresh the booking site (the page caches briefly after a template save) and try again.

Q: Customers are typing gift card codes into the promo code field. How do I prevent that?

A: Open the template's Content > Checkout & payment section, and in the Promo codes card set Show the promo code field on to Final step only. The promo code field then appears on the Payment step, alongside the gift card payment option.

Q: I chose Final step only. Why does the promo code field still show on the Your information step?

A: That happens when the booking is completed on that step: the cart has nothing to pay, or the template requires pay on arrival. In those cases there is no Payment step, so the field stays where the customer finishes the booking.

Q: How do I suggest another event to customers during checkout?

A: Open the template's Content > Checkout & payment section, and in the Event upsell card turn on Suggest other events at checkout. Customers with a booking in their cart then see other events from the same template with times they can book on the same day.

Q: Why is the upsell card not showing on my booking site?

A: The card only appears when another event on the same template has a bookable time on the same day that does not overlap the customer's booking. Check that the template has more than one active event and that the other events have available slots that day.

Q: Can I offer a discount on the second event?

A: Yes. Create a promo code with a Buy X Get Y eligibility rule, then select it under Discount promo code in the Event upsell section. The code is applied automatically when a customer adds a suggested event.

Q: How many templates can I have?

A: There's no fixed limit. Create one per audience, campaign, or event type. Each has its own URL slug.

Q: Can I embed the booking page on my website?

A: Yes. On the Publish tab, copy the embed code and paste it into your site's HTML.

Q: How do I add a custom field to a template?

A: Create the field once at Settings > Custom fields, then attach it from the template's Content > Customer info section using the + Add custom field dropdown. The same field can be linked to any number of templates, with different Required and Creates alert settings per venue.

Q: How do I require a zip code at checkout without making a custom field for it?

A: Open the template's Content > Customer info section. In the Standard fields card, set Address to Required and pick Zip/postal code only in the Collects dropdown. The zip lands on the customer's profile (no custom field needed) and is available across reports, searches, and future visits.

Q: Do I need the Address field to capture zip codes for card payments?

A: No. The postal code entered in the card form is saved to the customer's profile on its own. The Address field is for collecting a zip or full address regardless of payment method, for example on pay-on-arrival bookings, and it takes priority over the card form value when both are present.

Q: Where do the values customers type at checkout actually save?

A: The Standard fields' values save to the customer's profile — both your company's customer record (used for your venue's reports and history) and the customer's master record on first creation. Repeat bookings only update what the customer fills in; leaving a field blank on a return visit doesn't erase what they gave you before.

Q: I hid Phone but a customer's record still shows a phone number.

A: Existing data is preserved. Hiding a Standard field just stops the booking site from asking for it. If the customer's profile already has a phone (from a prior booking or admin entry), it stays. If you want it removed, edit the customer record directly.

Q: My booking page already worked the way I wanted. Will this change anything?

A: No. Existing templates keep their prior behavior: Phone Required, Zip and Address off. Standard fields is opt-in; nothing changes until you open the template editor and configure the card.

Q: Will customers in different countries see different labels?

A: Yes. The booking site adjusts the address labels to the venue's country (for example, "Postcode" in the UK), and pre-selects the country dropdown for the customer. In non-English locales the address labels currently display in English; field translations cover English, Spanish, French, Swedish, and Greek.

Q: How do custom field alerts work?

A: Each attached field has its own Creates alert toggle on its card. When on, the customer's response triggers a warning icon on the booking calendar, resource calendar, kanban view, and inside the booking drawer. Use it for special requests, accessibility needs, or anything staff should review on sight. The alert state is captured as a snapshot at the time of booking — changing the toggle later only affects new bookings, not historical ones.

Q: Can I make the same custom field required at one venue and optional at another?

A: Yes. The Required, Requires user interaction, and Creates alert toggles live on each venue's attachment of the field, not on the field itself. Flip them differently per template; the library field is shared but the behavior is per-venue.

Q: A customer ticked-required checkbox stopped enforcing on my booking site. What changed?

A: That was a known bug — checkbox fields with Requires user interaction turned on weren't blocking submission. It's been fixed. Required checkboxes now show the red asterisk and block submission until the customer ticks them. If you had a previously-required checkbox that silently stopped enforcing, re-toggle Requires user interaction on for that field on the template.

Q: My booking site shows "Last Slot!" next to a SOLD OUT label. Can I clean that up?

A: Yes. In Content > Availability & time slots > Time slots, turn on Hide custom slot messages on sold out slots. Any custom message on a slot is then hidden the moment that slot sells out. Only sold out slots are affected — messages on blocked and call-to-book slots stay visible (so notices like "Closed for Christmas" on a manually blocked slot are unaffected).

Q: What happens if I archive my main template?

A: Your base booking URL will show no active template until you set another as main. Set a new main template before archiving the current one.

Q: Why can I not activate my template?

A: Activation requires a configured payment gateway. Set up your gateway in Settings, then return and try again.

Q: Why is the "Add another booking" button section missing?

A: It's temporarily removed from the editor while being rebuilt. Existing templates continue to behave as configured until it returns.

Q: Which deposit layout should I pick?

A: Start with Stacked cards if customers regularly misread the classic checkbox as either mandatory or an extra charge — the cards spell out "due now" and "due later" explicitly. Pick Buttons for a faster, more compact look when customers already understand deposits. Stick with Checkbox if the existing flow works for your venue; nothing about how money is charged depends on the layout.

Q: My event requires a deposit. What do customers see?

A: With Buttons or Stacked cards, an informational line replaces the choice — it shows the amount due now and the amount due later, since there's no "pay in full" option to offer. With Checkbox, the classic prompt is hidden because there's no choice to make.

Q: Does the layout affect what the customer is actually charged?

A: No. The deposit amount and rules are unchanged. The layout only controls how the choice is presented. The same calculations, the same Stripe / Square / etc. authorization, and the same balance-due tracking apply regardless of which layout you pick.

Q: Can I write the deposit description in multiple languages?

A: Not directly — the description is a single textarea. The fixed labels around it ("pay in full", "pay deposit", "due now", "due later") translate automatically into English, Spanish, French, Swedish, Greek, and Danish; Arabic falls back to English. If you serve a multilingual audience, keep the custom description short and in the language most of your customers read, or lean on the translated fixed labels.

Q: Does duplicating a template carry the deposit layout and description?

A: Yes. Duplicate copies every setting including the deposit layout, the custom description toggle, and the description text. Edit the copy independently from there.

Q: How do I let customers read about an event before they pick a time?

A: In the template editor, open Content > Event selection > Event display and turn on Show event description before time selection. Pick a trigger style (an icon from the 13 curated options, or your own text like "Learn more" up to 30 characters). Customers then see a "learn more" trigger on each event — tapping it flips the card to show the description on the Cards layout, or expands it full-width under the row on the List layout. Events that don't have a description set on the event itself won't show the trigger.

Q: The "learn more" content reads too long. Where do I write a shorter version?

A: On the event itself. Open Events > Event setup, go to the Event details tab, and fill in the Booking page highlight field beside the existing Event description. The booking site's Learn more option uses the highlight when it's set, and falls back to the full description when it's blank. The full description still drives the checkout description card and step 2 of the booking flow, so you can keep that long and detailed.

Q: I turned on "Show event description before time selection" but the trigger is missing on some events.

A: Those events don't have either a Booking page highlight or an Event description filled in yet. The trigger only shows when there's something to read. Open the event in Events > Event setup, add either field (or both), and the trigger appears automatically — no template change needed.

Q: Can I pick a different icon or different text per event?

A: No. The icon (or custom text) is set per template, not per event. Every event with a description on the same template uses the same trigger style. If you need different presentations, create separate templates.

Q: The "learn more" trigger overlaps the badge / logo / event name on my event artwork. Can I move it?

A: Yes, on the Cards layout. With Show event description before time selection on, the Location picker offers all four corners (Top left, Top right, Bottom left, Bottom right). Pick the corner that doesn't collide with your artwork; the schematic preview updates immediately and the live booking site picks it up. On the List layout the trigger sits under the event details rather than over the image, so there's no overlap to worry about.

Q: Does the Location setting affect the List layout too?

A: No. The Location picker only appears when the template's layout is Cards. List layout shows the trigger beneath the event details (not on the image), so there's no corner to choose.

Q: Does duplicating a template carry the Location choice along?

A: Yes. The trigger style, custom text or icon, and the chosen Location all clone with the template.

Q: Does the description close when a customer picks a time?

A: On the Cards layout, the flip card stays open while the customer chooses a slot — the time slots remain visible alongside the description, and the close button on the card flips it back. On the List layout, the expansion can be tapped again to collapse it.

Q: Customers keep hitting "slot unavailable" right at checkout. How can I warn them earlier?

A: Turn on Show booking deadline countdown in Content > Availability & time slots > Availability. A live banner appears on the booking site as soon as a slot comes within your Countdown window (minutes) window of its minimum-booking-notice cutoff. The banner reads "Slot will become unavailable in MM:SS minutes. Complete your booking now to secure the slot" and follows the customer through every step, so they finish before the cutoff instead of being rejected at submit.

Q: When does the countdown banner appear on the booking site?

A: The banner only appears when a slot in the customer's cart is within the configured Countdown window (minutes) window (15 minutes by default) of its minimum-booking-notice cutoff. Customers who book well in advance never see it. If the cart has more than one slot, the banner counts down to whichever closes first.

Q: Will the countdown banner show on a slot that allows late booking past its start time?

A: Not in this version. The countdown is built around the standard minimum-booking-notice cutoff. Slots configured to allow late booking aren't included today.

Q: Does the countdown banner match my booking site's brand colors and fonts?

A: Yes. It inherits your template's colors and font automatically, and it's translated into every language the booking site supports.

Q: Does the countdown still block a customer if they miss the deadline?

A: Yes. The countdown is a friendly nudge; the booking site still checks availability when the customer submits, so missing the cutoff still rejects the booking. The countdown just gives customers a chance to finish before that happens.