Event CRM.Every contact's history across all your events.
An event CRM is the contact database behind all your events: it knows who was invited, who said yes and who actually showed up. In AirLST the guest list is your event CRM. Every guest is a contact, every event an entry in their history, with consent, attendance and survey answers, ready for your next invitation and in sync with Salesforce or HubSpot.
- Send email
- Invite to event
- Edit
- Delete
- Oct 2026Brand Summit 2026 VIP · confirmed · checked in 6:06 PM · survey 5/5
- May 2026Partner Day Partner · confirmed · checked in
- Nov 2025Fall Customer Event invited · declined
- Mar 2025Product Launch Attendee · confirmed · checked in
One contact database for all your events, not one list per event.
Yesterday's guest is tomorrow's contact, with everything you already know about them.
Who comes, who declines, who never replies: visible on the contact and ready to filter.
Opt-in and opt-out with a timestamp; the rule for who you may email sits on the contact.
Salesforce and HubSpot supply contacts, AirLST sends event data back.
Your next guest list starts with a question about the last one.
Who came to Partner Day and to the summit? Who declined twice? Who gave the survey five stars? With attendee data across events, the answer is a filter on your contacts, and the result is the invitation list for your next event.
| Contact | Events | Opt-in |
|---|---|---|
| CVChloe Vance | 4 · 3 attended | Event |
| JWJames Walker | 3 · 2 attended | Event Marketing |
| DSDavid Shaw | 5 · 5 attended | Event |
| TLTom Lee | 2 · 2 attended | Event |
Add the selection as guests to the new event, with group, data and consent; the invitation goes out through event invitation emails.
Address, company and job title come from the latest registration; guests correct their own data through their personal link.
Checked per event before anything is sent; imports update records through the booking code. Across events, duplicates are matched and merged.
Who you may email is recorded on the contact. With a date.
A contact database that grows over years needs rules: event communication for the event, marketing only with an opt-in, deletion according to your retention policy or on request. AirLST records consent per contact with timestamp and source, makes it filterable and logs every change.
- Two consents, kept separateEvent communication and marketing, per contact, with timestamp and source (registration, import, team).
- Built into the selectionAn invitation only goes to contacts whose consent matches; the rule lives in the filter.
- Export and deleteData access requests and deletion per contact; retention periods follow your policy.
- Read the rulesData processing agreement, hosting and retention in the Trust Center.
- Oct 24, 2026Photo and video empty → agreed · guest (check-in, signature)
- Sep 8, 2026Marketing empty → not given · guest (registration)
- Sep 8, 2026Event communication empty → subscribed · guest (registration)
Your company CRM stays the system of record. AirLST adds the event data.
If you run Salesforce or HubSpot, your contacts live there. The AirLST event CRM then becomes the event side of each contact: the connector brings contacts and lists in as guests, and invitation, RSVP and attendance go back as status or activity, for sales, marketing and follow-up.
- Salesforce and HubSpotReady-made connectors; fields and sync direction are set up with our integration services.
- SAP, Dynamics, marketing automationThrough the REST API as an integration project.
- No company CRM?Then AirLST is your contact database for events, with history and consent.
- Learn moreConnectors, API and MCP on the integrations page.
Contact data kept for years: this is where data protection is not an afterthought.
An event CRM stores personal data for the long term. That is why AirLST keeps it on servers in Germany, with consent per contact, roles and permissions for access, a change log and retention rules, assessed under TISAX, the information security assessment standard of the automotive industry.
- Hosted in GermanyContact and event data are stored on servers in Germany.
- GDPR compliantAccess requests, deletion, data processing agreement and retention rules in the Trust Center.
- TISAX assessedThe information security assessment standard of the automotive industry, passed by AirLST.
Example roles. You assign permissions per user; an agency only sees the guest list of its own event.
The event CRM is your guest list, read over the years.
Every event writes to the contact: invitation, RSVP, attendance, answers. The next event reads it. That is why there is no separate contact database next to the guest lists, just a guest who keeps coming back.
Many events, one contact database and one standard for every team: that is event management software with AirLST. The rules for storage and deletion are in the Trust Center.
What is an event CRM?
An event CRM is the contact management an event organizer runs across all events: contact data per person (salutation, title, name, company, department, job title, address, email, phone), plus a history of every event they were invited to, accepted, attended or answered, and the consent that defines how you may contact them. That makes it the basis for picking your next guest list and for outreach that knows who was actually there. Event management CRM and CRM for events mean the same thing.
In AirLST the guest list is the event CRM: a guest is a contact, an event is an entry in their history. If you run Salesforce or HubSpot, connectors link the two; your company CRM stays the system of record for contacts, and AirLST supplies the event side. Without a company CRM, AirLST is your contact database, with consent tracking, change log, roles and retention rules on servers in Germany.
The event CRM is your guest list, read over the years.
How does AirLST build your contact database?
- First event. An import or the registration form creates guests; contact data, consent and answers are stored on the guest.
- History grows. Invitation, RSVP, attendance and survey answers are written to the contact; guests update their own data through their personal link.
- Selection for the next event. Filter by history: returning guests, decliners, survey respondents, each with matching consent; then add them as guests to the new event.
- Integration. Connector to Salesforce or HubSpot, API to SAP or Dynamics; contacts come in, event status goes back.
- Maintenance and deletion. Roles and permissions, change log, access requests and deletion per contact, retention periods you define.
Event CRM vs. sales CRM: what is the difference?
A sales CRM knows a contact as a customer, lead or partner: revenue, pipeline, account owner. An event CRM knows the same person as a guest: invited, attended, seated, answered. Both are true about the same person, and neither replaces the other. Keep event data in your sales CRM and you get campaign members without attendance; keep customer data in your event tool and you lose the pipeline.
The company CRM owns the contact. The event CRM owns their events.
That is why AirLST connects the two instead of replacing one: connectors deliver contacts and bring event status back, roles control who sees which side, and consent applies on both sides. For organizers without a company CRM, the event CRM is the contact database that gets better with every event.
What does the event CRM work with?
With the guest list as the view of one event, event invitation emails for outreach, event registration so guests keep their own data current, the event check-in app and post-event surveys for the history, event reporting and analytics, and the connectors and API for Salesforce, HubSpot, SAP and Dynamics.
- Event management software: one contact database for many events and teams
- Corporate hospitality: sponsors, partners and their guests across seasons
- Trust Center: storage, deletion, data processing


