---
title: "Form Communications Overview"
slug: "form-communications"
updated: 2026-08-03T20:20:06Z
published: 2026-08-03T20:20:06Z
canonical: "knowledge.technolutions.net/form-communications"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Form Communications Overview

**Form communications** are delivered when a registrant performs some action, like submitting a [form](/v1/docs/forms-overview), or when qualifying milestones occur, like the approach of a deadline or the cancellation of an event.

With form communications, you can choose what event triggers the delivery of the communication, create a recipient list to narrow the list of potential recipients, personalize content with merge fields, and track or redirect form traffic. While email and SMS are the most common methods chosen for form communications, you can choose from any of the [Deliver methods](/v1/docs/deliver-new-mailing-settings-1#method).

> [!NOTE]
> 💡 Form communications are very closely related to [event communications](/v1/docs/event-communications-overview).

## Email form communications

Create and test email messages and confirmation pages that respond to form activity. Configure recipients and content, use merge fields, and control what appears in an email or on a Slate-hosted confirmation page.

📖 [Email Form Communications](/v1/docs/email-form-communications)

## SMS form communications

Configure and test text messages that respond to form activity. Review your Slate Credit settings before using this method.

📖 [SMS Form Communications](/v1/docs/sms-form-communications)

## Choosing triggers and groups

You can choose when a form or event communication is sent and which registrations qualify. Options include registration, update, waitlist, cancellation, deadline, and time-based triggers.

📖 [Form and Event Communications Triggers & Groups](/v1/docs/form-and-event-communications-triggers-groups)

## Adding payment receipt details

Include a prebuilt payment receipt or selected payment details in a form communication.

📖 [Form Payment Receipt Merge Fields](/v1/docs/form-payment-receipt-merge-fields)

## Avoiding form spam submissions

Reduce bot-generated submissions with submission conditions, then use retention policies to remove records identified as spam.

📖 [Avoiding Form Spam Submissions](/v1/docs/avoiding-form-spam-submissions)

## Using form and event merge fields

Personalize communications with standard form merge fields and related event data. Format dates and times for display in the message.

📖 [Form and Event Communications Merge Fields](/v1/docs/form-and-event-communications-merge-fields-1)

## Conditionally sending communications

Add filters to send a communication only to registrations that meet defined criteria. Add exports when the message needs merge fields beyond the standard options.

📖 [Conditionally Send Form and Event Communications](/v1/docs/adding-exports-and-filters-on-form-communications)

## Redirecting form pages

Redirect visitors to another Slate page or an external URL after they submit a form—or as soon as they open it.

📖 [Redirecting Form Pages](/v1/docs/redirecting-form-pages)

## Capturing UTM parameters

Add UTM parameters to form links, capture them with each submission, and export the values to measure where form traffic originated.

📖 [Capturing UTM Parameters in Forms](/v1/docs/capturing-utm-parameters-in-forms)