October 22, 2026 | 10 min read
Short answers to the questions organizers ask most often about confirmation emails and other registration messages in Eventact. Each answer links to the guide that covers the topic in full. To get started with messages, see Sending Messages to Registrants.
Click Messages in the Registration section toolbar and create a message, or edit an existing one. Write the subject and body in the editor or as raw HTML, and add dynamic fields to personalize it. Then set a rule to send it automatically - usually on the New Registration trigger. See How to Create a New Message.
The buyer. The same confirmation template is used for single registrants and group orders; it is addressed to the orderer, and its registration summary lists the number of tickets and the participants' names. You can:
A different personal email per attendee isn't possible in this model. If each attendee needs their own confirmation, have each person register individually.
Create a separate confirmation for free registrants and add conditions to both messages, so free registrants get only their message and paying registrants only theirs. Test both cases - a free and a paid registration - to confirm each gets just the right email. See Message Triggers.
Not reliably. One group registrant can order both kinds, so there is no way to decide which message to send. Either split the event into two forms - for example one for the conference and one for the free exhibition - or write one message that covers both cases. Free tickets usually work better as a simple individual registration than as a group form.
Yes. Define a version of the message for each language. When the trigger fires, Eventact picks the version that matches the registrant's registration language, and uses the event's primary language if there is no version for it. See Multilingual Support.
Yes. One message can have Email, SMS, and WhatsApp versions, and the automation rule decides which channels to use - you don't need a second automation. The versions don't synchronize, so check the other tabs after you edit the email, and keep SMS short: longer texts use more SMS credits. See Using Messages in Automated Processes and How Much It Costs to Send an SMS.
Open the registrant in the back office and click History. It lists every message sent to them and whether it was received. To review every outgoing message, add a BCC address to the message settings and Eventact sends a copy there. See Troubleshooting.
Dynamic fields are placeholders that Eventact replaces with each recipient's data when the message is sent -
for example {Contact.FullName}. In the message editor, open the Fields menu,
choose a group (Contact, Registration, Arrival, Form, Participant, or Project), and click the field; it is
added at the cursor. The same fields work in form page headers, receipts and invoices, and reports. See
Message Fields.
Exactly as the Fields menu shows them, spaces included - for example
{Registration.Accept Decline Link} or {Arrival.Ticket Download}. The safest way is to
insert fields from the Fields menu instead of typing them, then send a test message to yourself.
Insert {Arrival.Ticket Download} from the Arrival group of the Fields menu - for example "Download
and print your ticket: {Arrival.Ticket Download}". In an email it appears as a link to the
registrant's ticket page; in an SMS it is the plain link. If the registrant ordered a ticket, the page shows
that ticket; otherwise it shows a general ticket for the registration.
Yes. Store the link in a field of the registration - updated via the API or a file import - and insert that field in the message. You can't control when the value arrives, so don't rely on it being there when the automatic confirmation goes out. Send the confirmation as usual, then send a bulk reminder with the personal link once the values are in place. See Importing Contact Data.
Add the {Registration.Accept Decline Link} dynamic field to the invitation. The link opens a page
with two options, Confirmed and Decline, and the registrant's status updates as soon as they choose - no
manual work. Send a test message to yourself and click the link before sending. You can then set rules that
send follow-up messages only to those who confirmed. See How to Use It and
Registration Status Flags.
Because email and SMS security systems often "click" links automatically to check them. The selection page means only a real person's choice changes the status, so scanners can't mark registrants as Confirmed or Declined. See Key Advantages.
Open a message template, click Fields > Invitation, and select the new event. A field such
as {Invitation.Registration - Global Innovation Summit 2026 - Registration} is added, giving each
recipient a personal link to register. Send the message to the audience of the previous event or to a list of
contacts. The Invitation menu lists only future events that are open for registration. See
Invite Past Attendees to a New Event.
Create the questionnaire as a registration form that is open for registration. Then add a message in Registration > Messages and insert that form's field from the Invitation group of the Fields menu - it gives each recipient a personal link to the form. Test the link with one registrant before sending to everyone.
It depends on how many recipients you expect to register. Mailing systems usually give better open and click statistics, and sending through Eventact requires loading the invitee list. If few recipients will register - say 100 out of 10,000 - use your mailing system. The higher the expected ratio, and if you want RSVP with automatic identification of invitees, the more it pays to send through Eventact.
In Registration, click Messages and then Automatic Messages. Choose the trigger - the event that sends the message - and add conditions if needed, such as the registrant's country or ticket. A message can have several triggers, and it is sent only when all its conditions are met. See Message Triggers.
New Registration, Paid With Credit Card, New Pending Registration, Update Registration, Cancel Registration, Arrived, Confirmed, Declined, and three time-based triggers: Scheduled Time, Night Before, and Week Before. When a registration is completed, one of New Registration, New Pending Registration, or Update Registration fires; Paid With Credit Card fires in addition after a successful online card payment. See Available Eventact Triggers.
New Pending Registration, not New Registration. It also fires for registrations that need manual approval. If a confirmation should reach registrants who chose an offline payment method, add New Pending Registration to the message's rule - a condition on the payment method is usually unnecessary.
Yes. Use the Week Before trigger (seven days before the event starts), Night Before (about 24 hours before), or Scheduled Time for a specific date and time.
Click Registrants, select the recipients, and choose Bulk Actions > Quick Send and the message template. Choose to send only to those who haven't received the message yet, so a second batch doesn't reach the same people. Use Send Message... instead to preview the message first. See Sending Messages to Registrants.
Eventact emails the event's registration managers when a form crosses 10, 100, 500, and 1,000 registrations, and above that each time the count doubles. The count includes all valid registrations of the form, so an old form can still announce a milestone. To stop receiving them, remove yourself from the event's registration managers in Registration > Overview > Project Managers. This also stops block status emails; it doesn't affect emails from registrants.
No, as long as the template's Message Purpose is Transactional. Transactional messages - registration confirmations, payment receipts, and tax invoices - have no unsubscribe link and are sent even to contacts who opted out. Promotional, engagement, and operational messages include the link and aren't sent to contacts who opted out of them. See Message Purpose: Sending & Suppression Rules.
It is treated as Event Promotional: it includes an unsubscribe link and isn't sent to contacts who opted out of promotional emails. Review older templates and set confirmation and receipt templates to Transactional, or they won't reach those contacts. Don't mark promotional emails as Transactional - that removes the unsubscribe option and breaks anti-spam rules.
The footer tells recipients why they got the email and links to MyAccount, where they manage their email preferences; on non-transactional emails it sits next to the unsubscribe link. It can be turned off per company with the Enable User portal option in Company > Settings > Compliance, but we don't recommend it: recipients who can't remove themselves report spam, which hurts delivery of all your emails. See How Unsubscribe Works in Eventact.
No. Email opt-outs apply only to email. SMS has a separate Block SMS switch, which only Transactional and Authentication messages bypass, and WhatsApp opt-outs are handled within WhatsApp. Email opt-outs apply across all events of your company account.
Your own organization's address - such as registration@ your domain, or a separate address per event - so registrants recognize you and can reply. Avoid do-not-reply addresses, especially from another domain: they block replies and can send emails to spam. Set the address in the project settings under Email and Phone and click Test. See Custom Domain for Emails.
Yes. Add include:_spf.eventact.com to your domain's SPF record (the Test button gives you the
updated record), add the DKIM record shown under Company > Email, and check with your IT team that a DMARC
record exists. Gmail and Yahoo require all three from bulk senders. DNS changes can take 24-48 hours. See
Using DKIM.
Open the registrant's History to see whether the message was sent and received. If it was, ask them to check their spam folder. If it wasn't, check the message's trigger and conditions, and that its Message Purpose is Transactional - a promotional template isn't sent to contacts who opted out.
Offline payment methods fire New Pending Registration instead. Add that trigger to the message's rule.
The trigger fires only after a successful online credit card payment during registration. Check in the registrant's record that the payment succeeded and which payment method was used - offline methods fire New Pending Registration. If the message has a condition, such as a ticket, test the same condition with the New Registration trigger; if it works there, contact Eventact Support.
Check the registrant's name in the Registrants list. If it is correct there, the email you're looking at was sent before the correction. Send the confirmation again if the registrant needs an updated copy.
A registrant reached the end of the form without arriving at a valid final page - usually because the display conditions of all the remaining pages were false for them. They saw an error page and didn't get the confirmation. The email names the form and the registration ID: open that registrant and check which page conditions failed.
The calendar file uses the event's time zone, not the registrant's location. Set the event's time zone, country, and venue in the event settings. To investigate, ask a registrant to forward the confirmation they received.
Meanwhile, send the registrant the email from your own mailbox. Report the problem to Eventact Support with any blocklist where Eventact was found and the IP address that was tested, so the check can be repeated.
Still stuck? Contact Eventact Support. Read more about Eventact Event Registration