Setting Default Ticket Types

Defaults decide which ticket type gets attached to a guest when nobody picks one manually. Set them once and incoming requests sort themselves.

What a default does

When a guestlist request comes in online and auto approval is on, the guest is automatically assigned the default ticket type. When you approve requests manually, the default is the first option prompted, so approving is one tap instead of a decision every time.

Every guest needs a ticket type, so the default is what keeps requests flowing without your team touching each one.

Venue defaults

Each venue can have its own default ticket type. This is the fallback for everything at that venue and the setting most organisers only touch once.

A good venue default is whatever your standard guestlist entry is. For most venues that is your standard guestlist ticket type.

Event defaults

Each event can override the venue default. When you create an event and choose which ticket types it runs, you can mark one as the default for that night.

This is useful when a specific event runs different pricing to your usual week. A ticketed special event might default to a paid ticket type, while your regular Saturday stays on the venue default.

You can select an event default ticket type in the tickets section in manage event

How the two work together

The event default always wins. If an event has no default set, the venue default applies. Requests for that event follow whichever is active.

Where to set them

• Venue default: set when assigning venues to a ticket type in Products → Ticket Types

• Event default: set when choosing ticket types during event creation, or by editing the event