Form Communications

A customized confirmation page and email communications may be automatically configured to send when a form is submitted.

Configure the Mailing

Build and manage all post-form submission communications through the form management screen of a form.

  1. Click Forms in the top navigation bar.
  2. Select the appropriate form.
  3. Click Edit Communications
  4. Click New Mailing.
  5. Provide initial set up details for the communication:
    • Name - Provide a descriptive name for the communication
    • Trigger - Keep 'Upon registration or update' as the Trigger at this time.
    • Group - Keep 'Email + Confirmation Page' as the Group at this time.
    • Status - Keep the status Active.
    • Method - Keep Email as the Method.
    • UTM Tracking - Keep this set to Disabled.

Edit Message

Use the communication tools to build a mailing and confirmation page:

  • Edit Message - Click Edit Message to create the message form registrants will see.
  • Send Test Message / Submit Form Test - Once communication is built, use these buttons to test settings (If you are testing a mailing that has merge fields, you will need to use Submit Form Test to have the merge fields populate).

Use merge fields to customize the email message:



All of the fields from the form will appear in this list as merge fields. Place cursor in desired field and click a merge field from the list to add it to this location.

The name of the merge field is based on the export value for that field on the form. For example:

{{sys-email}} = sys:email

{{sys-preferred}} = sys:preferred

If Preferred Name ("sys-preferred") is used as merge field in the form communication, it is best practice to collect this data on a form as well.

  Common Questions

Merge fields that begin with “Form-“ generally should not be used in an inquiry form.

Email + Confirmation Page Group

A confirmation page message will appear on a webpage wrapped with institutional branding. Therefore, if using the Email + Confirmation Page group for the communication, it is not necessary to include header or footer images.

If emails should include institutional branding:

  • Make one communication using the Email only group that includes branding.
  • Make another communication for the Confirmation Page Only group and exclude branding. 

Communication Testing

When editing or viewing a mailing, you can test it with the following actions:

  • Send Test Message: This function sends a copy of the message to the specified recipient. However, no merge fields will have a value.
  • Submit Form Test: This function sends a copy of the message after completing the form or event registration.  Merge fields for values collected on the form will have a value. Merge fields that reference an actual registration, like Form-Share-Link or Form-Link, will not have a value.
  • Submit using a test record: The best way to test a form or event mailing is to submit an event registration using a test record. This causes Slate to send a message that has the relevant merge fields successfully populated.
Was this article helpful?
3 out of 15 found this helpful