Hi, I'm Amal.
Your friendly AI assistant, who is not trying to take over the world ❤️
Ask me anything about this community and its content.
Knowledge base, support, ideas and a crowd that knows exactly what have you done the last week
Your friendly AI assistant, who is not trying to take over the world ❤️
Ask me anything about this community and its content.
Your starting point for quick answers, clearer how-tos and the small fixes that keep work moving. Start here, then head into support or the community when you want to go further.
How run.events collects what speakers deliver, checks every slide deck before it reaches the room, and makes speakers sign the conditions first.
The screens run.events puts in the rooms, the speaker ready room and the poster hall, who uses each one, and how they work together.
How accepted speakers confirm that they will present, how you follow their answers, and until when they can withdraw on their own.
What a structured abstract is, how a Smart Form collects it part by part, and where the parts appear afterwards.
What a session role is, what its settings decide, and how each presentation type uses its own roles.
The building blocks of a congress programme in the Agenda Builder, what each one is for, and how chairs can arrange their own blocks.
How a scientific committee reviews abstracts in run.events: the rating form, the score it produces, the rounds of review, and who sees what.
The difference between the draft and the published agenda, what a publication contains, what goes public at once, and how versions let you compare and go back.
The documents run.events makes from your sessions and your programme, how they stay up to date, and how you keep the right version for print.
What a presentation type is, what it decides for its sessions, and how its dates and hidden grace dates work.
What’s new, what’s changed, and the updates worth knowing right now — all in one place.
Welcome to the new run.events Community
You're looking at it: our new home, built right on run.events Smart Hub, the same platform our customers use to run their own event communities. Now it's running ours too.
Quick orientation if you're poking around:
The run.events community portal has changed! The address stayed the same, but everything else is new: it is built on run.events Smart Hub, the same community platform our customers use for their own events and year-round communities. Until now the portal ran on a third-party help-desk product. From today, it runs on run.events.
Every event published on run.events is now reachable over the Model Context Protocol (MCP). Any MCP-capable AI application, whether Claude, an IDE assistant, a company's internal AI assistant, or an agent you build yourself, can connect to an event and read its live data: event details, the agenda, sessions, speakers, ticket types with current prices, and sponsors and exhibitors.
Every sponsor and exhibitor on a run.events event has its own dashboard in the event portal. It is the place where a sponsor's team manages its presence at the event without going through the organiser: company information, team members and their tickets, lead retrieval, booth events, meetings with attendees, downloadable material, and the booth itself. This article describes what is there and how the parts fit together.