The audience page — Studio → Audience — is the deed to the thing you're building here: the list. Who you can reach, on which rails, sliced by what fans actually did, and exportable any day. The page's own headline is the policy: the list is yours — feed it.
- The strip: people, paying now, lifetime value, average per payer, push-reachable, email-reachable — all net of every fan's own dials.
- The behavioral guest lists — counted from rows fans wrote, and each one opens as a roster and a send.
- The members table: what each person holds, what they're worth, when you last saw them, and which rails still reach them.
- Bring your list: paste emails, attest the opt-in, done. Texting is never importable.
- Export any day — names, emails, consents with provenance. No exit interview.
The number to watch
Push-reachable is reach you own outright — no carrier, no platform, no per-message toll in the path. Every fan you move there stays free to reach, forever. The product moves fans toward push on evidence only: once push notifications provably reach someone, their texts go quiet on their own (a fan who elected “keep texting me” keeps their texts — their dial wins).
The table, and what's in it
Under the chips is the roster itself, a row per person: their name and address, what access they hold (a Pass by name, Lapsed when it ended, Contact when you brought them, Follower when that's the whole story), what they've spent with you — lifetime value first, then Passes, tips and tickets broken out — when you last saw them in a room, and which rails still reach them. Sort by lifetime value, newest, last seen, or name; the sort runs over the whole list, not just the page you're looking at. Lifetime value is every settled dollar: Passes, tips, tickets, meet & greets and drops, refunds already taken out. It is the same number on the fan's own page, because it's the same query.
What the table will never show you is why a rail is dark. A fan's dials are theirs; you see whether you can reach them, never what they turned off.
Guest lists you don't have to build
The chips are computed from rows — were in the room, sent hearts, tipped, bought a ticket or Pass, haven't been in a room yet — and each one is three things at once: a count, the roster under it, and a send (Tell this list opens the composer with it checked and the preview already pricing it). No rule builder, no stored lists to go stale. The search box under the roster finds one fan by name, email, or number, and every fan opens to their own page with your private notes.
Bringing your list
Paste emails or upload a CSV (you point at the columns). One rule, stated on the card: the import covers email only, and it takes your word — a checkbox attesting everyone on the list knowingly opted in. Texting anyone takes their own word: they text you first, or they turn it on themselves. An import can't grant that, here or anywhere.
Taking it with you
Export CSV, any day: names, emails, numbers, consents with their provenance, and where every contact came from. The clause is printed beside the button and lives in the terms: we keep only the operational records any platform legally keeps — we'd rather you stay because leaving is easy. The same truth is an API: mint a read-only key on Studio → Automations → APIs and Webhooks and /api/v1/audience, /api/v1/audience/export and /api/v1/streams serve the list, the reach and the receipts — the export is byte-identical to the button.
The welcome, and the other lifecycle moments
Everything that goes out lives one row down the rail, on Studio → Automations: every moment BackstagePass sends on — a fan follows, joins backstage, buys a ticket, the live reminders, the encore, a new Pass, somebody going quiet, a Pass running out. Each one is a switch and a rail: what it says is ours to write, because it goes out on the BackstagePass domain, so you can read every sentence on that page before you turn it on. One human gets one message per moment, it rides the same rails as everything else, and every send lands on a receipt. Every blast you’ve made and the day-by-day delivery log are two pills on Studio → Channels, under that page’s own header — which is also where you see who each rail can reach.
The two pages share one vocabulary: an automation's “only these fans” is one of the guest lists whose counts are on this page, so what a moment did is always checkable against a number you can already see.