Contacts and segments
Every person who touched your organisation, filterable and reusable as audiences.
Contacts, at organisation level, is your people surface: one row per person, merging every mailing-list subscriber, prelaunch registrant and ticket buyer your organisation has. It fills up even if you have never sold a ticket. The header shows your total alongside how many are emailable and how many you can reach by SMS or WhatsApp, counted with exactly the same consent rules a real send uses, so the numbers always match what a campaign will reach.
People with only a phone number
Someone who signs up with just a phone number, or arrives on an imported list with a number and no email, is a contact like anyone else. Their row shows the number where an email would be, and they can be reached by SMS or WhatsApp if they agreed to it. They can never be emailed, because there is nothing to email.
If the same person later gives you an email address alongside that number, the two records join up on their own, so they are one contact with one set of permissions. This only happens when that number belongs to exactly one email contact: a number shared by two people (a couple, or a manager and their company address) is never joined automatically, and instead shows up under Possible duplicates for you to decide. The contact page lists any number joined this way under Also on file, and an admin can unlink it there if it was wrong.
Work the list
Filter by name, email or phone number, by stage (lead, registrant, customer, repeat), by channel consent (email, SMS, WhatsApp, post, push), by tag, by minimum lifetime spend and order count, or by the event somebody attended. Each row shows the contact's stage, consent chips, tags, orders, spend and last activity.
Attended is not the same as bought: it means a ticket of theirs was actually scanned in at the door, so it leaves out the people who bought and never turned up. It is credited to whoever paid for the order, so a group booking counts the buyer.
Tags are edited inline on the row: add one with a click, remove it from its chip. The tags you create become a shared vocabulary that feeds both the tag filter and the segment builder.
Contacts who have bought tickets carry a buyer record, and admins can edit it from the row: fix a name, phone number or email, and the change flows through to their orders.
Segments
Segments are saved contact filters: name or email, stage, channel consent, minimum spend, minimum orders, the event somebody attended, and tags (a contact must carry every tag you select). Build one, preview the count, and save it.
Because a segment carries its own event, "everyone who came to last year's edition" is a segment you can point at this year's campaign: save it once, then narrow any email or WhatsApp send to it.
A segment stores the filter, never a list of people, and membership is evaluated live: for email campaigns that happens at the moment the send fires, so your audience is always current; WhatsApp campaigns lock their recipient list in when you send or schedule. Deleting a segment is safe by design: anything already sent is unaffected, and a scheduled email still targeting it fails safely instead of sending to everyone.