End step

Use End to choose what the customer sees when an onboarding or loop reaches its final client-facing step: a custom confirmation message or a redirect to another destination.

#1. Add an End step

1. Open your onboarding or loop process.
2. Select + immediately before the outcome on the path where the customer-facing flow should end. End cannot be inserted before another processing step.
3. In Add steps, AI Agents and services → Steps, select End. Use Search if needed.
4. In New end step, choose Add custom message or Add redirect link.

End is available in Onboarding and Loop processes. It controls the final customer-facing response; it does not itself approve, reject or hold the customer, or calculate a score.

#2. Choose the final response

#Show a custom message

Use this when the customer should remain on the completion screen.

1. Select Add custom message.
2. Enter the text in Custom message.
3. Use the editor toolbar for bold, italic, underline or links where useful.
4. Select Save.
5. Close and reopen End to confirm the message persisted.

An empty message cannot be saved. The sample text shown in an empty editor is a placeholder, not your saved confirmation.

#Redirect to another destination

Use this when the customer should leave the completion page for another destination.

1. Select Add redirect link.
2. Enter the complete destination in Redirect link.
3. Select Save.
4. Close and reopen End to confirm the address persisted.

For a website, enter the complete address starting with http:// or https://, for example https://example.com. A bare domain such as example.com is not accepted; Save remains disabled.

For email, use mailto:address@example.com; for a phone number, use tel:+ followed by the country calling code and the phone number. These links ask the customer's device to open its configured email or calling application. They do not send an email or place a call automatically. The application may require setup or sign-in, so check the result on the intended device and browser.

The message and address above are independent examples. Use wording and a destination appropriate to your workflow.

#3. Publish and check the result

1. Reopen End and check the saved response on the intended path.
2. Open Deployment and publish the process changes.
3. Start a fresh session using the process's normal trigger.
4. Complete the required steps and reach the path containing End.
5. Check the result in the browser and confirm the execution in Runs history.

Saving End updates the process configuration; it does not publish a new version. Start a fresh session after publication when checking your latest changes.

The example message describes a scoring result from the example flow. End only displays the text: the preceding rules must establish any result your message claims.

For the wider testing procedure, see internal page.

#End vs. an outcome

End configures the customer's final response. An outcome is also used to connect another process. Choose the feature that matches your goal:

• To display a final message or redirect, configure End.
• To start a separate downstream process from an outcome, see internal page.
• To call a child process and use its result before the parent continues, see internal page.

#Troubleshooting

• End is missing: check that the process is an Onboarding or Loop process and that you have permission to edit it.
• Save is disabled: enter a non-empty custom message or a valid redirect address with a supported protocol.
• The previous response appears: reopen End, confirm what was saved, publish the changes and start a fresh session.
• A redirect replaced the message: the two options are alternatives. Select Add custom message and save the intended text to switch back.
• The customer never reaches the final response: inspect the path, earlier waiting steps and run status. A saved End configuration does not prove the execution reached it.
• The browser leaves the form but the destination does not work: check the address and destination separately. For mailto: or tel:, check the customer's configured application.

#Related guides

• internal page — choose which path reaches End.
• internal page — publish and verify a process run.
• internal page — inspect execution results.
• internal page — connect processes through outcomes.