Sample Event Form Communication
- 04 Apr 2024
- 2 minute read
- Print
- DarkLight
- PDF
Sample Event Form Communication
- Updated 04 Apr 2024
- 2 minute read
- Print
- DarkLight
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The following chart displays a sample communication campaign for a campus tour event template and explains fields and special triggers that may be employed.
First Entry
Communication 1
Trigger | Group |
|---|---|
Upon Registration | Direct Entry Only (Confirmation page Only) |
Sample Message
Thank you for registering for {{Form-Title}} on {{Form-Date-Time}}.
We have sent a confirmation email to {{sys-email}} which contains your itinerary and instructions to update your registration information.
We look forward to meeting you!
✨ TipUse the {{Form-Link}} merge field to create the Edit Registration link.
Communication 2
Trigger | Group |
|---|---|
Upon Registration or Update | Direct Entry Only (Email Only) |
Sample Message
Dear {{sys-first}},
We look forward to meeting you on {{Form-Date}}!
Your campus tour leaves from the Admissions Office. Click here for directions. Here are the activities that you selected:
....
To update or cancel your registration, use this link: {{Form-Link}} by {{Form-Deadline}}.
Sincerely,
Slate University Office of Admissions
✨ TipIf an event will rarely have registrations submitted administratively, and the same registration email should be sent, simply use the event's public URL to fill out the registration form. This will trigger the Direct Entry communication.
Registrant Re-Entry
Communication 1
Trigger | Group |
|---|---|
Upon Update | Direct Entry Only (Confirmation page Only) |
Sample Message
Thank you for updating your registration!
Your updated itinerary has been sent to {{sys-email}}.
Communication 2
Trigger | Group |
|---|---|
Upon Cancellation | No Group Option |
Sample Message
Thank you for letting us know that your plans have changed. We hope another day will fit your schedule.
Please view our campus visit schedule here.Pre Event
Trigger | Group |
|---|---|
Hours before Event | Hours - 24 |
Sample Message
Dear {{sys-first}},
We are looking forward to meeting you tomorrow at {{Form-Time}}!
As a reminder, your campus tour will meet at the admissions office. For detailed directions, click here.
If you need to update or cancel, or if you have any questions, please call us at 203-123-4567.
Sincerely,
Slate University Office of AdmissionsPost Event
Communication 1
Trigger | Group |
|---|---|
Hours after Event | Hours - Upon 24 | Group - Attendees |
Sample Message
Dear {{sys-first}},
It was great meeting you yesterday! We hope you had an awesome time on our campus and value any feedback you may have. Please take our brief survey:
{{form-survey-link}}.
Stay in the loop by liking us on Facebook and following us on Twitter. In addition to posting important application deadline information, we also post pictures of current students participating in our many fun campus events!
We hope to see you again soon!
Sincerely,
Slate University Office of AdmissionsCommunication 2
Trigger | Group |
|---|---|
Hours after Event | Hours - Upon 24 | Group - No Shows |
Sample Message
Dear {{sys-first}},
We’re sorry that you weren’t able to attend {{Form-Title}} yesterday.
We hope another day will fit your schedule. Please view our campus visit schedule here.
Sincerely,
Slate University Office of AdmissionsCustom Communications
A custom communication campaign may be created using different combinations of triggers and groups. Here are some other common communication scenarios:
Attendance is not Captured
If registrants are not marked as Attendees or No Shows, and all event registrants are considered attendees
Trigger | Group |
|---|---|
Hours after Event | Group - All Registrants |
No Preregistration
If event registration occurs administratively after the event, (e.g. contact cards collected at a high school visit
Trigger | Group |
|---|---|
Upon Registration | Admin Entry Only (including post-deadline) |
Send Emails to Slate Users
Event communications can be sent to people other than the event registrant.
Instead of using the merge field {{sys-email}} in the Recipient field, enter a hard-coded email address or include a different merge field, such as {{Form-User-Email}} to send an email to the Slate user associated with the event.
Was this article helpful?
