Event registration for universities and research

A faculty office runs a public lecture series with eight dates, a two-day conference with 150 seats, and an alumni evening in June. Today each of these lives in a different place: a Google Form for the lectures, a spreadsheet for the conference, and a mail thread for the alumni list. Nobody knows at a glance how many people are coming, and the printed list at the door is already out of date.

With Mission Support the same office creates every date from an event template. Lecture, Workshop and Book presentation come ready with a registration form, so a new date takes a few minutes. Each date gets its own sign-up page under the institute’s address, a confirmation mail and a guest list. The conference gets a capacity of 150 and a waiting rule for when the room is full. The alumni evening lets each guest bring a companion, with a name on the list.

At the door, a student assistant scans QR codes with their own phone. A week later a follow-up form asks for feedback, and the department gets one Excel file with a sheet per question set. All of it is in the Free plan for a single event, and in Plus or Pro for the whole semester.

A Google Form collects names well. It does not know that the room holds 150 people, that the same person registered twice, or that a guest has cancelled. The spreadsheet behind it is edited by three people and printed the evening before. Reminders go out by hand, if at all.

Mission Support is built around the guest list rather than the form. Capacity is enforced when someone registers. A cancellation is recorded and frees the seat. The reminder mail goes to everyone who has not responded, from the institute’s own sender address. And the list at the door is live, not printed.

• Lecture series: one event per date from the Lecture template, each with its own address under the institute’s subdomain or domain, a short description and a calendar link in the confirmation.

• Conference: capacity per ticket category, for example 120 delegates and 30 speakers, a registration window with a clear start and end, and a reference code on each ticket for the badge.

• Alumni evening: personal invitations with one link per guest, companions, recorded declines, and a reminder two weeks before to everyone who has not answered.

• Afterwards: a follow-up form to attendees, a campaign with the recording or the slides, and one Excel export per event for the department.

Universities are used to asking where data goes. The database and the application run in Frankfurt, mails go out through Brevo in Paris, and payments, if you ever take any, run through Stripe in Dublin. The university remains the controller, Mission Support is the processor under Art. 28 GDPR.

Guest pages carry no analytics and no cookies. Each contact can be exported on request, and a retention purge removes guest data after an event when you want it gone. Nothing on the guest page is sold to anyone, and nobody is asked to create an account to register.

Free covers one live event with up to 100 guests and one admin, with no time limit. That is enough for a single lecture or a small workshop. Plus at €49 per month gives five live events, 500 guests per event and three admins, plus QR tickets, your own logo and event address, reminders and companions. Pro at €149 per month removes the event limit, raises the cap to 2,000 guests and 10 admins, and adds personal invitations with approval, conditional logic in forms, file uploads and a custom domain.

A single event pass at €199 one-off unlocks Pro for one event with up to 500 guests, which suits a conference that happens once a year. Every workspace starts with 14 days of Pro, no card required.