Events & Tickets

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

• Ticket sweep runs mondays · 8am and keeps the What's On dashboard fresh. Mondays — files new ticket confirmations, saves the tickets, and checks each event against your calendar.
• Event brief runs daily · 8am. The day before — the ticket, the venue, the doors time and the reference, in one card.
• What is captured lands in the Event register dataset, which lives at Data/Event Register in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Event party dataset, which lives at Data/Event Party in your vault — yours to open, search, and edit like any other file.
• What is captured lands in the Event wishlist dataset, which lives at Data/Event Wishlist in your vault — yours to open, search, and edit like any other file.
• The What's On dashboard reads from the dataset and shows, at a glance: events on the register · this weekend · not in the calendar yet · in the calendar · the wishlist, by on-sale date · tickets held · what this is.

The wiring, in one breath: Event capture writes to Event register · Event register shown by What's On · What's On kept fresh by Ticket sweep · Ticket sweep run by Robin · Robin runs Event brief · Robin holds Event capture · Robin holds Who is coming · Who is coming keeps Event party · Robin holds Venue and getting there · Robin holds Wishlist and on-sale dates · Wishlist and on-sale dates keeps Event wishlist.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

• Let the Monday Ticket sweep do the reading; your job is the glance. Open What's On when the weekend is coming and read This weekend first, then Not in the calendar yet — those two are the honest signal of what still needs your hand.
• Forward a confirmation the moment it arrives somewhere other than your inbox — a screenshot, a message from whoever booked — with a line saying what it's for. Event capture files it where the sweep would have, and saves the ticket into Tickets/ so the row links straight to it.
• Say the word on the calendar. When the sweep's card names an event that isn't in your diary, "add them" is all it takes; Robin adds those and nothing else, and the In the calendar ring moves.
• Ask Robin, not your email, when you're at the door: "where's my ticket for Saturday?" is answered from the register — the vault link, the reference, the doors time — never a search back through months of mail.
• Read the Event brief the morning it lands, the day before, and check it against what you know. It is drawn only from your own records (the register, who is coming and the venue notes on the row), so a detail it does not show is a detail they do not hold — say so and it is filed.
• Tell Robin when something changes hands — "gave the derby tickets to Sam", "the play's been cancelled" — and the row's status moves, so the brief and the cards stop treating it as a night out; the register keeps the row, so the count on the board still includes it.
• Say who is coming when you book for more than one — "Sam is coming with a plus-one, Priya has one" — and Robin keeps who is going on Event party. Give the price and it works out each share with the sum shown; "Sam paid me the rest" marks it paid back; ask "who still owes me?" and it adds it up, in the chat. It never writes to anyone, never decides what is fair, and the sums are not on the board.
• Before you go, ask Robin about the venue — the doors, the bags, step-free entry, how to get there from where you set out. It reads the venue's own page and says which page, and whether it covers that night, and says so plainly when it cannot find one. Ask for it to be kept and it goes on the event's row, where the Event brief carries it the day before. It is what the page said when it was read: check anything that matters to you on the day.
• Name something you would like to go to and it goes on the wishlist on What's On; ask when tickets go on sale and Robin reads that one event's own announcement and writes the date with the page it came from. Nothing here reminds you when the day comes, so the list shows the soonest first; tick one when you have bought it. Ask what is on this weekend, or for an idea for a night out, and Robin looks it up and suggests, naming the page it read; the wishlist holds what you name or take up.
• Afterwards, say how it went — "brilliant, the second half especially" — and your line goes on the ticket's row in your words, with the event marked attended. It is never a score, and Robin never asks.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

• Which kinds of event belong on the board — say "never cinema" once and the sweep leaves it out.
• Where your confirmations arrive and who you usually go with — said once, remembered for every sweep.
• Where you usually set out from, so that getting to a venue is looked up from there — said once, remembered.
• Whether the sweep reads your calendar at all, or the column stays "not checked" and you tell Robin yourself.
• How far ahead you want the Event brief, or turning it off and keeping just the board.
• The event labels and the ticket notes themselves — the register is yours to edit, and the board follows it.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

1. Adding the Kit offers the first sweep right away: connect your email on the same screen, start it with one tap, and watch Robin read back through a year of ticket confirmations — gigs, theatre, comedy, sport, talks, festivals — file every live ticket with where it's kept, save any ticket file into your vault under Tickets/, and check each event against your calendar. The calendar is asked for the first time the sweep reaches for it; until it is connected, the calendar column honestly reads "not checked". Prefer not to connect email? Tell Robin about the next thing you've got tickets for instead, and the register builds by hand, starting from what 1Presence already knows.
2. When that first sweep finishes, Robin leaves a short note in your 1Presence inbox saying what it filed — how many events, at how many venues — and invites a few minutes together to catch anything that isn't yours and fill what email could not show: an event with no date or venue, tickets a friend bought or that wait at the box office or in an app, an event with a date and no ticket yet. You can also say which of the ones not in your calendar you'd like added. Robin starts from what 1Presence already knows, in its memory and in the files in your vault, and asks only for the gaps. Nothing goes into your calendar until you say so.
3. Whatever is still blank waits on the Kit page with a way back to Robin, and Robin offers it once the next time you talk. Tell it a part does not apply to you, or that you have finished setting up, and it stops asking.
4. From then on the Ticket sweep runs on Mondays and raises a card only when something new arrived, something booked isn't in the calendar, or a cancellation came in — offering, never adding. The Event brief runs each morning and stands down until the register has an event on it; the day before you go, it sends one card with the ticket, the venue, the doors time and the reference.
5. Mention something you've booked in passing and it goes on the register; forward a confirmation and the ticket file is saved and linked from the row — never the barcode.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits