Ticket notices
The Ticket notices tab lets visitors ask to be emailed when tickets are available again, or when a scheduled sale opens. It belongs to the date selected in the event header — not to the event as a whole, and not to a create-event wizard step.
A notice is not a reservation. It does not hold stock, skip the line, or guarantee a ticket.
Where to find it: Events → [your event] → Ticket notices
Need a website first? The signup form lives on the public event page. If the brand has no site, the tab tells you to create one before you can collect signups.
Two independent promises
The tab has two cards. You can use one, both, or neither.
| Card | What it does | How you turn it on |
|---|---|---|
| Notify when tickets are available | When the date has nothing left to buy, the event page shows Notify me when tickets are available. Visitors leave their email and join the list. | Switch on the card |
| Schedule the sale opening | Set the date and time tickets go on sale for this function. Until then, the event page can show a countdown and collect Notify me first emails. | Set date and time — there is no on/off switch |
The availability switch has no On/Off label: the card title is the control.
Schedule the sale opening
This writes the same public start date as the Tickets tab. There is one schedule, not two.
| Control | What it does |
|---|---|
| Set date and time | Opens the scheduler. Field label is Start date. Confirm with Save opening. |
| Edit date and time | Change an existing opening |
| Remove schedule | Clears the opening. Tickets become purchasable as soon as they are published |
When an opening is saved you see Scheduled opening and Tickets go on sale on [date]. When there is none, No opening scheduled and: tickets are on sale as soon as they are published.
Rules:
- The moment must be in the future and before the function starts. You cannot schedule an opening after the date has begun.
- If the date's tickets currently open at different times, saving here replaces that stagger with one opening for all of them. The dialog warns you first.
Email templates
Each card has its own template. Deleting a custom template returns that card to Fanz default announcement.
| Status | Actions |
|---|---|
| Currently using default template | Preview email, Create template |
| Currently using custom template | Preview email, Edit, Delete |
Create template / Edit opens the same visual Email builder used in Communications. Preview uses the real delivery width (not a clipped desktop canvas), so the button looks like it does on a phone.
The event button in a notice email is unique per recipient and per function. If you omit that button, Fanz appends it so every notice still has a working link.
Leaving the waitlist uses the same public preferences page as a marketing unsubscribe. It only removes that person from this date's notices. It does not opt them out of marketing campaigns.
Notify now
When tickets are on sale, people are still waiting, and no send is already queued, a banner appears:
There are tickets on sale and N people who were never told.
Notify now opens Send a ticket availability notice. Confirm with Send notice. The toast is Ticket notice sent — N emails queued.
A send is not instant for the whole list: emails are queued.
The same prompt can appear after you save tickets that go from unsellable to sellable: Tickets are now available / N subscribers are waiting. Do you want to notify them now?
Where visitors see it
On the event page ticket area — not inside checkout.
| Situation | What buyers see |
|---|---|
| Sold out | SOLD OUT, then the option to be notified when stock returns |
| Sale not open yet | Live countdown and Notify me first / Avisame primero |
| Tickets on sale | Normal buy flow. Notice signup is hidden |
Copy for each option can be customized from the matching card.
Metrics and the people list
When someone has signed up, the tab shows four cards:
| Card | Meaning |
|---|---|
| Signed up for this date | People on the list for the selected date |
| Ticket notices sent | Notices already sent |
| Pending notice | Still waiting to be told |
| Conversion from notices | Percentage, plus N attributed purchases |
Below the cards: Signups over time (from the notice's creation through today).
People on the notice list
Search is available. Columns:
| Column | What it shows |
|---|---|
| Contact | Name, email, and phone when they left one |
| Registered | When they signed up |
| Result | One chip: Not notified yet, Notice sent, or Purchased via notice |
There is no “requested ticket” column and no demand-ticket count on this tab.
Empty state: Nobody has signed up for ticket notices yet.
Opens, clicks, and full recipient detail live in the regular email analytics for that send — not as extra columns here. Attributed revenue from notices can also appear on the Home Marketing AI widget.
Discovery from Tickets
If the selected date has a future opening, notices are still off, and the brand can send email, the Tickets tab can show a nudge: the sale has not opened yet, and Ticket notices takes you here. The nudge does not configure anything by itself.
FAQs
No. People ask to be told. They still buy like everyone else when tickets are on sale. The event tab is labeled Ticket notices, not Waitlist.
No. It follows the date in the header picker. Configure each function separately.
Tickets become purchasable immediately. People already on the list stay there until you notify them or they leave.
On each card: Create template or Edit. That is the visual email builder, not a second editor inside Notify now.
No. They leave this date's notice list only. Marketing opt-out is a separate confirmation on the same style of preferences page.
Tickets must be purchasable, at least one person must be unnotified, and no send can already be in flight for them.