Design a clear completion state
Open Form Settings → After submit. Choose the confirmation content or redirect and configure the additional options you need. Keep the primary result easy to understand: what was received and what happens next.
Available settings include submission details, answer summary, a fill-again action, respondent email and a downloadable follow-up file. Show only the information appropriate for the visitor.
Use token chips offered by the editor rather than guessing token syntax. Examples include {{submission:id}}, {{form:title}} and {{field:email}}. Field tokens refer to stable keys.
Configure email
Check the site's email transport and sender identity. Choose the email field used for the respondent and write a concise subject/body. Submit a real QA request and verify delivery to the expected mailbox; a saved template does not prove that SMTP is configured.
Avoid including private answers in a public redirect URL. Use an approved destination and verify the result signed out as well as signed in.
When custom logic changes the response
An approved C# script can set ctx.Response.SuccessMessage for one submit response. That does not permanently change the form's configured confirmation. The C# demo shows a calculated reference and total in this way.
For server actions such as webhooks, approvals or external inserts, review their execution history separately. See Workflows and C# scripting.