Short answers, no ticket queue.

Add https://events.pressonetwork.com/mcp as a custom connector in Claude, ChatGPT, Cursor or any client that supports remote MCP servers, then sign in when your assistant opens the Presso Events sign-in window. It is passwordless, there is no token to find or paste, and the first sign-in creates your organisation from your email address. The connector page has the one-click install for Claude and the exact command for Claude Code. The connector page.

Remove it and add it again, and check the URL is exactly https://events.pressonetwork.com/mcp with no trailing slash. Adding it should open a Presso Events sign-in window; if your assistant reports that authentication is required, it has not finished that sign-in. Complete it, and the full toolset appears without reconnecting. The connector page.

Ask it to confirm the connection first. If it reports a different organisation, you signed in with a different email from the one holding the events, and that sign-in created a new organisation. Remove the connector, add it again and, when the Presso Events sign-in window opens, sign in with the email that holds your events. It does not have to be the email your AI account uses.

Presso Events runs from your AI rather than a website dashboard: connect Claude, ChatGPT or another assistant and ask it for your events, tickets, orders, attendees and payouts. If you signed up on the website before, connect with the same email and your organisation and events are all there. Connect your AI.

It is taken from each ticket sale as the payment passes into your Stripe account. There is no invoice to pay, no minimum, no per-attendee charge and no subscription. Stripe charges its own standard processing separately, paid to Stripe. The whole of pricing.

The platform fee on that ticket is refunded with it. We do not keep a fee on a sale that did not stand.

Yes. The fee is a percentage of ticket revenue, so a free ticket costs you nothing, and you still get the portal, the checkout and the attendee app.

If you sold with Presso Tickets before, email support@pressonetwork.com and we'll link your existing Stripe account. Otherwise Claude sets one up with you in a few minutes.

Stripe needs your business details and a bank account before it will release payouts, and it sometimes asks for more after the first sales. The outstanding list is in your own Stripe dashboard - it is their check, not ours, and we cannot clear it for you.

You hold it. Payments land in your Stripe account and pay out on your own Stripe timetable. Presso Network Ltd is not the merchant of record, never holds your funds, and adds no payout schedule of its own.

Yes - multiple types per event, each with its own price and quantity, including free ones. You can issue a free ticket directly for speakers and sponsors without going through checkout.

Ask your assistant to cancel it. It first shows you how many paid and free tickets there are, how much will be refunded and your available Stripe balance, and changes nothing until you say yes. Then sales stop, every paid ticket is refunded in full to the card that bought it, free tickets are cancelled, and every ticket holder is emailed once. The refunds come from your own Stripe balance, because the money was always yours - Presso never holds your funds. If your balance is short, Stripe still makes every refund and takes the difference from your bank account. The platform fee on each refunded ticket is returned with it. A cancelled event cannot be brought back; if the date is only moving, change it instead and holders are told the new details.

Publishing is the moment a stranger can be charged, so the server refuses until the event has dates, a venue, a refund policy and real ticket types - and then only once the full price list has been read back to you and confirmed. If what comes back does not match what is about to go on sale, nothing publishes. All the guardrails.

An email with their ticket, a QR code, a six-character check-in code, and a link to your event app with the agenda and speakers. It is sent by Presso Events on your behalf, and there is no account for them to create. Walk the attendee journey.

Resend it from the portal, or ask your assistant to. The link does not expire.

Three ways, and you can mix them on the night. Tick people off: ask Claude or ChatGPT to open the door for your event, and the door screen shows your guest list with a box to tick as each guest arrives, plus the live count. Type the code: the same screen has a box for the six-character code on the ticket, for example 7HK-2M9. It ignores hyphens, spaces and case, and reads I and L as 1 and O as 0, because people read them out loud. The QR code on the ticket holds the same code, and you can also just ask Claude to "check in code 7HK-2M9 for Spring Founders Supper". Print or export the list: tap Download list on the door screen, or ask for the guest list as Excel, and you get a private link to an Excel file, a CSV or an A4 tick sheet sorted by surname to print and cross off by hand. The link works for 15 minutes, and the list itself never appears in the chat. Checking in the same ticket twice says it was already checked in rather than counting it again. Door staff need the Presso Events connector added to their own Claude or ChatGPT, signed in to your team with an editor role, to check people in. A viewer can see and download the list but cannot tick it.

You do. Ask Claude or ChatGPT for your guest list as Excel or CSV (the get_attendees tool), or tap Download list on the door screen, and you get a private download link; the list itself never appears in the chat. Use it in whatever tool you already run. We do not market to your attendees and we do not charge you to reach your own audience. Every tool your AI can call.

No, and there is no marketing-email product in Presso Events at all. The only mail we send is the ticket itself to the person who holds it, and a notice to them if you change the date, time or venue of that event, or cancel it.

No. Your connection is scoped to your account. There is no shared context between organisers, so it cannot read another organiser’s sales, buyers or payouts.