Every event sends thousands of messages. Make every one count.

Every event has the same lifecycle backbone: registration confirmation with the attendee's ticket, approval and rejection messages for events that use approval workflows, event reminders before the day, and a thank-you message after the event ends. All of these are configurable templates that draw from the live registration data, triggered by attendee state in the platform.

Yes. The campaign engine includes advanced filters that target by ticket type, registration status, attendee type, sessions selected, custom form fields, tags, and any combination of those. You define a segment, compose the message in the visual builder, and send. Filters can be saved and reused.

Yes. Every field on the registration form becomes a variable you can drop into any message — first name, ticket type, sessions selected, dietary preferences, merchandise add-ons, the price paid, anything captured at registration. The same email template renders differently for each attendee based on what they registered for.

Yes. Connect your sending domain through DNS records (SPF, DKIM, DMARC) and all communications go out under your name and domain reputation. The attendee sees emails from your organization, not from Eventtia. This also improves deliverability since you build sender trust under your own brand.

Yes. SMS uses the same targeting and segmentation engine as email. You can trigger SMS for time-sensitive moments — day-of reminders, last-minute changes, on-site notifications — to the same audience segments you'd target by email. Phone numbers captured at registration are available for SMS routing automatically.

Yes, for registration confirmations. When the attendee provides a phone number on the registration form, Eventtia delivers the confirmation through WhatsApp with the ticket and QR code attached. WhatsApp delivery is currently scoped to confirmation flows; broader WhatsApp campaign capabilities are on the roadmap.

Delivery rate, bounce rate, open rate, and click rate per campaign. Error logs detail why specific messages failed (invalid address, hard bounce, soft bounce, ISP rejection). Automatic retries handle transient failures, and the retry results are logged so you can see what eventually delivered. All metrics are available in real time as the send progresses.

Yes. Every message uses a visual editor — drag-and-drop composition with no HTML required. You control colors, typography, logo placement, layout, and content. Save designs as templates and reuse across events. The branded design applies across email, ticket attachments, and confirmation flows.

Yes. The same multilingual layer that runs across the platform applies to communications. Each lifecycle template can be defined in multiple languages, and the attendee receives the version that matches their browser, region, or registration preference. Campaign messages also support multilingual variants.

The platform attempts automatic retries for transient failures (server unavailable, temporary throttling). Persistent failures are logged with the specific reason — invalid address, hard bounce, blocked by recipient — so the organizer can investigate or update the contact. The failure log is available per send and per attendee.

Yes. Communications are tied to the same attendee records that drive registration, check-in, and analytics. Approve someone in the dashboard, they receive the approval email automatically. Cancel a session, the affected attendees get notified. The communications layer is one integrated piece of the event lifecycle, not a separate tool.