# Form completion, thank-you messages, and redirects

You'll see how a form's submission actions and final screen fit together, so you can show a thank-you message or send visitors to another page.

Available on the Grow, Scale, and Pro plans.

After someone submits your form, you can thank them in the widget or send them to another page. The form's submission actions handle their data, while a separate post-submit path decides what they see next.

## What happens when someone submits

A form ends the ordinary path in its parent flow. Submitting it won't continue through steps below that form. Instead, the canvas shows a separate path under **Post-Submit Actions For This Form**.

The form's **Actions** tab controls the submission itself, such as adding a contact to a list or sending a webhook.

![Opt-in form actions editor with the subscriber form preview](https://rightmessage.com/help/screens/forms-actions.light.webp)

These are separate jobs. For example, [WorkForge](https://workforge.rightmessage.com) could add a guide requester to its email platform, then show a message saying the guide is on its way. The email platform still needs to send the guide.

Adding a contact or updating a provider record needs a supported connection. A webhook needs access on your plan and an endpoint to receive it. The choices you see depend on your connection and form configuration.

## Where the next steps belong

Open the flow and find **Post-Submit Actions For This Form** beneath the form node. Keep its default **Message** to confirm the submission in the widget, or replace it with **Redirect** to send the visitor elsewhere.

If you need a data update or routing decision after submission, put it before the message or redirect in this separate path. Both of those display choices end the path.

The editor allows supported data actions and routing here. It doesn't offer another **Form**, **Offer**, **Exit Flow**, or an asking **Question**. Ask any additional questions before the form, not below it in the ordinary path.

Forms are reusable. When you change submission or completion settings, check the other places that use the same form.

## A thank-you message stays in the widget

A **Message** displays rich text after submission and uses the widget's appearance. A new empty post-submit path starts with `Thank you!`. You can replace that wording in **Content**, including adding links.

![Submit Message editor containing the WorkForge guide confirmation](https://rightmessage.com/help/screens/flows-message-settings.light.webp)

A message ends the path. It doesn't send an email, start a countdown, or continue automatically to the next step. If you've placed a redirect below it, the message stops the visitor from reaching that redirect.

A link in the message lets the visitor choose when to leave. For more on its content, see the [Submit Message reference](https://rightmessage.com/help/flow-node-message).

## A redirect sends the visitor to another page

A **Redirect** sends the visitor to a thank-you page, booking page, or another destination. For an immediate redirect, replace the terminal message in the post-submit path with the redirect. Don't put it below the form in the ordinary parent path.

Choose a real page on your website, such as WorkForge's [contact page](https://workforge.rightmessage.com/contact.html). If you're sending someone to a booking page, the booking tool handles availability and appointments. Opening that page doesn't book an appointment for them.

Enter a full HTTP or HTTPS URL, or a path beginning with `/`. **Open in a new tab?** starts off. **Send subscriber data?** also starts off and appears only for an absolute HTTP or HTTPS URL. Use it only for a cross-domain destination that's meant to receive the visitor's context and runs the same RightMessage project.

The ordinary builder preview suppresses navigation. Test the redirect on your website through an authorized on-site test. RightMessage also blocks a destination equal to the current URL to prevent a redirect loop. The [Redirect reference](https://rightmessage.com/help/flow-node-redirect) explains the destination and forwarding rules.

## Check the submission and the next screen

Test both validation errors and a successful submission. Check the submitted email and mapped fields in your email platform, or check the receiving webhook endpoint. Then check the thank-you message or redirect.

A confirmation screen tells the visitor what happened in the form. Check the destination separately to confirm that an email was delivered or an appointment was booked. Previewing the form without submitting it won't test completion.

Use the [Form actions reference](https://rightmessage.com/help/form-actions-reference) for submission settings. When you're ready to try the whole form, follow [testing your changes](https://rightmessage.com/help/best-practices-for-testing).