Event Templates

If you run the same kind of event over and over — a monthly meetup, a recurring workshop, a yearly conference — you don't want to re-enter the same ticket types, add-ons and custom form fields every time. An Event Template is a reusable blueprint: you capture an event's setup once, then spin up new events from it in a few clicks.

A template stores three things:

• Event details and settings — category, host, venue, medium, description, banner, time zone, ticket-email and sponsorship-deck settings, payment gateways.
• Ticket types — title, price, currency, capacity and publish settings.
• Add-ons and custom form fields — copied so the new event starts with the same booking options and questions.

You need the Event Manager (or System Manager) role to create templates and to create events from them.

How templating works

There are two directions, and you'll usually use both:

When you save an event as a template, its ticket types, add-ons and custom fields are snapshotted into child tables on the template. When you later create an event from that template, those snapshots are turned back into real linked records (Event Ticket Type, Ticket Add-on and Buzz Custom Field) tied to the new event.

Create a template from an existing event

The easiest way to build a template is from an event you've already configured.

1. Open the source event in Desk (Buzz Event list, then the event).

2. Click Actions > Save as Template.

3. Give the template a Template Name (it defaults to "<event title> Template").

4. Under Select What to Include, tick the parts you want to capture:

   • Event Details — category, host, banner, description, medium, venue, guest-booking settings, time zone.
   • Ticketing Settings — ticket-email, tax and print-format settings.
   • Sponsorship Settings — pitch-deck email settings and attachments.
   • Payment Gateways, Ticket Types, Add-ons, Custom Fields.

   Use Select all / Unselect all to toggle everything at once.

5. Click Save Template. Buzz creates the Event Template and opens it.

Only the boxes you tick are copied — anything left unticked is simply omitted from the template.

Build or edit a template by hand

You can also create a template directly: go to Event Template > New (/app/event-template/new) and fill it in.

• Template Name — required; how the template appears when you pick it later.
• Fill any of the event-detail, ticketing and sponsorship fields you want carried over to new events.
• Add rows to the child tables:
  • Ticket Types (Event Template Ticket Type) — title, price, currency, published flag, max tickets available, auto-unpublish-after date.
  • Add-ons (Event Template Add On) — title, price, currency, description, whether the attendee picks an option, the option list, and enabled flag.
  • Custom Fields (Event Template Custom Field) — label, field name, field type (Data, Phone, Email, Select, Date, Number), options, whether it applies to the Booking or each Ticket, mandatory/enabled flags, placeholder, default value and display order.

Editing a template never affects events already created from it — a template is a starting point, not a live link.

Create an event from a template

1. Go to the Buzz Event list.
2. Click Create from Template (top-right; visible if you can read templates).
3. Select Template — pick the template to use.
4. If the template is missing any field that's mandatory on an event (notably Category and Host), the dialog shows a Required Fields section — fill those in.
5. Under Select What to Copy, tick the settings, ticket types, add-ons and custom fields you want this event to start with.
6. Click Create Event.

Buzz creates a new Buzz Event and opens it. The new event is a normal draft you then finish off — set its real title, dates and times before publishing.

What the new event starts with: it's named "New Event from <template>", dated today, 09:00–18:00, with the copied settings applied. The template's ticket types, add-ons and custom fields are created as real records linked to the new event. Adjust the title, dates and any details, then publish as usual — see Create an Event.

Tips

• A template only copies what you tick — keep a "full" template for your flagship event and lean ones for quick meetups.
• Mandatory event fields not stored on the template (Category, Host) are asked for at create time, so a partial template still works.
• Templates are independent snapshots: changing prices on a template won't change any existing event, and vice-versa.