frequentix
Help centre

How frequentix works, for the people running the event.

Orientation guides for every part of the platform — the organiser console, your public storefront, and the Scanner and Box Office apps at the door. Enough to know what to expect; the console itself guides each step.

Help menu

Arrival alerts: know when a VIP arrives

A sponsor, a speaker, a buyer your sales team has been courting: the people who should be met at the door are easy to miss in a queue. Arrival alerts email your team the moment such a guest is scanned in, and say which entry point they came through.

Where to find it: open your event, then On-site → Arrival alerts in the sidebar. The same switch is on each ticket type, and the per-guest flag is on the Tickets list and the order page.

Who gets told

The Arrival alerts page for the event Aurora Vaults — Live at The Foundry. A “Who to tell” card lists two recipients, promoter@frequentixdemo.test and vip-host@frequentixdemo.test, each with a remove button, then “Add a person”, “2 of 10” and a Save recipients button. Below it the “Who triggers an alert” card begins its list of ticket types, each with a switch: Members Night, Gold Membership and Standing (Floor), all off.
On-site → Arrival alerts — the people to tell, up to ten addresses, saved explicitly.

Each event has one list of people to tell — up to ten email addresses, typically the sales or hospitality team working that night. Everyone on the list gets every alert for the event, and each alert names the guest, their ticket type and their company, so a team of a few people can tell at a glance whose guest has arrived.

The list is saved on the event itself (not on a ticket type), so the door devices never carry it. Change it any time, including during the event: the next arrival goes to the new list.

What triggers an alert

The same page scrolled to the “Who triggers an alert” card. Seven ticket types each have a switch — Members Night, Gold Membership, Standing (Floor), Balcony Reserved, Box Seat, VIP Meet & Greet and Guest List — and only VIP Meet & Greet is on. Under “Individual attendees” it reads “3 attendees are flagged individually” with a See who link, and explains that flagging someone is done from the row’s menu on the Tickets list.
On-site → Arrival alerts — a switch per ticket type, and how many guests are flagged one by one.
  • A whole ticket type. Switch on arrival alerts for a type — VIP, Speaker, Press — and every holder of that type raises one. The switch is on the ticket type’s own form and, side by side for every type, on the Arrival alerts page.
  • An individual guest. Open Attendees → Tickets, find the person, and tick the Arrival alerts box in the row’s menu — it stays ticked while they are watched, and is ticked but locked when their ticket type already alerts. The same switch is on the order page, where it reads Alert on arrival. Flagged rows show an Alert on badge under the name, and the Alerts: on filter lists everyone being watched.
The edit panel for the VIP Meet & Greet ticket type, open over the Ticket types list and scrolled to its switches. Between “Requires approval” and “Offer wallet passes” sits a bordered “Arrival alerts” row reading “Email your team the moment anyone with this ticket is scanned in — once per guest, naming the entry point. Sending to 2 people.” with its switch on. Behind the panel, the VIP Meet & Greet row in the list carries an “Arrival alerts” badge.
Setup → Ticket types — the same switch on the type’s own form, saying how many people it currently reaches.
The event’s Tickets list with one row’s menu open. The menu lists View QR code, View badge, Download PDF, View scans, then “Arrival alerts” with an empty checkbox beside it, then Open contact and Open order. Further down the list, Jack Smith’s row carries an “Alert on” badge under his name.
Attendees → Tickets — ticking the “Arrival alerts” box in a guest’s row menu flags them; the badge under the name shows who is watched.

A guest who is flagged and holds an alerting ticket type is alerted once, not twice. Flagging needs the tickets permission; the recipient list and the type switches need event management.

The Tickets list with the Arrival alerts selector set to “Alerts: on”. Nine rows remain, each with an “Alert on” badge under the contact’s name: Jack Smith on Standing (Floor), Grace Khan on a Box Seat who arrived at 13:14 on 13 October, and holders of VIP Meet & Greet tickets, some of them refunded or cancelled.
Attendees → Tickets, filtered to Alerts: on — everyone the door will raise an alert for, whichever way they were added.

What the email says

The subject is the whole story — “Jane Smith has arrived — VIP Door” — and the body carries the rest: the guest’s email and company, their ticket type and seat, the date on a multi-date run, when they were scanned in (in your event’s time zone, and marked when the scan was recorded offline and synced later), which device or staff member recorded it, and why the alert fired — the guest was flagged, or their ticket type alerts. A button opens the order in the console. When a check-in has no entry point — a staff check-in from the console, or one made through the API — the email says so rather than guessing.

The event’s Emails area with an arrival alert open in its detail dialog. The dialog is titled “Grace Khan has arrived — Main Doors”, addressed to vip-host@frequentixdemo.test, with status Sent and the send time. The Message preview shows the email itself: a Frequentix Demo Co header, the heading “Grace Khan has arrived”, the line “Scanned in to Aurora Vaults — Live at The Foundry at Main Doors.” and the start of a details table with Name, Email and Ticket type (Box Seat).
Comms → Emails — an alert exactly as it was sent, with the entry point in the subject and the guest’s details in the body.

Once per guest, once per date

An alert is sent the first time a guest is scanned in, and not again: a re-entry on a scan-many ticket, an offline scan that syncs after an online one, or two devices admitting the same person all leave it at one email. On a multi-date run, a season ticket alerts once on each date it is used. Every way of checking in counts — a scanner at a gate, an offline batch, a staff check-in, the box office and the API — and a denied scan never alerts.

Plans