A conference

Several days, several rooms, workshops with limited seats and an audience asking questions. It is the most demanding format, and the one that leans hardest on the programme.

Illustration - no real data

How it goes

The same features as for any other event, in the order a conference uses them.

  1. Before

    You build the site and the programme: sessions, rooms and speakers, over as many days as needed. Capacity-limited workshops open for booking, with a waiting list that moves on its own. Registration opens, each participant gets their QR badge by email, and reminders follow.

  2. During

    The desk scans badges on a phone, the list updates for the whole team, and workshop attendance is taken session by session. In the room, the run of show chains polls and audience questions; stage screens display whatever you send them.

  3. After

    You read attendance session by session, add your own figures, and send the report to the client by a revocable link. The next edition is built by duplicating this one.

What it does not cover

Two things a conference sometimes needs and the tool does not do.

  • No paid ticketing: registration is free. A paid conference sells its tickets on its own platform (Billetweb, Weezevent…); once that platform is connected, its buyers become participants here, with their badge.
  • No dedicated mobile app. Programme, badge and interaction open in the participant’s browser. That avoids a download, but does not replace an app if you want one.

Questions we get

How many sessions and speakers can be handled?
Several hundred of each, with search, filters on every field and pagination, in the dashboard and on the site.
Can workshop seats be limited?
Yes, session by session, with a waiting list that moves on its own when someone drops out, and attendance specific to the session.
The conference is multilingual: is that handled?
Yes. Up to seven languages per event, falling back to the default rather than leaving a gap. Participants get theirs without having to choose it.