Call to action

Call to action controls what happens after a feedback form ends—close the form, navigate inside your app, or redirect to a URL. Configure it when editing a Thank you screen (visible buttons) or an Exit form (silent action with no UI).

In the form builder, open Call to action → Configure on either panel type in the Thank you & Exit Section.

When to use

Send respondents to a pricing page, support article, or onboarding flow after submission
Navigate users inside your app (for example billing upgrade) when the form runs in your product
End disqualified branches silently via an exit form without showing a thank-you screen
Auto-dismiss or auto-redirect after a short delay on the thank-you screen

How it works

Enable call to action on a thank-you screen or exit form in the form editor.
Choose surfaces — set actions separately for In-App (form embedded in your product) and Shareable link (standalone form URL).
Respondent finishes or is routed — on a thank-you screen they see CTA buttons; on an exit form the form ends with no UI when a Logic jumps rule targets it.
Action runs — when call to action is enabled, the configured action executes (close, redirect, or in-app navigation). If call to action is not enabled on an exit form, the form still ends silently but no post-exit action runs.

If call to action is disabled on a thank-you screen, respondents see a single button using the Next button label (typically Close).

Configuration

Open your feedback form on the Form tab.
Edit a Thank you screen or Exit form in the Thank you & Exit Section.
Find Call to action and click Configure.
Turn on Enable call to action.
Set per-surface actions for In-App and Shareable link as needed.
Save the panel.

Surfaces

Surface	When it applies
In-App	Form runs inside your product via the Web or mobile SDK.
Shareable link	Form is opened as a standalone URL in a browser tab.

If a surface is not configured, the form falls back to Close form on that surface.

Actions

Each surface supports one action. Available options depend on the panel type and button (primary vs secondary):

Action	Description
Close form	Dismiss the form. Default when call to action is disabled or a surface is unset.
Navigate in app	Send respondents to a route inside your app. Available on In-App only—not on shareable links. Requires SDK integration — see Web SDK or Mobile SDK.
Open in same tab / in-app browser	Open a URL in the current tab or in-app browser.
Open in new tab / external browser	Open a URL in a new browser tab or the device browser. Not available on shareable links for exit form primary actions or secondary button actions.

For Navigate in app, enter a route such as onboarding/start or billing/upgrade. Your development team maps that route in the SDK integration.

For redirect actions, enter a valid http:// or https:// URL.

In-app external browser

On the In-App surface, Open in new tab / external browser may not work reliably in all application setups.

Thank you screen options

When call to action is enabled on a thank-you screen:

Option	Description
Primary button label	Text on the main CTA button. If unset, the Next button label is used.
Auto-trigger delay (ms)	Optional timer that fires the primary action automatically. Leave empty for manual-only.
Primary button actions	Per-surface action for the main button (In-App and Shareable link).
Secondary button	Optional second button with its own label (default: Close form) and per-surface actions.

Translate Primary button label and Secondary button label per language using the language tabs. Actions, URLs, routes, and auto-trigger settings are shared across languages. See Language Setup for multilingual forms.

Exit form options

Exit forms have no respondent-visible UI. When a logic jump routes here and call to action is enabled, the configured action fires on the matching surface:

Option	Description
Auto-trigger delay (ms)	Use 0 for an immediate silent action (this is also the default when left empty). Optional higher values delay the action.
Primary button actions	Per-surface action (In-App and Shareable link). No button labels—the exit form shows no screen.

Exit forms do not support a secondary button. If call to action is not enabled, the form still ends silently with no thank-you screen, but no post-exit redirect or navigation runs.

Examples

Thank you → upgrade page

Edit the thank-you screen → Call to action → enable.
Set Primary button label to Upgrade now.
In-App → Navigate in app → route billing/upgrade.
Shareable link → Open in same tab / in-app browser → https://yoursite.com/pricing.
Work with your development team to handle in-app navigation for the billing/upgrade route in your SDK integration.

Silent exit for disqualified respondents

Add an Exit form in the Thank you & Exit Section.
Call to action → enable → Auto-trigger delay 0 → Close form on both surfaces.
On a screening question, add a logic jump: disqualified answer → Go to Exit form.

Respondents on that branch end immediately with no thank-you screen.

Auto-close after 5 seconds

Thank-you screen → enable call to action.
In-App and Shareable link → Close form.
Auto-trigger delay → 5000.

The thank-you message stays visible for five seconds, then the form dismisses automatically.

Tips

Configure both surfaces when the same form is used in-app and via shareable links.
Use a secondary button on thank-you screens for “Continue” + “Close” patterns (for example primary → upgrade, secondary → close).
Pair exit forms with Logic jumps for screening flows that should end without a thank-you message.
Test call to action behavior in Test logic jumps using In app vs Shareable preview modes.

Thank you screen
Exit form
Logic jumps
Language Setup
Web SDK — developer integration for in-app navigation and CTA events
Mobile SDK — developer integration for in-app navigation and CTA events

Call to action

On this page