In order to be able to use these settings optimally, advanced technical understanding and knowledge of HTML and CSS are helpful.
In addition to the email sending address, it is also possible to specify a “reply to” address in the form and newsletter. This can prevent an email from being automatically classified as “SPAM” by a recipient server and therefore not being delivered at all. It is recommended to enter an email address in the sender address that can actually originate from the configured email server.
Various placeholders can be used in the email configuration. These allow you to personalize the email subject and text. Placeholders can be used in the following configuration fields of the form:
- Administrative email: Subject
- Administrative email: Text
- Confirmation email: Subject
- Confirmation email: Text
The following placeholders are available:
- %(content.Title) for the title of the form (or event)
- %(formdata) for a table with all form entries
- %(date) for the date the email was sent
For events with online booking, the following placeholders can also be used:
- %(event.time) for the date/time of the booked event
- %(event.note) for the optional note for the booked event, i.e., the value of the individual note or description input field for the online booking
- %(event.type) for the value of the event type or number input field
- %(event.waitlist.info) for information about the waiting list (if necessary)
Furthermore, the user entries of all configured form fields can be displayed in the email via the field name. For example, if a first name field has been configured for the form, this can be output with %(first name).
The use of placeholders is particularly recommended in the subject line of administrative emails. When used correctly, emails sent via the form can be much more easily distinguished in the administrative mailbox.
For online bookings, the following configuration is recommended for administrative email: Subject, e.g.:
Registration of %(Firstname) %(Lastname) for %(content.Title) %(event.note) (%(event.time))
This requires that the first name and last name fields have been configured in the form.
Let's assume, for example, that there is a series of events entitled Choir Evening. Depending on the date, these events are held in different rooms. The room could be stored in the Individual Note or Description field. The emails would then have the following subject lines, for example:
Registration of John Doe for Choir Evening [large hall] (10/22/2020 6:00 p.m.)
Registration from Jane Doe for Choir Evening [small room] (10/29/2020 7:00 p.m.)
The additional information %(event.note) and %(event.time) makes it easy to identify bookings for different days or rooms in the mailbox.