Every participant knows where their application stands

The status changed — the person got an email in their language. Confirmed — the email carries a pass for Apple and Google Wallet. Need to tell something to speakers only, or to the press only — a campaign to that segment, with a delivery status for each person.

The email log: to whom, which email, in which language, the delivery status
01

An email for every status change

Application received, approved, confirmed, declined, waitlisted, data needed. Six templates you edit to the event’s tone — in any languages.

  • A participant gets the email in the language they filled the form in
  • Placeholders from the profile: name, category, event
  • The event’s own sender and Reply-To
Trigger emails: a template per status, two languages side by side, with variables
02

A campaign to a segment, not to everyone

To speakers — about the hall and time. To partners — about build-up. To everyone confirmed — about opening. A segment is built with the same filters as the application catalogue.

  • Reusable campaign templates
  • A preview and the recipient count before sending
  • Trigger emails — on an event in the system
A new campaign: segment, template, preview
03

A segment counts people after every condition

“Confirmed, not arrived at the desk yet” — a segment like this is built step by step. After each condition you see how many people remain and how many that very condition cut. A saved segment is a set of conditions, not a list: it is recounted before every send.

  • Conditions on registration and payment dates, payment state, desk arrival, zone scans
  • Specific people are added or excluded on top of the conditions
  • The same builder serves emails, pushes and survey audiences
The segment builder “Confirmed, not arrived yet”: condition steps and the head count after each
04

The push goes at 08:55 event time, the email — from your address

The “Doors open at nine” push is scheduled for the summit’s first morning, 08:55 Vienna time, with a text for each language. While it waits, it can be edited, moved, sent right away or cancelled. A failed send stays in the list with its reason and can be retried.

  • Both emails and pushes are scheduled to a day and hour on the event’s clock
  • A send keeps the segment conditions and the head count at the moment it went out
  • The organization’s own mail: its SendPulse account is checked before it is saved
The scheduled “Doors open at nine” push: 14 December, 08:55 on the event clock, English and Ukrainian texts, 60 people · 60 devices, the “Move”, “Send now” and “Cancel” actions
05

A delivery status for each person

Sent, not delivered, deliberately not sent. A server bounce — with the reason. Unsubscribed from the event’s or the organization’s campaigns — the system remembers.

  • The message log — on the application card too
  • Resend from the card
  • Unsubscribes at event and organization level
The email log with delivery statuses and reasons
06

A transfer push from the run card, text already written

The Danube Coaches bus leaves in half an hour. The bell on the run card opens a push from a template: the recipients are this run’s passengers, the trip code and time are already filled in. Each passenger gets it in their phone’s language, and the delivery result shows for every device.

  • Seven starter templates: transfer, meals, hotel check-in, survey, programme, programme change, announcement
  • Organization and event templates have versions — a newer one is pulled in with one tap
  • “Remind” on a meal slot, “Notify guests” at a hotel, “Push to the audience” in the programme
Example of a push from the “Transfer” template
07

A pass in Apple and Google Wallet

It arrives in the confirmation email. The pass holds the event, dates, venue, name, category, badge group, QR, photo, the event’s colour and logo. No contacts or documents in it.

  • Data changed — the pass updates itself
  • Badge reissued — the old pass is voided
  • The same QR as on the badge and in the app

We’ll show emails on your event

Your templates, your languages, your sender — we show it on a 30-minute demo call.

A 30-minute demo

Tell us about your event — we’ll show it on yours

A demo is a 30-minute call with the team that develops Aditum. Not slides but your scenario: we set up categories, approvals, zones and desks for your event.

  1. Fill in the form: event type, number of participants, a few words about it
  2. Within one business day we email you to agree a time
  3. On the call we show Aditum configured for your event and answer your questions
Or write directly [email protected]
Phone
We’ll call if the email gets lost
By submitting you agree to the privacy policy.