Prompt library
Events, tickets and publishing.
Copy any prompt below into your AI once it is connected to Presso Events, or hit Run it in Claude to open it in a fresh chat. Each one maps to a real tool, so you always know what is actually happening behind the words.
Your organiser profile
Uses update_organiser. This is your organisation's public identity, and attendees read all of it: it renders on your profile page, on every event page and in search results.
Set up our public profile: the name, a one-line description of what we do, London as our location, and our website.
What it does: sets your organisation's public name, description, location and website via update_organiser. The name is the one field to get right first, because it can only be changed before your first event is published or your first ticket is issued.
Use our logo and brand colours on the public profile, and make the profile page visible.
What it does: sets the logo, brand colours and profile visibility via update_organiser. Fields merge, so you can change one thing at a time without resending the rest.
Create an event
Uses create_event.
Create a draft event called "Autumn Product Summit" on 14 October 2026 in London.
What it does: creates a new draft event via create_event.
Configure and brand
Uses update_event_config.
Set the tagline to "Two days of product craft", write a short description, and use our brand indigo for the event page.
What it does: updates the event's tagline, description and colours via update_event_config.
Switch the agenda and speakers sections on for attendees.
What it does: enables those sections in the attendee app via update_event_config. Only sections you switch on render, so this is what makes a programme you have already written visible.
Agenda and speakers
Uses set_agenda, get_agenda, add_session, update_session, remove_session, add_speaker, update_speaker and remove_speaker. Your agenda is structured, not prose in the description: every session has its own times, track and room, speakers attach to the sessions they are on, and the attendee app groups it all by day in your event's own timezone.
Write the agenda for Autumn Product Summit: a keynote at 9am, a panel at 10:30 and a workshop at 12 on the first morning, with Ada Lovelace on the keynote.
What it does: writes the whole programme, sessions and speakers together, in one call via set_agenda. It is a set rather than an append, so anything left out of the payload is removed: your AI has to send the full programme every time, and a call that would remove sessions is refused unless it says how many go. Ask for a dry run first if you want to see the change before it is written.
Show me the agenda for Autumn Product Summit.
What it does: reads back every session grouped by day, each with its speakers, plus the full speaker list, via get_agenda. Sessions can exist and be read here while the agenda section is still hidden from attendees.
Add a 15-minute coffee break at 10:15 on the first day of Autumn Product Summit.
What it does: adds one session without touching the rest of the programme via add_session. This is the tool for a single edit once the agenda exists.
Move the closing panel to 4pm and put it in the Main Hall.
What it does: edits that one session in place via update_session. Anything you do not mention is left alone, and attendees who saved the session keep it.
Drop the sponsor showcase from the agenda.
What it does: removes that session via remove_session. It takes the session's speaker assignments and any attendee's saved pick for it with it, and there is no undo.
Add Ada Lovelace as a speaker: Head of Engineering at Analytical, with a short bio and her photo.
What it does: adds one speaker to the event via add_speaker. Give your AI the words the speaker actually sent you: a bio it invented is the first thing an attendee reads about them.
Update Ada Lovelace's headline and swap in her new photo.
What it does: edits that one speaker in place via update_speaker, leaving every field you did not mention as it was.
Remove Ada Lovelace from the speaker list.
What it does: removes the speaker and their assignment to any session via remove_speaker. The sessions themselves are untouched.
Ticket types
Uses ticket_types.
Add a Standard ticket at £150 and an Early bird at £120.
What it does: creates ticket types on the event via ticket_types.
List my ticket types and their prices.
What it does: reads back the event's ticket types via ticket_types.
Publish
Uses publish_event and list_events.
Show me the status of Autumn Product Summit.
What it does: checks the event's current state via list_events.
Publish Autumn Product Summit.
What it does: makes the event live via publish_event.
List all my events.
What it does: lists your events via list_events.
Selling and money
Uses generate_checkout, ticket_types, get_revenue and get_analytics.
Give me the ticket links for Autumn Product Summit.
What it does: returns the public pages that sell your tickets via ticket_types. These are the links you put in an email or on your own site.
Create a checkout for 2 Early bird tickets to Autumn Product Summit.
What it does: builds a one-off checkout for a specific quantity via generate_checkout - useful for invoicing a sponsor or a group booking by hand.
How is Autumn Product Summit selling?
What it does: reads the money on that event, gross, Presso's 1% fee, net of it, orders, refunds and disputes, via get_revenue. get_revenue is money only. For how many tickets actually went out, and the split across your ticket types, ask for volume instead.
How many tickets have gone out per ticket type in the last 30 days?
What it does: reads valid tickets issued per day, broken down by ticket type and by event, across everything you own, via get_analytics. It counts tickets rather than money, which is why a free event shows here and not in get_revenue.
What have I taken across all my events this year?
What it does: totals gross ticket sales less the platform fee via get_revenue. It is a ledger figure, not a bank balance - it says nothing about when Stripe pays you out, because that schedule is a setting in your own Stripe account.
A worked run, start to finish
The prompts above in the order you would actually say them. Nothing sells until the last step, and your AI has to read the full price list back to you before that one goes through.
I am running a two-day conference called Autumn Product Summit, 14-15 October 2026, at Second Home Spitalfields in London. Refunds up to 14 days before. Set it up with an Early bird at £120 for the first 50 and a Standard at £150, write a three-session agenda for the first morning with the speakers attached, then show me everything before we publish.
What it does: your AI works through create_event, record_event_setup, ticket_types and set_agenda, then update_event_config to switch the agenda and speakers sections on, asking for anything you left out rather than guessing it. Prices and the refund policy have no defaults - leave one out and the server refuses the call rather than inventing it.