The page's "Post-Submission" tab sets what happens after a Person submits a form: where they go next, and the texts and emails that follow.

Redirect To

The "Redirect To" section sets where a supporter goes after a successful submission. Most options can show share icons that ask the supporter to invite their friends.

Custom Follow-Up Page (Default)

By default, the supporter goes to a customizable thank you page at the Page's URL with /thanks added. On a "Schedule a Call" page, this option goes to the call confirmation page instead.

To edit it, open the page's "Post-Submission" tab and click the arrow next to "Redirect To". Choose "Custom Follow-Up Page (Default)". Edit the text in "Follow-Up Page Content". Click "Save Redirect To". The content can use merge tags from the Person's profile and from the form they submitted.

Conditional

Conditional redirects send each supporter to a different page based on a filter, so you can chain pages into a sequence (for example sign up, then complete a profile, then schedule a call). The conditions are checked top to bottom. A Person who matches none of them goes to the default Custom Follow-Up page.

Share Overlay

The share overlay shows a window with share buttons. The supporter stays on the page.

Custom URL

Redirect to any URL. The URL can hold merge tags, for example ?amount={{ form-submission.donation-amount }}. Add | url_encode to a value with spaces or symbols, for example {{ form-submission.city | url_encode }}. If the URL is part of your Website, you can show a "flash message" at the top of that page.

Push Notification Prompt

With the Custom Follow-Up Page redirect, you can enable Show Push Notification Prompt to show a push notification opt-in on the thank you page. The prompt shows instructions for each device. On iPhone and iPad, push notifications require adding the site to the home screen, and the prompt guides users through it. See Push Notifications.

Text Confirmation

Enable the text confirmation to send a customized follow-up text from the phone number of the person's chapter within the page's scope. It goes only to people with SMS permission, which a form gives by default. You can personalize the text with Merge Tags and add attachments, such as a contact card with your organization's number, name, and logo.

📘

Note: Text confirmations are only sent when a submission creates a new record. When 'Store Multiple Submissions' is off, a new submission from the same person updates that person's previous submission and sends no text confirmation.

Who receives text: Everyone who submits the form, or only People who match a filter.

Delay: Send the text immediately, or after a delay.

Constrain to texting hours: Holds the text until texting hours. The texting hours are set in the Chapter Structure settings of your root Organization. If you set your texting hours to 9AM to 5PM, supporters who submit the form at 1AM, will not receive the text confirmation until 9AM.

Email Confirmation

Enable the email confirmation to send a personalized email to people who submit the form and have an email address. "Who Receives Email" can be "Anyone who submits form" or "Anyone matching filter who submits form". You set the content, sender, subject line, and email wrapper like any other email.

📘

Note: Email confirmations are only sent when a submission creates a new record. When 'Store Multiple Submissions' is off, a new submission from the same person updates that person's previous submission and sends no email confirmation.

Admin Notification Email

Enable admin notification emails to send an email to any valid email address after a Person submits a form, for example to tell an organizer about each new dues-paying member.

The admin notification email requires a sender, an email wrapper, at least one recipient email address, and either a subject line or body content. If both the subject line and body are left blank, the email will not be sent. You can use this with conditional merge tags to send the notification only in some cases.

Using Merge Tags

Use {{ form-submission.field-name }} to include a form answer, for example {{ form-submission.employer }}. It works in texts, emails, the follow-up page, and a custom URL, and it gives the answer labels. This is in addition to the default merge tags available within the text editor.

Merge tags also work on "Email Custom Target" pages.