How do I redirect a Visitor to a URL from a Chat or Scheduling flow?

The Redirect to node sends the Visitor's browser to a page you choose, after a delay you set. The address can be one fixed URL, or it can be built from what you know about the Visitor, such as a country in the path or a campaign in a query parameter.

Table of Contents

• Adding the Redirect to node
• Setting the delay
• Simple mode: one address
• Advanced mode: building the address from parts
• Using Data Fields and fallbacks
• What the Visitor experiences
• Checking a redirect in Chat Logs
• Publishing checks

Adding the Redirect to node

1. Open your Chat or Scheduling flow in the flow builder;
2. Click + where you want the redirect to happen;
3. Select Redirect to from the node menu.

Note: Add a Send a Message node before the Redirect to node so the Visitor knows where they are going, for example "Taking you to our pricing page now." The delay gives them time to read it.

Setting the delay

Set Delay before Redirect to how long the Visitor waits before the redirect, in seconds. It defaults to 10 seconds. Set it to 0 to redirect immediately.

Simple mode: one address

Simple mode takes one full URL. Paste the address into Redirect URL, including any path, query parameters, or #fragment. The address must start with http:// or https://.

Advanced mode: building the address from parts

To switch, click Advanced next to Simple under Redirect URL. Advanced mode splits the address into three parts:

• Base URL – the fixed part of your URL, like your domain (for example, https://www.example.com);
• Path – segments that follow the base URL, in order, separated by slashes. Click Add path segment to add one;
• Query Parameters – name and value pairs added after a question mark. Click Add query parameter to add one.

When you click Add path segment or Add query parameter, choose the type of value:

• Fixed value – always the same, for every Visitor;
• Data Field – uses what is known about the Visitor. Pick the Data Field from Select a Data Field.

URL Preview shows the address as it is being built. Each Data Field appears by name, and any part that can resolve empty is marked.

When you switch from Simple to Advanced, the address you already typed is split into its parts, so you do not need to type it again.

Note: Once any part uses a Data Field, you cannot switch back to Simple mode, because the address can no longer be written as one line. Remove the Data Fields to switch back.

Using Data Fields and fallbacks

A Data Field can be empty for some Visitors. To handle this, click Add fallback under a Data Field to name another Data Field to try next. You can add several, and they are tried in order. To end the chain, add a Fixed fallback value that is used when every Data Field in the chain is empty.

What happens when the whole chain is empty depends on where the value sits:

Add a fixed fallback value to every Data Field path segment if the redirect must always happen.

Data Field values are used exactly as saved, including capital letters. Many websites treat /Salesforce and /salesforce as different pages, so if your page addresses are lowercase, make sure the saved values are too.

Data Field values are encoded before they are added to the address. A value can fill its own segment or parameter, but it cannot change the domain or add new parts to the address.

What the Visitor experiences

• When the Visitor reaches the node, the whole browser page goes to the address, not only the chat window;
• The redirect waits for the delay you set;
• The flow continues through the node, so any nodes after the Redirect to node still run;
• If the Visitor reloads the page or reopens the chat after the redirect, they are not redirected a second time.

Checking a redirect in Chat Logs

In Chat Logs, select the Redirect to node to see what happened:

• Visitor redirected to – the address the Visitor was sent to, with each Data Field's value filled in;
• Redirect failed – the redirect was skipped, with the reason and the value that could not be resolved.

Publishing checks

You cannot publish the flow when:

• The base URL is missing, or is not a valid http or https address;
• A path segment is empty;
• A query parameter has no name or no value.

A value that contains spaces is valid. Only an empty value blocks publishing.