---
title: "Reader Form Communications"
slug: "reader-form-communications"
status: "new"
updated: 2026-07-30T16:52:51Z
published: 2026-07-30T16:52:51Z
canonical: "knowledge.technolutions.net/reader-form-communications"
---

> ## 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.

# Reader Form Communications

> [!TIP]
> 🏔️ Summit 2026 Feature
> 
> Send communications immediately when a reader form is submitted.

Use Reader [form communications](/v1/docs/form-communications) to send a message when a [Reader-scoped form](/v1/docs/workflow-review-forms) is submitted in the [Reader](/v1/docs/reader-overview). These communications are useful for time-sensitive confirmations, next steps, and internal notifications tied directly to review activity.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/New communication from reader scoped form.png)

## Creating a reader form communication

1. Go to **Forms**.
2. Open the Reader-scoped form that should trigger a communication.
3. Select **Edit Communications**.
4. Select **New Mailing**.
5. In **New Mailing**, enter a name.
6. Configure the trigger, group, status, delivery method, UTM tracking, and timeline settings.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Configuring communication details.png)
7. Select **Save**.
8. Select **Edit Message**.
9. Configure the sender, recipient, subject, and message body.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/New Reader review form communication(1).png)
10. Select **Save**.
11. Select **Submit Form Test** to open the form in communications testing mode.
12. Submit a test reader form and confirm that the message is delivered as expected.

> [!NOTE]
> 💡 Communications send only when the Reader form is submitted. Saving a draft does not trigger a communication.

## Targeting recipients and conditions

Use the **Recipient** field to decide who receives the message. Enter a fixed email address for a fixed recipient, or insert a merge field when the recipient should come from the form context. The message editor lists form user and form submitter fields, such as `{{Form-User-Email}}` and `{{Form-Submitter-Email}}`.

Select **Edit Conditions** when the communication should send only for certain reader form submissions. The condition builder can use reader form values and Reader Bin context, including the current bin and next bin.

📖 [Form access and submission conditions](/v1/docs/access-and-submission-conditions)

> [!WARNING]
> 📝 Note
> 
> The **Next Reader** selected at the bottom of a Reader review form is not listed as a default merge field in the message editor. If a communication should notify a next assigned reader, verify the recipient merge field or database-specific source before activating the mailing.

## Examples

**Admissions 🪪**

Send a notification to a committee chair when a faculty review form is submitted.

**Student Success 🎓**

Send a confirmation to an advisor after a case review form is submitted.

**Advancement 🤝**

Notify a gift officer when a prospect review form is completed.