Test Form confirmations and notifications

Set the submit message and verify any configured team notification, visitor confirmation, or redirect with a realistic submission.

Follow the steps.

Use your own accurate details and check the result as you go. You can return to the relevant Website editor to make corrections.

  1. Write the success message

    Confirm that the submit button has a useful label and the success message says the response was received without promising an immediate reply or confirmed transaction.

  2. Check configured actions

    Review the stored submission action and any enabled team notification, visitor confirmation, or redirect. Use a valid notification address and a supported safe redirect.

  3. Submit realistic data

    Use an address and values you are permitted to test. Complete the Form from the Page or preview where visitors will use it.

  4. Verify every destination

    Confirm the submission appears for the selected Form. Check the success state and separately verify any external message or redirect before relying on it.

Illustrative example

What a useful result looks like

The result
The visitor sees confirmation and the response appears under the Form.
What to check
Verify the saved response first, then check any configured notification as a separate result.

Adapt the example to your Website and review the result before moving to the next task.

Say only what the submit action proves

The default success state can acknowledge receipt. It should not say that a team member replied, a payment completed, an appointment was reserved, or a request was accepted unless another relevant Website tool has actually confirmed that result.

Treat external delivery as a separate check

A valid configuration can still depend on external delivery and provider setup. Verify the exact recipient, visitor address, message content, and redirect destination with an appropriate test.

  • Keep notification recipients current.
  • Make visitor confirmation conditional on a usable email field.
  • Use an HTTPS URL or Website path for a configured redirect.
  • Retest after changing the Form fields or submit actions.

Before you continue

A saved notification or confirmation setting is configuration, not evidence that an external message was delivered.

Make the next change with a clear result in mind.