Form templates

SalesMarketing

A form template is a complete booking form — the contact fields, the custom questions, and the multi-step layout — saved at workspace level so you can apply it to any event type in one click. Templates are managed by workspace owners and admins under Settings → Form templates.

Creating a template

There are two ways:

  • From an event type. On the event's Form screen click Save as template. The form is saved exactly as it is right now — unsaved edits included — and the event is marked as using that template.
  • From scratch. Under Settings → Form templates click New template. You get the same form builder as the event editor, plus a live preview rendered on one of your booking pages.

Give the template a name (unique per workspace) and, optionally, a description that helps your team pick the right one later.

Applying a template

On any event type's Form screen click Apply template, pick one from the list — the preview shows it on that very event — and confirm. Applying replaces the event's contact fields, questions and steps. Nothing is saved yet: review the result, and press Save in the editor when you're happy (or discard to keep the old form).

If the event already had saved questions, Preb shows you exactly what the replacement affects before you confirm:

  • which saved questions disappear,
  • how many disqualification or routing rules refer to a removed question and will no longer match,
  • that CRM field mappings pointing at removed questions stop syncing until you map the new questions.

Copy, not link

Applying a template makes a copy. Editing the questions in the event never changes the template, and editing the template never changes events that already use it — each event keeps a small "From template …" note so you know where its form came from. Deleting a template only removes that note.

Editing, duplicating, deleting

From the templates list you can open a template in the editor, duplicate it as a starting point for a variant, or delete it. Question identifiers already in a template stay fixed (they may already be referenced by answers and CRM mappings in events that used the template).