For an internal corporate event, we recommend the full Happenee ecosystem, including the attendee app, even for 30 people. Adapt registration, communication, the agenda, and app content to your purpose: from practical information and materials to reservations or Networking. Employees can choose the web or mobile app, or stay with e-mail and admission documents; recommending the app does not make installation or use mandatory.
Describe the outcome for employees. For example: understanding three company priorities, meeting colleagues from another branch, or choosing a suitable activity. Use that outcome to design feedback later.
Define roles and the invitation path. Who receives an invitation, who confirms their own attendance, and who may select guests for a branch? Distinguish employees, nominators, team captains, and companions. Check how people without a company phone or regular access to their inbox will receive information.
Decide which data you will actually use. Attendance confirmation, transportation, dietary needs, and activity choices should each have someone who uses the answers. You do not need a field simply because it can be added.
Agree on an administrator and launch points. Registration, app content, and activity reservations can be ready at different times. You need a working registration path before the first invitation and useful content before introducing the app.
For invitation and confirmation at a simple gathering with a shared agenda, an Event microsite, Registration form, Confirmation e-mail, and practical E-mail campaign may be enough. Explain the purpose, time, venue, and contact on the microsite. Add check-in if you need to record arrival or control admission.
We also recommend a lightweight attendee app with information, a ticket, and materials to return to later; the e-mail path remains usable.
For a kick-off with discussion, prepare the Agenda, Speakers, Questions, and possibly Polls in the attendee app. The moderator needs to know when to introduce questions and who will answer them. One meaningful contribution to a discussion is more useful than several features with no role in the event.
For a sports day or learning event, address individual activity choices and capacities. For a branch gathering or recurring community, consider Networking with chat so people can find a colleague and arrange further contact. For a gathering of 50 people, Networking may be the app's main benefit; for a celebration, information, the ticket, and follow-up materials may take priority. An internal event also need not be limited to one language or exclude partners. Follow the actual audience and content.
If HR knows the invitees, prepare their list and a path for each person to confirm attendance and complete their own details. If a branch manager selects attendees, nominations may be suitable. Before using them, check the required scope and rules with support: who can add people, how many they can assign, and who sends the invitation.
For teams, explain whether employees are choosing a preference or an already confirmed assignment. If you assemble teams after the deadline, state this in the instructions and send the final assignment afterward. A captain or person filling in the list does not automatically confirm every member's individual attendance. Prepare change rules in advance and verify the specific team workflow; do not assume automatic roster balancing.
Consider companions separately: do you need a count, a named person, their own admission, or an activity choice? Check their path accordingly. An employee's company sign-in may not be available to a companion.
Prepare useful Attendee app content even for a small gathering: the agenda, practical information, materials, the ticket, and an organizer contact. Add reserved activities and selected engagement features according to your purpose. Explain the benefit in the invitation, such as “find training materials and colleagues from other branches.” After the event, keep promised materials available for the agreed access period; for a series, also prepare a path to the next gathering.
Each guest can choose e-mail/PDF with a QR ticket or a name lookup at check-in, the web app in a browser, or the mobile app. Do not require installation or use. If, as the organizer, you consider the benefits and decide not to use the app, provide practical information, admission, and changes through another agreed channel.
Connect registration or purchase to confirmation and the guest's correct app access. For the next gathering, provide the appropriate registration or sales link. Before sending it, test where it leads and whether the guest can complete the required step; displaying an existing ticket is not a new registration or purchase.
The web app opens in a browser. The mobile version may suit ongoing use; check access and required features on the devices employees actually have. An in-person event with a web app is still an in-person event; this alone does not require a hybrid setup.
Arrange SSO through customer success if you need company sign-in. Check employees, external guests, and companions separately; SSO does not supply form responses. A white label app is an option with your own branding through customer success, typically requiring 6–8 weeks of preparation. It is neither a necessary part of an internal event nor simply a logo change.
Shared talks can be informational agenda items. Use Workshop for activities with limited capacity and Time slot for repeated short reservations, depending on the scenario. Attendees register for sessions in the attendee app, including the web version; the public microsite alone does not let them reserve a place.
Before opening registration, define the capacity, registration opening and closing times, and an optional cancellation deadline. The cancellation deadline limits when a reservation can be canceled; turning off that setting does not prohibit cancellation. Allow time to move between activities.
There is no wait list. Prepare an alternative activity or another run if you have the space and instructor. An available place is not automatically promised to a particular substitute. A favorite item in a personal agenda also does not mean a reserved place.
The first message explains the purpose and leads to registration. The confirmation states what is complete and what comes next. A practical campaign before the event reminds people about the venue, transportation, and any QR admission; introduce the app once employees can find useful content there. Prepare appropriate targeting and copy for different branches or languages.
You prepare reminders to people who have not registered manually as a campaign; automatic reminders to this group are not available. Groups are global within the workspace, so distinguish their names and use by event. Changing one group can affect other content or communication.
During the event, use Notifications for changes and the moderator to introduce Questions or Polls actively. Supplement essential instructions with another suitable channel for people without app access. Publishing a notification does not confirm that everyone read it.
Before launch, walk through registration and confirmation in every language you use. Then test app content and access as an employee. Before the event itself, check staff, devices, and any printing: a QR code, a person without a QR code, a long name, and a team change. Check-in software does not automatically include staffing; arrange the equipment and support you need.
If you want gamification, Leaderboard is a paid feature enabled by customer success. It fits situations with clear rules, moderation, and a specific desired activity. Networking needs a purpose, completed profiles, and time to connect; a QR badge helps exchange contacts but is not required for chat.
After the event, distinguish invitees, registered attendees, and checked-in attendees. Focus the Survey on the original goal: understanding priorities, making a useful contact, or the suitability of activities. Statistics are in administration; use an export for colleagues, as there is no public statistics link. Before the next edition, check lists, dates, and access conditions again.
Questions, Polls, and a competition each need a specific moment and a responsible person. Give the moderator a short brief and test the attendee path.
After a manual change, check the old and new assignment, capacity, and visibility. Then explicitly inform the attendee; editing details does not itself send a message and is not an automatic identity transfer.
Check a regular employee, the required languages, and a device outside the company network. Include a companion or nominator if you use that path.
Web use, activity reservations, and a useful contact mean different things from an installation. Evaluate the intended purpose; a reserved meeting does not yet prove that people met.
