An internal corporate event (team-building, kick-off, anniversary, roadshow) is typically for employees, often in two languages (CZ + EN), with no paid tickets. The goal is to deliver strategy or vision and engage employees — so it makes sense to combine a classic setup (Agenda, Speakers, registration) with engagement features (Polls, Questions, Survey, Leaderboard) and sometimes gamification. No paid tickets, usually no sponsors or exhibitors, but with a focus on communication and the attendee app.
Decide four things before you start the setup:
Event size: small (up to ~50) / medium (50–300) / larger (300+). This determines whether to turn on the attendee app and engagement features at all.
Languages: typically one or two (Czech + English). Three languages are almost never seen at internal events.
Paid tickets: at internal events, no. Employees do not pay for registration.
White label / SSO: at larger companies this is handled through customer success — branded microsite, custom app, single sign-on with the company identity system.
An internal event has a clear message — a new strategy, an annual recap, a product launch, celebrating a success, team-building. Employee satisfaction is secondary — the primary goal is to deliver the message. That is why it makes sense to use engagement features so participation is not passive: a game, Polls, audience Questions, gamification at internal booths.
Modules
Event microsite — a basic event card with the Agenda and Venue. Internal events are usually not shared publicly, but the microsite serves as a reference point.
Registration form — collecting attendance, additional questions (diet, transport, T-shirt size).
Invitation e-mail or E-mail campaigns — the first wave of invitations. At larger companies with different employee groups, campaigns make sense (targeting).
Confirmation e-mail — with a QR code and a link to the attendee app.
On-site check-in — QR scanning at the entrance, typically with badge printing.
Attendee app (mobile and web) — the key channel during the event.
Content features
Agenda — structure of the day, times, stages.
Speakers — who is presenting (CEO, department heads, external guest).
Venue — where the event is held (address, map, parking).
Contact — the organizer to reach out to.
Custom content — FAQ (dress code, transport, cancellation), site map, catering information.
Engagement features
Notifications — push notifications for Agenda changes and updates during the day.
Engagement features as needed
Polls — for events with moderated discussion or vision presentations ("How would you rate…?").
Questions (from the audience) — for panel discussions and Q&A with leadership.
Survey — feedback at the end of the event.
Leaderboard — if you want to gamify (points for activity, booth visits, taking part in Polls).
Contests — a combination of Leaderboard and rewards.
Social / photo / video engagement — sharing experiences in the attendee app.
Single sign-on (SSO) — at large companies with enterprise integration. Employees sign in to the app with their company account, no separate registration. Customer success turns this on.
White label app — a branded mobile app in the App Store and Google Play under the company's name. Standard at larger enterprise customers. Customer success turns this on.
Sponsors, Exhibitors — not present at a classic internal event. Exception: the company has a parallel exhibition of internal departments (HR booth, IT booth) — then it is exhibitors in an internal context.
Online module — only if you stream between branches or have a hybrid format (some attendees join online). Otherwise unnecessary.
Paid tickets — not used at internal events.
Nominations and Nominators — rarely relevant for internal events (registration is run centrally by HR).
Networking (Attendees feature) — usually not needed at internal events (people know each other). Exception: a large company with branches that wants to connect teams.
Seating — only at formal gala dinners with a fixed seating plan.
Before the event
Date announcement — typically through an internal channel (Slack, Teams, intranet). Link to the microsite.
Invitation e-mail / campaign — with a registration button. At large companies, split into segments (by department, branch, language).
Confirmation e-mail — automatic after registration, with the QR ticket and a link to the app.
Reminder 2–3 days before the event — an e-mail campaign with the Agenda, transport, dress code. Attach an ICS file so employees can add the event to their calendar.
Reminder on the morning of the event — with the QR code (helps reduce queues at On-site check-in for people who deleted the e-mail).
During the event
Push notifications via Notifications — Agenda changes, session openings, contests, announcements.
Polls / audience Questions — during panel discussions.
Leaderboard / gamification — running point updates.
Survey at the end of the day — optionally with an incentive (a draw).
After the event
Follow-up e-mail — thank-you, photos, video, key take-aways.
Link to materials — speaker presentations, recordings.
Survey results — sharing feedback with employees (where appropriate).
Advanced engagement (contests, audience Questions, Polls) needs an active moderator. Without one, the features look turned on but feel dead.
At large companies, split the audience into groups (branch, language, role) and use targeted E-mail campaigns. One generic e-mail to 2,000 people has a lower open rate than three targeted ones.
The attendee app is also available as a web app (link from the e-mail) — the attendee does not need to download anything. For medium and larger events, always turn it on.
The Agenda content feature fills both the microsite and the app automatically. If it is missing in one, you most likely filled it only in the microsite text, not in the Agenda content feature.
Fill in the badge content based on what you have in your contacts. Whatever is missing in the form will not appear on the badge.
