Retail event managementEvery invitation on record.
Invite dealers and partners who invite guests of their own, with consent, allocation and a record. AirLST keeps opt-in, allocation, registration and scan on the same guest, in your brand design.
- 1Double opt-in
The confirmation runs as a system template; every change is stored with a timestamp.
- 2Allocation per partner
Every partner has its seats; headquarters sees taken and remaining.
- 3In your brand design
Invitation, registration page and ticket from one template.
What decides how a brand may invite and meet
Four rules that apply as soon as a brand invites dealers, partners or customers. For each: what it means for the event, and where it comes from.
Email invitations: CAN-SPAM
Commercial email needs a clear opt-out, a valid physical postal address, and opt-outs honored within 10 business days. Whoever sends the invitation has to know who opted out of what.
Source: FTC: CAN-SPAM Act compliance guideContacts in the EU: consent with double opt-in
For dealers and customers in Germany and the EU, marketing email generally needs prior consent; German data protection authorities consider double opt-in necessary, with the confirmation email as proof.
Source: DSK guidance on advertising (German PDF)Sweepstakes: no purchase necessary
Mailed sweepstakes have to state in the mailing, the rules and the entry form that no purchase is necessary and that a purchase does not improve the odds. For a launch with a prize draw: rules and marketing consent as two separate checkboxes.
Source: 39 U.S.C. 3001 (Cornell LII)Antitrust at dealer meetings
Using a trade association or dealer council to control or suggest prices is illegal. Partner summits run on a reviewed agenda that is kept, so the meeting can be shown to be neutral later.
Source: FTC: spotlight on trade associationsThese summaries are not legal advice; what counts are the requirements of your legal and privacy teams, including state law. How AirLST processes data is described in the Trust Center.
Who invites, who checks, and what each needs
How do we invite 300 dealers without an opt-out problem?
Invitation in the brand design, event opt-in and marketing opt-in kept separate, every change stored with time on the guest.
Invitation emailsWhich partner has how many seats, and who is coming?
Allocation per partner in the guest list, taken and remaining seats visible to headquarters, companions as a separate registration step.
Guest list appDoes every event look like our brand, even the twentieth?
Invitation, registration page and ticket set up once in the corporate design, copied as a template for every further event.
Event websitesDo RSVP, attendance and lead land on the right contact?
Connectors to Salesforce and HubSpot or the REST API, lead capture at the booth with the consent of the scanned person.
API and integrationsTypical events for retailers and consumer brands
How each event runs in AirLST is described on the linked page. Here only why it comes up in this industry.
What the industry asks for and how AirLST delivers it
Standard means: in the product and documented on the feature page. Custom build means: AirLST builds it for you in the project; scope and effort are part of the conversation.
| Requirement | Standard | Custom build | More |
|---|---|---|---|
| Double opt-in and consent historyDouble opt-in as a system template, event opt-in and marketing opt-in kept separate, status, time and trigger of every change on the guest. | – | Invitation emails | |
| On-brand invitationsInvitation, registration page and ticket in the corporate design, as a template for every further event. | – | Event websites | |
| Allocations per partnerEvery partner has an allocation, headquarters sees taken and remaining seats, a waitlist for everyone else. | – | Guest list app | |
| Official rules and consent kept apartSeparate fields for official rules, marketing consent and companions in the registration. | – | Event registration | |
| Lead capture with consentBadge scan at the booth, the scanned person consents by holding out their badge, export per account manager. | – | Lead retrieval | |
| CRM syncConnectors to Salesforce and HubSpot, REST API; field mapping through integration services. | – | API and integrations | |
| Partners add their own guestsA login per partner to fill their allocation with guests on their own is a custom build. | – | Custom development | |
| Sweepstakes with drawingA sweepstakes module with a drawing and winner notification is a custom build. | – | Custom development | |
| Consent records as an exportAn export with wording and confirmation email per contact for your privacy audit is a custom build. | – | Custom development |
Security and data protection
- TISAX-assessed
AirLST has been assessed under TISAX, the information security standard of the automotive industry.
TISAX at AirLST - Hosted in Germany
The platform runs on Amazon Web Services in Germany. The AWS infrastructure holds ISO/IEC 27001, SOC 2 and BSI C5; these are certifications of our hosting provider, not of AirLST.
Data hosting - GDPR and DPA
Processing follows the GDPR, with a data processing agreement; the current list of subprocessors is provided with it.
GDPR - Signed at the guest
Consents and NDAs are signed digitally and stored with the guest record; the entrance sees at the scan whether the signature is there.
Event access control
Tickets and fees are paid in the registration form through Stripe, Mollie or PayPal. Revenue goes straight to your account; card data stays with the provider.
Event ticketingHow retailers and brands typically set up AirLST
- 01
One template per format
Dealer summit, launch and roadshow each set up once in the brand design, copied per event.
- 02
Opt-ins kept apart
Event opt-in for confirmation and ticket, marketing opt-in for promotion, double opt-in automatic.
- 03
Allocation per partner
Partner and region as fields on the guest, each counts against its allocation.
- 04
Confidentiality before the launch
Whoever gets embargoed material signs digitally in the registration.
- 05
Sync back to the CRM
RSVP, attendance and consent on the contact in Salesforce or HubSpot.
Used by retailers and consumer brands
Digital Acceleration Summit with close to 30 speakers
Attendee management, live stream and interaction on one platform.
Read the case study Case study · Telefónica2,000attendees, one designPlanning events in-house, every template in the corporate design
Landing pages, tickets and emails adjusted by drag and drop, every event in their own hands.
Read the case studyHospitality allocation around the Champions League and Formula 1
Heineken assigns its hospitality allocation around the UEFA Champions League and Formula 1 with AirLST.
- Allocations
- Hospitality
- Partners
The invitation is usually marketing
An email that invites dealers or customers to a brand event is in most cases commercial email under CAN-SPAM: it needs a working opt-out, a postal address, and opt-outs honored within 10 business days (FTC). For contacts in the EU the bar is higher: prior consent, confirmed by double opt-in. AirLST keeps event opt-in and marketing opt-in apart in invitation emails and records every change with a timestamp.
Whoever invites has to be able to show they were allowed to.
Partners who invite guests of their own
In retail the brand rarely invites alone: dealers, distributors and partners get seats they fill with their own guests. To keep headquarters in control, allocation and source belong on every guest as fields, and the guest list shows taken and remaining seats per partner. How this works for hospitality is described under corporate hospitality; a login per partner is built through custom development.
Dealer meetings with an agenda
When competitors meet, through a trade association, a dealer council or a partner summit, the FTC warns that using the forum to control or suggest prices is illegal (FTC). A reviewed agenda on the event website and an attendee list from check-in make the meeting traceable afterwards.