• Frequency: Every fifteen minutes within seven days of the event end date.
• Recipients: Any Event Participant with a status of 03-Attended or 04-Confirmed with the Attendee Message Sent field set to No or is left blank and the Event is in the last seven days. If you chose Send to Heads and the Registrant is not a Head of Household, the Attendee and their household's Head of Household Contacts receive the message. If the Attendee is a Head of Household, only they receive the message.
• From/Reply To: The Event Primary Contact. If the Primary Contact does not have a valid email address, it uses the From field on the Message Template. If the Message Template does not have a valid email address, it uses mpsupport@acst.com and, we recommend changing the Email Address on the Template.
• Contents: An event-specific email giving attendees additional post-event information or follow-up (for example, presentation links, surveys, and so on).
• How to Stop: Remove the message from the Attendee Message field in the Event record.
• Method for sending: Platform.
• Logging in Messages: The template message is copied. Recipients are logged. Event Participant Record is set to Yes for Attendee Message Sent.
• Configuration Settings: None.
• Merge Fields Supported:
  • Subject & Body: [Nickname] and [Event_Title].
  • Body only: [Notes], [Email_Address], [Mobile_Phone], [Event_Title], [Meeting_Instructions], [Congregation_Name], [Location_Name], and [Event_Start_Date].
• Initial Configuration: Create a message and set it as the Attendee Message on the Event record.
• Optional Configuration: None.
• Notes: If the participant used an email to register through the Portal, the notification sends to that email. The email is then stored in event participant notes.
  Note: It doesn't matter how the registrant was added to the event. They will be sent this email if there is an email on file.

Event Fields

See Creating Events > Event Fields > Notification Settings.

Other Notes

• Event Series: Each Event is separate and each Event can have its own Attendee Message.
  • An Attendee Message sends for each Event in the series with an Attendee Message set on the specific Event record.
  • If you allow registration on any Event in a series, have Register into Series set to Yes, and you don't want to send multiple Attendee Messages, then you can just set the Attendee Message value on the last Event in the series.
• Message Templates: You can use the same Message template for various Events. Each Event does not need its own Message template, although it can if you want.
  • You do not need to use a template to send the Message.
  • You can't send attachments with the Message.
  • You can send links to publicly downloadable files.
• Recent Events Only: Messages do not send for Events with End Dates more than seven days in the past. If you add a Participant more than seven days after the Event End Date, an Attendee Message does not send.
• Event Primary Contact: Messages do not send if the Primary Contact does not have an email address.
• Default Contact: If the Attendee is the Default Contact, the message sends to the email they provided during registration. This displays in the Notes field of the Event Participant record when there is information in the Email and Address1 fields.
  • If Send to Heads is set to Yes and the Event Participant record is the Default Contact, the system can't identify a Head of Household, so it doesn't send a Head of Household email.
  • We recommend reviewing and cleaning up and clearing out the Event Participant > 1. Reassign Participant view daily. Or, in the Event record, set Force Login to Yes to require registrants to log in to register and reduce Default Contacts.
• No Email: Messages do not send unless there is an email entered in the Event Participant's Contact record. If the Attendee did not provide an email during registration, they will not receive a message.